On 20 June 2017 at 10:06, Linus Walleij wrote:
> Moxart is deploying the DTBs with the kernel, they go hand-in-hand.
> Backward compatibility with old DTBs here would just be an academic
> exercise.
I've used CONFIG_ARM_APPENDED_DTB=y since the beginning mainly because
UC-7112-LX's proprietary bo
On Fri, Jun 9, 2017 at 2:52 PM, Andrew Jeffery wrote:
> So the fttmr010 bindings describe the clocks and clock-names properties
> as optional (a little confusingly, "Optionally required properties").
We should remove that. The timer frequency is strictly required.
> I guess keeping in mind the
On Fri, 2017-06-09 at 11:19 +0200, Arnd Bergmann wrote:
> > On Fri, Jun 9, 2017 at 9:30 AM, Andrew Jeffery wrote:
> > Add the clock-names property in init_timer() to work-around Aspeed
> > devicetrees from times prior to merging the Moxart/Aspeed and Faraday
> > drivers.
> >
> > > > Signed-off-by
On Fri, Jun 9, 2017 at 9:30 AM, Andrew Jeffery wrote:
> Add the clock-names property in init_timer() to work-around Aspeed
> devicetrees from times prior to merging the Moxart/Aspeed and Faraday
> drivers.
>
> Signed-off-by: Andrew Jeffery
> ---
> Well, here's an implementation I knocked up. It's
Add the clock-names property in init_timer() to work-around Aspeed
devicetrees from times prior to merging the Moxart/Aspeed and Faraday
drivers.
Signed-off-by: Andrew Jeffery
---
Well, here's an implementation I knocked up. It's a fair chunk of code for
marginal benefit. Joel is against it.
At
5 matches
Mail list logo
