From: jszhang@marvell.com (Jisheng Zhang)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] ARM: dts: berlin2q: add the Marvell Armada 1500 pro (BG2Q) device tree
Date: Thu, 13 Mar 2014 19:02:06 +0800 [thread overview]
Message-ID: <20140313190206.762108a2@xhacker> (raw)
In-Reply-To: <20140313104303.GB4418@piout.net>
Hi,
On Thu, 13 Mar 2014 03:43:03 -0700
Alexandre Belloni <alexandre.belloni@free-electrons.com> wrote:
> On 13/03/2014 at 10:05:31 +0000, Sebastian Hesselbarth wrote :
> > On 03/12/2014 11:06 AM, Antoine T?nart wrote:
> > >+ compatible = "arm,cortex-a9-twd-timer";
> > >+ reg = <0xad0600 0x20>;
> > >+ clocks = <&sysclk>;
> >
> > Playing with Chromecast, I remember local-timer running at sysclk/3 or
twdclk is running at cpuclk/3.
On chromecast, freq of cpuclk is the same as sysclk. But parent of twdclk
is cpuclk.
> > something. I know berlin2/berlin2cd is wrong here. Can you check that
> > for berlin2q local-timer also runs at sysclk/n?
> >
>
> Actually, what we have is sysclk = cpuclk/3 so I guess it depends on
> what you call sysclk.
>
> > >+ interrupts = <GIC_PPI 13 IRQ_TYPE_LEVEL_HIGH>;
> > >+ status = "okay";
> > >+ };
> > >+
> > >+ apb at e80000 {
> > >+ compatible = "simple-bus";
> > >+ #address-cells = <1>;
> > >+ #size-cells = <1>;
> > >+
> > >+ ranges = <0 0xe80000 0x10000>;
> > >+ interrupt-parent = <&aic>;
> > >+
> > >+ 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";
> > >+ };
> >
> > berlin2/berlin2cd have a vast amount of 8 apb timers. Any timers missing
> > here or did Marvell remove them?
We still have 8 apb timers
> >
> >
> > Also for uart, can you please double-check if there is no uart2?
> >
>
> We don't have those informations, maybe Jisheng can help ?
uart2 is removed
Thanks,
Jisheng
WARNING: multiple messages have this Message-ID (diff)
From: Jisheng Zhang <jszhang@marvell.com>
To: Alexandre Belloni <alexandre.belloni@free-electrons.com>
Cc: "Sebastian Hesselbarth" <sebastian.hesselbarth@gmail.com>,
"Antoine Ténart" <antoine.tenart@free-electrons.com>,
"Jimmy Xu" <zmxu@marvell.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2] ARM: dts: berlin2q: add the Marvell Armada 1500 pro (BG2Q) device tree
Date: Thu, 13 Mar 2014 19:02:06 +0800 [thread overview]
Message-ID: <20140313190206.762108a2@xhacker> (raw)
In-Reply-To: <20140313104303.GB4418@piout.net>
Hi,
On Thu, 13 Mar 2014 03:43:03 -0700
Alexandre Belloni <alexandre.belloni@free-electrons.com> wrote:
> On 13/03/2014 at 10:05:31 +0000, Sebastian Hesselbarth wrote :
> > On 03/12/2014 11:06 AM, Antoine Ténart wrote:
> > >+ compatible = "arm,cortex-a9-twd-timer";
> > >+ reg = <0xad0600 0x20>;
> > >+ clocks = <&sysclk>;
> >
> > Playing with Chromecast, I remember local-timer running at sysclk/3 or
twdclk is running at cpuclk/3.
On chromecast, freq of cpuclk is the same as sysclk. But parent of twdclk
is cpuclk.
> > something. I know berlin2/berlin2cd is wrong here. Can you check that
> > for berlin2q local-timer also runs at sysclk/n?
> >
>
> Actually, what we have is sysclk = cpuclk/3 so I guess it depends on
> what you call sysclk.
>
> > >+ interrupts = <GIC_PPI 13 IRQ_TYPE_LEVEL_HIGH>;
> > >+ status = "okay";
> > >+ };
> > >+
> > >+ apb@e80000 {
> > >+ compatible = "simple-bus";
> > >+ #address-cells = <1>;
> > >+ #size-cells = <1>;
> > >+
> > >+ ranges = <0 0xe80000 0x10000>;
> > >+ interrupt-parent = <&aic>;
> > >+
> > >+ 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";
> > >+ };
> >
> > berlin2/berlin2cd have a vast amount of 8 apb timers. Any timers missing
> > here or did Marvell remove them?
We still have 8 apb timers
> >
> >
> > Also for uart, can you please double-check if there is no uart2?
> >
>
> We don't have those informations, maybe Jisheng can help ?
uart2 is removed
Thanks,
Jisheng
next prev parent reply other threads:[~2014-03-13 11:02 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-12 11:06 [PATCH 0/2] ARM: add initial support for the Marvell BG2-Q DMP Antoine Ténart
2014-03-12 11:06 ` Antoine Ténart
2014-03-12 11:06 ` [PATCH 1/2] ARM: dts: berlin2q: add the Marvell Armada 1500 pro (BG2Q) device tree Antoine Ténart
2014-03-12 11:06 ` Antoine Ténart
2014-03-12 12:22 ` Alexandre Belloni
2014-03-12 12:22 ` Alexandre Belloni
2014-03-13 9:56 ` Sebastian Hesselbarth
2014-03-13 9:56 ` Sebastian Hesselbarth
2014-03-13 10:08 ` Alexandre Belloni
2014-03-13 10:08 ` Alexandre Belloni
2014-03-13 10:17 ` Sebastian Hesselbarth
2014-03-13 10:17 ` Sebastian Hesselbarth
2014-03-13 10:27 ` Antoine Ténart
2014-03-13 10:27 ` Antoine Ténart
2014-03-13 10:05 ` Sebastian Hesselbarth
2014-03-13 10:05 ` Sebastian Hesselbarth
2014-03-13 10:43 ` Alexandre Belloni
2014-03-13 10:43 ` Alexandre Belloni
2014-03-13 11:02 ` Jisheng Zhang [this message]
2014-03-13 11:02 ` Jisheng Zhang
2014-03-12 11:06 ` [PATCH 2/2] ARM: dts: berlin2q: add the Marvell BG2-Q DMP " Antoine Ténart
2014-03-12 11:06 ` Antoine Ténart
2014-03-12 11:20 ` Arnd Bergmann
2014-03-12 11:20 ` Arnd Bergmann
2014-03-12 11:30 ` Antoine Ténart
2014-03-12 11:30 ` Antoine Ténart
2014-03-12 12:04 ` Jisheng Zhang
2014-03-12 12:04 ` Jisheng Zhang
2014-03-12 12:37 ` Andrew Lunn
2014-03-12 12:37 ` Andrew Lunn
2014-03-12 12:44 ` Jisheng Zhang
2014-03-12 12:44 ` Jisheng Zhang
2014-03-13 10:08 ` Sebastian Hesselbarth
2014-03-13 10:08 ` Sebastian Hesselbarth
2014-03-12 11:35 ` [PATCH 0/2] ARM: add initial support for the Marvell BG2-Q DMP Alexandre Belloni
2014-03-12 11:35 ` Alexandre Belloni
2014-03-13 9:51 ` Sebastian Hesselbarth
2014-03-13 9:51 ` Sebastian Hesselbarth
2014-03-13 9:56 ` Alexandre Belloni
2014-03-13 9:56 ` Alexandre Belloni
2014-03-13 10:35 ` Antoine Ténart
2014-03-13 10:35 ` 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=20140313190206.762108a2@xhacker \
--to=jszhang@marvell.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.