From: Jason Cooper <jason@lakedaemon.net>
To: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Cc: Andrew Lunn <andrew@lunn.ch>, Lior Amsalem <alior@marvell.com>,
devicetree@vger.kernel.org,
Mike Turquette <mturquette@linaro.org>,
Tawfik Bayouk <tawfik@marvell.com>,
linux-kernel@vger.kernel.org, Nadav Haklai <nadavh@marvell.com>,
Ezequiel Garcia <ezequiel.garcia@free-electrons.com>,
Gregory CLEMENT <gregory.clement@free-electrons.com>,
linux-arm-kernel@lists.infradead.org,
Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
Subject: Re: [PATCH 6/6] dt: Update binding information for mvebu gating clocks with Armada 380/385
Date: Tue, 11 Feb 2014 14:06:32 -0500 [thread overview]
Message-ID: <20140211190632.GE27395@titan.lakedaemon.net> (raw)
In-Reply-To: <20140210185908.3374eaf6@skate>
On Mon, Feb 10, 2014 at 06:59:08PM +0100, Thomas Petazzoni wrote:
> Dear Andrew Lunn,
>
> On Mon, 10 Feb 2014 18:53:50 +0100, Andrew Lunn wrote:
> > > +The following is a list of provided IDs for Armada 380/385:
> > > +ID Clock Peripheral
> > > +-----------------------------------
> > > +0 audio Audio
> > > +2 ge2 Gigabit Ethernet 2
> > > +3 ge1 Gigabit Ethernet 1
> > > +4 ge0 Gigabit Ethernet 0
> > > +5 pex1 PCIe 1
> > > +6 pex2 PCIe 2
> > > +7 pex3 PCIe 3
> > > +8 pex4 PCIe 0
> >
> > Is that last one a typo? It at least looks a bit odd.
>
> Right, this should be:
>
> 8 pex0 PCIe 0
>
> (just checked again in the datasheet)
I can fix this up when I pull it in for Mike. No need to redo the
series just for this.
I'll let it sit for a day or two more before I pull it to give everyone
a chance to look it over.
thx,
Jason.
>
> Thomas
> --
> Thomas Petazzoni, CTO, Free Electrons
> Embedded Linux, Kernel and Android engineering
> http://free-electrons.com
>
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2014-02-11 19:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-10 17:32 [PATCH 0/6] Marvell Armada 375 and 38x clocks drivers Gregory CLEMENT
2014-02-10 17:32 ` [PATCH 1/6] clk: mvebu: add clock support for Armada 375 Gregory CLEMENT
2014-02-10 17:32 ` [PATCH 2/6] dt: Update binding information for mvebu core clocks with " Gregory CLEMENT
2014-02-10 17:32 ` [PATCH 3/6] dt: Update binding information for mvebu gating " Gregory CLEMENT
2014-02-10 17:32 ` [PATCH 4/6] clk: mvebu: add clock support for Armada 380/385 Gregory CLEMENT
2014-02-10 17:32 ` [PATCH 5/6] dt: Update binding information for mvebu core clocks with " Gregory CLEMENT
2014-02-10 17:32 ` [PATCH 6/6] dt: Update binding information for mvebu gating " Gregory CLEMENT
2014-02-10 17:53 ` Andrew Lunn
2014-02-10 17:59 ` Thomas Petazzoni
2014-02-11 19:06 ` Jason Cooper [this message]
2014-02-17 2:20 ` [PATCH 0/6] Marvell Armada 375 and 38x clocks drivers Jason Cooper
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=20140211190632.GE27395@titan.lakedaemon.net \
--to=jason@lakedaemon.net \
--cc=alior@marvell.com \
--cc=andrew@lunn.ch \
--cc=devicetree@vger.kernel.org \
--cc=ezequiel.garcia@free-electrons.com \
--cc=gregory.clement@free-electrons.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@linaro.org \
--cc=nadavh@marvell.com \
--cc=sebastian.hesselbarth@gmail.com \
--cc=tawfik@marvell.com \
--cc=thomas.petazzoni@free-electrons.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox