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 10:53:36 +0100 [thread overview]
Message-ID: <5322D1A0.9040601@gmail.com> (raw)
In-Reply-To: <5322D089.7010605@free-electrons.com>
On 03/14/2014 10:48 AM, Antoine T?nart wrote:
> On 14/03/2014 10:31, Sebastian Hesselbarth wrote:
>> On 03/13/2014 03:06 PM, Antoine T?nart wrote:
>>> + clocks {
>>> + #address-cells = <0>;
>>> + #size-cells = <0>;
>>> +
>>> + smclk: sysmgr-clock {
>>> + compatible = "fixed-clock";
>>> + #clock-cells = <0>;
>>> + clock-frequency = <25000000>;
>>> + };
>>> +
>>> + sysclk: system-clock {
>>> + compatible = "fixed-clock";
>>> + #clock-cells = <0>;
>>> + clock-frequency = <400000000>;
>>> + };
>>> + };
>>> +
>>> + soc {
>> [...]
>>> + 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 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.
>
> Sure, this is why I only kept one fixed clock in this patch.
>
> I'll add the cpuclk here then.
>
>>> + timer0: timer at 2c00 {
>>> + compatible = "snps,dw-apb-timer";
>>> + reg = <0x2c00 0x14>;
>>> + interrupts = <8>;
>>> + clock-freq = <100000000>;
>>> + status = "okay";
>>> + };
>>> +
>>> + timer1: timer at 2c14 {
>>> + compatible = "snps,dw-apb-timer";
>>> + reg = <0x2c14 0x14>;
>>> + clock-freq = <100000000>;
>>> + status = "disabled";
>>> + };
>>
>> Please also add the remaining 6 apb timers.
>
> I don't have any information about the remaining 6 apb timers. I'll ask
> Jisheng.
He replied to v1 of this patch with
"We still have 8 apb timers"
Sebastian
WARNING: multiple messages have this Message-ID (diff)
From: Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
To: "Antoine Ténart" <antoine.tenart@free-electrons.com>
Cc: alexandre.belloni@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 10:53:36 +0100 [thread overview]
Message-ID: <5322D1A0.9040601@gmail.com> (raw)
In-Reply-To: <5322D089.7010605@free-electrons.com>
On 03/14/2014 10:48 AM, Antoine Ténart wrote:
> On 14/03/2014 10:31, Sebastian Hesselbarth wrote:
>> On 03/13/2014 03:06 PM, Antoine Ténart wrote:
>>> + clocks {
>>> + #address-cells = <0>;
>>> + #size-cells = <0>;
>>> +
>>> + smclk: sysmgr-clock {
>>> + compatible = "fixed-clock";
>>> + #clock-cells = <0>;
>>> + clock-frequency = <25000000>;
>>> + };
>>> +
>>> + sysclk: system-clock {
>>> + compatible = "fixed-clock";
>>> + #clock-cells = <0>;
>>> + clock-frequency = <400000000>;
>>> + };
>>> + };
>>> +
>>> + soc {
>> [...]
>>> + 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 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.
>
> Sure, this is why I only kept one fixed clock in this patch.
>
> I'll add the cpuclk here then.
>
>>> + timer0: timer@2c00 {
>>> + compatible = "snps,dw-apb-timer";
>>> + reg = <0x2c00 0x14>;
>>> + interrupts = <8>;
>>> + clock-freq = <100000000>;
>>> + status = "okay";
>>> + };
>>> +
>>> + timer1: timer@2c14 {
>>> + compatible = "snps,dw-apb-timer";
>>> + reg = <0x2c14 0x14>;
>>> + clock-freq = <100000000>;
>>> + status = "disabled";
>>> + };
>>
>> Please also add the remaining 6 apb timers.
>
> I don't have any information about the remaining 6 apb timers. I'll ask
> Jisheng.
He replied to v1 of this patch with
"We still have 8 apb timers"
Sebastian
next prev parent reply other threads:[~2014-03-14 9:53 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 [this message]
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
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=5322D1A0.9040601@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.