The PLL2 on the A10 and later SoCs is the clock used for all the audio
related operations.
This clock has a somewhat complex output tree, with three outputs (2X, 4X
and 8X) with a fixed divider from the base clock, and an output (1X) with a
post divider.
However, we can simplify things since the
From: Emilio López
The codec clock on sun4i, sun5i and sun7i is a simple gate with PLL2 as
parent. Add a driver for such a clock.
Signed-off-by: Emilio López
Signed-off-by: Hans de Goede
Signed-off-by: Maxime Ripard
From: Shaohui Xie
Modify the I2C_IMX config to support to Layerscape platforms.
Signed-off-by: Mingkai Hu
Signed-off-by: Wenbin Song
Signed-off-by: Hou Zhiqiang
---
V5: V4 V3 V2
- No
From: Shaohui Xie
Modify watchdog/Kconfig file to support Layerscape platforms.
Signed-off-by: Shaohui Xie
Signed-off-by: Wenbin Song
Signed-off-by: Hou Zhiqiang
Acked-by: Guenter Roeck
From: Hou Zhiqiang
Signed-off-by: Hou Zhiqiang
Acked-by: Stephen Boyd
---
V5: V4 V3 V2
- No change.
drivers/clk/clk-qoriq.c | 38 ++
1 file changed, 38 insertions(+)
diff --git
From: Shaohui Xie
Signed-off-by: Shaohui Xie
Signed-off-by: Mingkai Hu
Signed-off-by: Wenbin Song
Signed-off-by: Hou Zhiqiang
---
V5: V4 V3
- No change.
V2:
-
From: Mingkai Hu
LS1043a is an SoC with 4 ARMv8 A53 cores and most other IP blocks
similar to LS1021a which complies to Chassis 2.1 spec.
Following levels of DTSI/DTS files have been created for the
LS1043A SoC family:
- fsl-ls1043a.dtsi:
DTS-Include file for FSL
From: Mingkai Hu
Signed-off-by: Mingkai Hu
Signed-off-by: Hou Zhiqiang
---
V5: V4 V3 V2
- No change.
Documentation/devicetree/bindings/arm/fsl.txt | 4
1 file changed, 4 insertions(+)
diff --git
On Mon, Oct 19, 2015 at 4:08 PM, Maxime Ripard
wrote:
> The PLL2 on the A10 and later SoCs is the clock used for all the audio
> related operations.
>
> This clock has a somewhat complex output tree, with three outputs (2X, 4X
> and 8X) with a fixed divider from
On Sun, 2015-10-18 at 20:53 +0100, Mark Brown wrote:
> On Sun, Oct 18, 2015 at 12:37:57PM -0700, Greg Kroah-Hartman wrote:
> > On Sun, Oct 18, 2015 at 08:29:31PM +0100, Mark Brown wrote:
> > > On Fri, Oct 16, 2015 at 11:57:50PM -0700, Greg Kroah-Hartman wrote:
>
> > > > I can't see adding calls
On Mon, Oct 19, 2015 at 4:08 PM, Maxime Ripard
wrote:
> Some clocks are using a multiplier component, however, unlike their mux,
> gate or divider counterpart, these factors don't have a basic clock
> implementation.
>
> This leads to code duplication across
On Mon, Oct 19, 2015 at 10:44:41AM +0100, David Woodhouse wrote:
> On Sun, 2015-10-18 at 20:53 +0100, Mark Brown wrote:
> > On Sun, Oct 18, 2015 at 12:37:57PM -0700, Greg Kroah-Hartman wrote:
> > > On Sun, Oct 18, 2015 at 08:29:31PM +0100, Mark Brown wrote:
> > > > On Fri, Oct 16, 2015 at
On Mon, Oct 19, 2015 at 04:29:40PM +0100, David Woodhouse wrote:
> On Mon, 2015-10-19 at 15:50 +0100, Mark Brown wrote:
> > > But the point I'm making is that we are working towards *fixing* that,
> > > and *not* using DT-specific code in places where we should be using the
> > > generic APIs.
>
On Mon, Oct 19, 2015 at 10:29 AM, David Woodhouse wrote:
> On Mon, 2015-10-19 at 15:50 +0100, Mark Brown wrote:
>> > But the point I'm making is that we are working towards *fixing* that,
>> > and *not* using DT-specific code in places where we should be using the
>> >
On Monday, October 19, 2015 10:58:25 AM Rob Herring wrote:
> On Mon, Oct 19, 2015 at 10:29 AM, David Woodhouse wrote:
> > On Mon, 2015-10-19 at 15:50 +0100, Mark Brown wrote:
> >> > But the point I'm making is that we are working towards *fixing* that,
> >> > and *not* using
On 10/19, Krzysztof Kozlowski wrote:
> Add a gate clock for controlling all clocks of Security Sub System
> (SSS).
>
> Signed-off-by: Krzysztof Kozlowski
> ---
The To: list is huge, so I have no idea if you want me to apply
this patch or not, and given that it's part of
On 10/16/2015 04:05 PM, Stephen Boyd wrote:
> On 10/16, York Sun wrote:
>>
>>
>> On 10/16/2015 02:31 PM, Stephen Boyd wrote:
>>> On 10/16, York Sun wrote:
On 10/09/2015 05:09 PM, Stephen Boyd wrote:
> On 10/09, York Sun wrote:
>> +/*
>> + * To support multiple si5338
Hello,
On Mon, Oct 19, 2015 at 04:43:24PM +0100, Russell King - ARM Linux wrote:
> It's a bit ironic that you've chosen GPIO as an example there. The
> "new" GPIO API (the gpiod_* stuff) only has a fwnode way to get the
> gpio descriptor. There's no of_* method.
Without following all that
On 10/16, Ray Jui wrote:
> From: Simran Rai
>
> This patch affects the clocks that use fractional ndivider in their
> PLL output frequency calculation. Instead of 2^20 divide factor, the
> clock's ndiv integer shift was used. Fixed the bug by replacing ndiv
> integer shift
On 20.10.2015 01:11, Tobias Jakobi wrote:
> Hello Krzysztof,
>
> I can confirm that this also works on a Odroid-X2, so I guess it's safe
> to enable the PRNG for all Exynos4412-based Odroid devices.
Sure, I can send a patch for that. I can test it later also on Odroid-U3.
>
> Any chance that
On Tue, Oct 20, 2015 at 3:39 AM, Russell King - ARM Linux
wrote:
> On Mon, Oct 19, 2015 at 08:27:44PM +0200, Uwe Kleine-König wrote:
>> Hello,
>>
>> On Mon, Oct 19, 2015 at 04:43:24PM +0100, Russell King - ARM Linux wrote:
>> > It's a bit ironic that you've chosen GPIO as
On 10/20, York Sun wrote:
> Sorry for top posting. I am on outlook web.
>
> We have no problem with device tree. Let's put it aside.
>
> When device is not used, the platform data is used to hold the data, filled
> by a platform device before probing the clock. For my case, the platform
>
On 10/18, Geliang Tang wrote:
> s/regsiter/register/
>
> Signed-off-by: Geliang Tang
> ---
Applied to clk-next
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
--
To unsubscribe from this list: send the line
On Mon, Oct 19, 2015 at 4:40 PM, Rafael J. Wysocki wrote:
> On Monday, October 19, 2015 10:58:25 AM Rob Herring wrote:
>> On Mon, Oct 19, 2015 at 10:29 AM, David Woodhouse
>> wrote:
>> > On Mon, 2015-10-19 at 15:50 +0100, Mark Brown wrote:
>> >> > But
On 10/19, York Sun wrote:
>
>
> On 10/16/2015 04:05 PM, Stephen Boyd wrote:
> > On 10/16, York Sun wrote:
> >>
> >>
> >> On 10/16/2015 02:31 PM, Stephen Boyd wrote:
> >>> On 10/16, York Sun wrote:
>
>
> On 10/09/2015 05:09 PM, Stephen Boyd wrote:
> > On 10/09, York Sun wrote:
On 10/19/2015 02:55 PM, Ray Jui wrote:
>
>
> On 15-10-19 02:49 PM, Stephen Boyd wrote:
>> On 10/16, Ray Jui wrote:
>>> From: Simran Rai
>>>
>>> This patch affects the clocks that use fractional ndivider in their
>>> PLL output frequency calculation. Instead of 2^20 divide
From: Simran Rai
This patch affects the clocks that use fractional ndivider in their
PLL output frequency calculation. Instead of 2^20 divide factor, the
clock's ndiv integer shift was used. Fixed the bug by replacing ndiv
integer shift with 2^20 factor.
Signed-off-by:
Sorry for top posting. I am on outlook web.
We have no problem with device tree. Let's put it aside.
When device is not used, the platform data is used to hold the data, filled by
a platform device before probing the clock. For my case, the platform device is
a PCIe device. It is a
From: Kuninori Morimoto
This patch adds CS2000 Fractional-N driver as clock provider.
Signed-off-by: Kuninori Morimoto
---
v4 -> v5
- remove "clock-frequency"
- use dev on clk_register()
- remove CLK_IS_BASIC
- .enable ->
On 10/19/2015 05:36 PM, Stephen Boyd wrote:
> On 10/20, York Sun wrote:
>> Sorry for top posting. I am on outlook web.
>>
>> We have no problem with device tree. Let's put it aside.
>>
>> When device is not used, the platform data is used to hold the data, filled
>> by a platform device before
Hi Russell,
On Mon, Oct 19, 2015 at 5:35 PM, Russell King - ARM Linux
wrote:
>> > What you can do is print those devices which have failed to probe at
>> > late_initcall() time - possibly augmenting that with reports from
>> > subsystems showing what resources are not
On Mon, Oct 19, 2015 at 06:21:40PM +0200, Geert Uytterhoeven wrote:
> Hi Russell,
>
> On Mon, Oct 19, 2015 at 5:35 PM, Russell King - ARM Linux
> wrote:
> >> > What you can do is print those devices which have failed to probe at
> >> > late_initcall() time - possibly
On Sat, Oct 17, 2015 at 8:19 AM, Rob Herring wrote:
> On Fri, Oct 16, 2015 at 4:23 PM, Olof Johansson wrote:
>> Hi,
>>
>> I've bisected boot failures in next-20151016 down to patches in this branch:
>>
>> On Thu, Oct 15, 2015 at 4:42 AM, Tomeu Vizoso
>>
33 matches
Mail list logo