Hi Stephen,
Thanks for all of your comments.
On Mon, 28 Sep 2015, Stephen Boyd wrote:
> I'd say your binding is wrong. Either the container node
> "pinctrl" is a software concept that contains the two devices for
> port_a and port_b or there's only one pinctrl device that happens
> to span some
Am Montag, 28. September 2015, 11:46:40 schrieb Stephen Boyd:
> On 09/23, Heiko Stübner wrote:
> > ---
> >
> > While it may be nice to do the actual handling of the clock references
> > only in the calling code, in this current use case it would create
> > a big additional overhead.
> >
> > It
mxc_timer_init must not be called from within mx31_clocks_init_dt. It will
eventually be called by imx31_timer_init_dt
(drivers/clocksource/timer-imx-gpt.c).
This arranges the initialization code similar to clk-imx27.c
Signed-off-by: Alexander Stein
---
Hi Rob,
On Sat, Sep 5, 2015 at 2:45 AM, Rob Herring wrote:
> On Fri, Sep 4, 2015 at 2:05 AM, Bhupesh Sharma
> wrote:
>> This patch updates the LS2085a DTSI (DTS Include) file to add
>> support for various peripherals supported by FSL LS2085a
The rk3036's pll and clock are different with base on the rk3066(rk3188,
rk3288, rk3368 use it), there are different adjust foctors and control
registers, so these should be independent and separate from the series
of rk3066s.
Signed-off-by: Xing Zheng
Reviewed-by:
Previously we've only supported a few fixed clocks based on
assumptions about how the firmware sets up the clocks, but this
binding will let us control the actual (audio power domain) clock
manager.
Signed-off-by: Eric Anholt
Acked-by: Stephen Warren
---
clk-bcm2835.c predates the drivers under bcm/, but all the new BCM
drivers are going in there so let's follow them.
Signed-off-by: Eric Anholt
Acked-by: Stephen Warren
---
drivers/clk/Makefile| 1 -
drivers/clk/bcm/Makefile| 1
On Mon, Sep 28, 2015 at 5:03 AM, Bhupesh SHARMA wrote:
> Hi Rob,
>
> On Sat, Sep 5, 2015 at 2:45 AM, Rob Herring wrote:
>> On Fri, Sep 4, 2015 at 2:05 AM, Bhupesh Sharma
>> wrote:
>>> This patch updates the LS2085a