[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <560999B6.7080400@wwwdotorg.org>
Date: Mon, 28 Sep 2015 13:49:10 -0600
From: Stephen Warren <swarren@...dotorg.org>
To: Eric Anholt <eric@...olt.net>
Cc: linux-clk@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-rpi-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
Lee Jones <lee@...nel.org>,
Stephen Boyd <sboyd@...eaurora.org>,
Mike Turquette <mturquette@...libre.com>,
devicetree@...r.kernel.org
Subject: Re: [PATCH 3/3] ARM: bcm2835: Add the auxiliary clocks to the device
tree.
On 09/28/2015 01:26 PM, Eric Anholt wrote:
> Stephen Warren <swarren@...dotorg.org> writes:
>
>> On 09/10/2015 03:22 PM, Eric Anholt wrote:
>>> These will be used for enabling UART1, SPI1, and SPI2.
>>
>>> diff --git a/arch/arm/boot/dts/bcm2835.dtsi b/arch/arm/boot/dts/bcm2835.dtsi
>>
>>> + aux_clocks: aux-clocks@...e215004 {
>>> + compatible = "brcm,bcm2835-aux-clock";
>>> + #clock-cells = <1>;
>>> + reg = <0x7e215004 0x4>;
>>
>> Actually, I take back the ack on this patch. This HW module has two
>> registers. The reg property should include both of those registers so
>> that if SW needs to start using the other register at some time in the
>> future, the entire set of registers is already represented in DT.
>
> If I changed it to "reg = <0x7e215000 0x8>" and use a #define for the
> clock register offset in patch 2/3, would I then have your ack?
I suspect the compatible should then be "brcm,bcm2835-aux" (or similar)
since the node would represent the entire aux module, not just the clock
gate feature of the module (assuming there are other features in the aux
module besides just the clock gate).
With the reg change and the compatible change if appropriate, you can
have my ack,
Acked-by: Stephen Warren <swarren@...dotorg.org>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists