From: sebastian.hesselbarth@gmail.com (Sebastian Hesselbarth)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 1/3] ARM: dts: berlin2q: add the Marvell Armada 1500 pro
Date: Fri, 14 Mar 2014 12:36:44 +0100 [thread overview]
Message-ID: <5322E9CC.9060602@gmail.com> (raw)
In-Reply-To: <20140314113202.GB3106@piout.net>
On 03/14/2014 12:32 PM, Alexandre Belloni wrote:
> On 14/03/2014 at 10:31:55 +0100, Sebastian Hesselbarth wrote :
>> On 03/13/2014 03:06 PM, Antoine T?nart wrote:
>>> + local-timer at ad0600 {
>>> + compatible = "arm,cortex-a9-twd-timer";
>>> + reg = <0xad0600 0x20>;
>>> + clocks = <&sysclk>;
>>
>> If I understand Jisheng correctly, this should be cpuclk/3. When
>> removing the clocks {} container above, please also take care of
>> it.
>>
>
> You understood correctly
>
>> You can do
>>
>> cpuclk: cpu-clock {
>> compatible = "fixed-clock";
>> #clock-cells = <0>;
>> clock-frequency = <1200000000>; /* <- put correct freq here */
>> };
>>
>> sysclk: system-clock {
>> compatible = "fixed-factor-clock";
>> #clock-cells = <0>;
>> clocks = <&cpuclk>;
>> clock-multi = <1>;
>> clock-div = <3>;
>> };
>>
>> Hopefully, we'll have proper clock drivers soon so we can just replace
>> referenced "fixed-*" clocks.
>>
>
> I'm working on that, do you have some code that you can share right now ?
No, nothing specific. You can have a look at drivers/clk/mvebu/ and see
how we deal with it on mvebu. For now, you can stick with bg2q and I'll
see how we extend that drivers for bg2/bg2cd then.
BTW: We really enjoy having a mvebu subfolder in drivers/clk as it makes
things easier. If you prepare any clk drivers for berlin, I'd suggest to
put them in drivers/clk/berlin from the beginning.
Sebastian
WARNING: multiple messages have this Message-ID (diff)
From: Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
To: Alexandre Belloni <alexandre.belloni@free-electrons.com>
Cc: "Antoine Ténart" <antoine.tenart@free-electrons.com>,
zmxu@marvell.com, jszhang@marvell.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/3] ARM: dts: berlin2q: add the Marvell Armada 1500 pro
Date: Fri, 14 Mar 2014 12:36:44 +0100 [thread overview]
Message-ID: <5322E9CC.9060602@gmail.com> (raw)
In-Reply-To: <20140314113202.GB3106@piout.net>
On 03/14/2014 12:32 PM, Alexandre Belloni wrote:
> On 14/03/2014 at 10:31:55 +0100, Sebastian Hesselbarth wrote :
>> On 03/13/2014 03:06 PM, Antoine Ténart wrote:
>>> + local-timer@ad0600 {
>>> + compatible = "arm,cortex-a9-twd-timer";
>>> + reg = <0xad0600 0x20>;
>>> + clocks = <&sysclk>;
>>
>> If I understand Jisheng correctly, this should be cpuclk/3. When
>> removing the clocks {} container above, please also take care of
>> it.
>>
>
> You understood correctly
>
>> You can do
>>
>> cpuclk: cpu-clock {
>> compatible = "fixed-clock";
>> #clock-cells = <0>;
>> clock-frequency = <1200000000>; /* <- put correct freq here */
>> };
>>
>> sysclk: system-clock {
>> compatible = "fixed-factor-clock";
>> #clock-cells = <0>;
>> clocks = <&cpuclk>;
>> clock-multi = <1>;
>> clock-div = <3>;
>> };
>>
>> Hopefully, we'll have proper clock drivers soon so we can just replace
>> referenced "fixed-*" clocks.
>>
>
> I'm working on that, do you have some code that you can share right now ?
No, nothing specific. You can have a look at drivers/clk/mvebu/ and see
how we deal with it on mvebu. For now, you can stick with bg2q and I'll
see how we extend that drivers for bg2/bg2cd then.
BTW: We really enjoy having a mvebu subfolder in drivers/clk as it makes
things easier. If you prepare any clk drivers for berlin, I'd suggest to
put them in drivers/clk/berlin from the beginning.
Sebastian
next prev parent reply other threads:[~2014-03-14 11:36 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-13 14:06 [PATCH v2 0/3] ARM: add initial support for the Marvell BG2-Q DMP Antoine Ténart
2014-03-13 14:06 ` Antoine Ténart
2014-03-13 14:06 ` [PATCH v2 1/3] ARM: dts: berlin2q: add the Marvell Armada 1500 pro Antoine Ténart
2014-03-13 14:06 ` Antoine Ténart
2014-03-13 17:25 ` Mark Rutland
2014-03-13 17:25 ` Mark Rutland
2014-03-13 17:25 ` Mark Rutland
2014-03-14 9:31 ` Sebastian Hesselbarth
2014-03-14 9:31 ` Sebastian Hesselbarth
2014-03-14 9:48 ` Antoine Ténart
2014-03-14 9:48 ` Antoine Ténart
2014-03-14 9:53 ` Sebastian Hesselbarth
2014-03-14 9:53 ` Sebastian Hesselbarth
2014-03-14 11:32 ` Alexandre Belloni
2014-03-14 11:32 ` Alexandre Belloni
2014-03-14 11:36 ` Sebastian Hesselbarth [this message]
2014-03-14 11:36 ` Sebastian Hesselbarth
2014-03-13 14:06 ` [PATCH v2 2/3] ARM: berlin2q: add the Marvell Armada 1500 pro in the documentation Antoine Ténart
2014-03-13 14:06 ` Antoine Ténart
2014-03-13 14:06 ` [PATCH v2 3/3] ARM: dts: berlin2q: add the Marvell BG2-Q DMP device tree Antoine Ténart
2014-03-13 14:06 ` Antoine Ténart
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5322E9CC.9060602@gmail.com \
--to=sebastian.hesselbarth@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.