SUPERH platform development
 help / color / mirror / Atom feed
From: Simon Horman <horms@verge.net.au>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [GIT 00/19 v2] Renesas ARM based SoC pinmux updates for v3.12
Date: Sun, 18 Aug 2013 03:55:57 +0000	[thread overview]
Message-ID: <20130818035557.GB30709@verge.net.au> (raw)
In-Reply-To: <20130814072328.GA30577@quad.lixom.net>

On Wed, Aug 14, 2013 at 12:23:28AM -0700, Olof Johansson wrote:
> On Wed, Jul 24, 2013 at 09:32:14AM +0900, Simon Horman wrote:
> > Hi Olof, Hi Arnd,
> > 
> > please consider the following pinmux updates for v3.12.
> > 
> > Difference with v1 of this pull-request:
> > * Remove bogus i2c portions of the first patch of the series.
> > * Correct addressing mode used in dts of the first patch of the series.
> > * Removal of egg from face: wip
> > 
> > The following changes since commit ad81f0545ef01ea651886dddac4bef6cec930092:
> > 
> >   Linux 3.11-rc1 (2013-07-14 15:18:27 -0700)
> > 
> > are available in the git repository at:
> > 
> >   git://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas.git tags/renesas-pinmux-for-v3.12
> 
> Pulled, but I noticed this. Can you please follow up with bindings revisit in
> time for 3.12 final (i.e. if we need to take it after merge window that's
> probably OK):
> 
>         pfc: pfc@e6060000 {                                                     
>                 compatible = "renesas,pfc-r8a7790";                             
>                 reg = <0 0xe6060000 0 0x250>;                                   
>                 #gpio-range-cells = <3>;                                        
>         };                                                                      
>                                                                                                                
>         sdhi0: sdhi@ee100000 {                                                  
>                 compatible = "renesas,r8a7790-sdhi"; 
> 
> 
> I.e. different ordering on the compatible values looks a bit uncoordinated.

Can I confirm that you are referring to the fact that
assume you mean that "-sdhi" follows "r8a7790" whereas "pfc-" precedes
"r8a7790"?

If so, I'll work with Laurent and Guennadi (both CCed, both on vacation),
and Magnus to resolve this inconsistency.

> I resolved the conflicts by inserting the entries alphabetically; most
> DTS files are ordered by address instead of alphabetically, but I stuck
> to the current norm per-file.

Thanks.

  reply	other threads:[~2013-08-18  3:55 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-24  0:32 [GIT 00/19 v2] Renesas ARM based SoC pinmux updates for v3.12 Simon Horman
2013-07-24  0:32 ` [PATCH 01/19] ARM: shmobile: r8a73a4: Add pin control device to device tree Simon Horman
2013-07-24  6:11   ` Guennadi Liakhovetski
2013-07-24  7:23     ` Simon Horman
2013-07-24  0:32 ` [PATCH 02/19] ARM: shmobile: r8a7740: " Simon Horman
2013-07-24  0:32 ` [PATCH 03/19] ARM: shmobile: r8a7778: " Simon Horman
2013-07-24  0:32 ` [PATCH 04/19] ARM: shmobile: r8a7778: Add GPIO controller devices " Simon Horman
2013-07-24  0:32 ` [PATCH 05/19] ARM: shmobile: r8a7779: Add pin control device " Simon Horman
2013-07-24  0:32 ` [PATCH 06/19] ARM: shmobile: r8a7779: Add GPIO controller devices " Simon Horman
2013-07-24  0:32 ` [PATCH 07/19] ARM: shmobile: r8a7790: Add pin control device " Simon Horman
2013-07-24  0:32 ` [PATCH 08/19] ARM: shmobile: r8a7790: Add GPIO controller devices " Simon Horman
2013-07-24  0:32 ` [PATCH 09/19] ARM: shmobile: sh7372: Add pin control device " Simon Horman
2013-07-24  0:32 ` [PATCH 10/19] ARM: shmobile: sh73a0: " Simon Horman
2013-07-24  0:32 ` [PATCH 11/19] ARM: shmobile: armadillo-reference: Move pinctrl mappings " Simon Horman
2013-07-24  0:32 ` [PATCH 12/19] ARM: shmobile: armadillo-reference: Add st1232 pin mappings Simon Horman
2013-07-24  0:32 ` [PATCH 13/19] ARM: shmobile: armadillo-reference: Move st1232 reset GPIO to DT Simon Horman
2013-07-24  0:32 ` [PATCH 14/19] ARM: shmobile: armadillo-reference: Add LED1-LED4 to the device tree Simon Horman
2013-07-24  0:32 ` [PATCH 15/19] ARM: shmobile: marzen-reference: Move pinctrl mappings to " Simon Horman
2013-07-24  0:32 ` [PATCH 16/19] ARM: shmobile: marzen-reference: Add LED2-LED4 to the " Simon Horman
2013-07-24  0:32 ` [PATCH 17/19] ARM: shmobile: kzm9g-reference: Move pinctrl mappings to " Simon Horman
2013-07-24  0:32 ` [PATCH 18/19] ARM: shmobile: kzm9g-reference: Move SDHI regulators to DT Simon Horman
2013-07-24  0:32 ` [PATCH 19/19] ARM: shmobile: kzm9g-reference: Add LED1-LED4 to the device tree Simon Horman
2013-07-24  8:05 ` [GIT 00/19 v2] Renesas ARM based SoC pinmux updates for v3.12 Simon Horman
2013-08-14  7:23 ` Olof Johansson
2013-08-18  3:55   ` Simon Horman [this message]
2013-08-22  5:03     ` Olof Johansson
2013-08-22  5:32       ` Simon Horman

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=20130818035557.GB30709@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