From: Simon Horman <horms@verge.net.au>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/5] ARM: shmobile: Use SoC-specific clock source compat strings
Date: Tue, 09 Sep 2014 02:50:21 +0000 [thread overview]
Message-ID: <20140909025021.GF31320@verge.net.au> (raw)
In-Reply-To: <20140908002956.GA32532@verge.net.au>
On Mon, Sep 08, 2014 at 09:29:56AM +0900, Simon Horman wrote:
> On Mon, Sep 08, 2014 at 09:27:43AM +0900, Simon Horman wrote:
> > In general Renesas hardware is not documented to the extent
> > where the relationship between IP blocks on different SoCs can be assumed
> > although they may appear to operate the same way. Furthermore the
> > documentation typically does not specify a version for individual
> > IP blocks. For these reasons a convention of using the SoC name in place
> > of a version and providing SoC-specific compat strings has been adopted.
> >
> > Although not universally liked this convention is used in the bindings
> > for a number of drivers for Renesas hardware. The purpose of this series
> > is to make use of SoC specific clock source strings.
>
> This series is based on
> renesas-next-20140904v2-v3.17-rc2
>
> The bindings used are proposed in
> "[PATCH v3 0/3] clocksource: Document Renesas SoC specific bindings"
>
> > Simon Horman (5):
> > ARM: shmobile: r8a7740: Use SoC-specific 48-bit CMT compat string
> > ARM: shmobile: r8a7790: Use SoC-specific 48-bit CMT compat string
> > ARM: shmobile: r8a7791: Use SoC-specific 48-bit CMT compat string
> > ARM: shmobile: r7s72100: Use SoC-specific MTU2 compat string
> > ARM: shmobile: r8a7779: Use SoC-specific TMU compat string
> >
> > arch/arm/boot/dts/r7s72100.dtsi | 2 +-
> > arch/arm/boot/dts/r8a7740.dtsi | 2 +-
> > arch/arm/boot/dts/r8a7779.dtsi | 6 +++---
> > arch/arm/boot/dts/r8a7790.dtsi | 4 ++--
> > arch/arm/boot/dts/r8a7791.dtsi | 4 ++--
> > 5 files changed, 9 insertions(+), 9 deletions(-)
I have queued up these changes.
prev parent reply other threads:[~2014-09-09 2:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-08 0:27 [PATCH 0/5] ARM: shmobile: Use SoC-specific clock source compat strings Simon Horman
2014-09-08 0:27 ` [PATCH 1/5] ARM: shmobile: r8a7740: Use SoC-specific 48-bit CMT compat string Simon Horman
2014-09-08 0:27 ` [PATCH 2/5] ARM: shmobile: r8a7790: " Simon Horman
2014-09-08 0:27 ` [PATCH 3/5] ARM: shmobile: r8a7791: " Simon Horman
2014-09-08 0:27 ` [PATCH 4/5] ARM: shmobile: r7s72100: Use SoC-specific MTU2 " Simon Horman
2014-09-08 0:27 ` [PATCH 5/5] ARM: shmobile: r8a7779: Use SoC-specific TMU " Simon Horman
2014-09-08 0:29 ` [PATCH 0/5] ARM: shmobile: Use SoC-specific clock source compat strings Simon Horman
2014-09-09 2:50 ` Simon Horman [this message]
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=20140909025021.GF31320@verge.net.au \
--to=horms@verge.net.au \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).