On Thu, Oct 17, 2013 at 6:56 AM, Mark Rutland wrote:
> On Wed, Oct 16, 2013 at 10:47:06PM +0100, Tim Kryger wrote:
>> Rather than declaring the frequency of the external clock, specify the
>> label of the clock such that the driver may determine the frequency on
>> its own.
>
> Nit: we're not spec
On Wed, Oct 16, 2013 at 10:47:06PM +0100, Tim Kryger wrote:
> Rather than declaring the frequency of the external clock, specify the
> label of the clock such that the driver may determine the frequency on
> its own.
Nit: we're not specifying the label of the clock. Clocks are represented
py a pha
On 10/17/2013 07:41 AM, Christian Daudt wrote:
On Wed, Oct 16, 2013 at 2:47 PM, Tim Kryger wrote:
Rather than declaring the frequency of the external clock, specify the
label of the clock such that the driver may determine the frequency on
its own.
Signed-off-by: Tim Kryger
Reviewed-by: Marku
On Wed, Oct 16, 2013 at 2:47 PM, Tim Kryger wrote:
> Rather than declaring the frequency of the external clock, specify the
> label of the clock such that the driver may determine the frequency on
> its own.
>
> Signed-off-by: Tim Kryger
> Reviewed-by: Markus Mayer
> Reviewed-by: Matt Porter
>
Rather than declaring the frequency of the external clock, specify the
label of the clock such that the driver may determine the frequency on
its own.
Signed-off-by: Tim Kryger
Reviewed-by: Markus Mayer
Reviewed-by: Matt Porter
---
arch/arm/boot/dts/bcm11351.dtsi | 8
1 file changed,
5 matches
Mail list logo