mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jason Cooper <jason@lakedaemon.net>
To: Haojian Zhuang <haojian.zhuang@gmail.com>
Cc: Neil Zhang <zhangwm@marvell.com>,
	Grant Likely <grant.likely@linaro.org>,
	Bergmann Arnd <arnd@arndb.de>,
	devicetree-discuss@lists.ozlabs.org,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH V3 1/3] dts: change Marvell prefix to 'marvell'
Date: Wed, 10 Jul 2013 17:50:41 -0400	[thread overview]
Message-ID: <20130710215041.GR11908@titan.lakedaemon.net> (raw)
In-Reply-To: <CAN1soZzMvront1-jcBW6-uRKNs0OZNGnmiOjKGZSM28bViB_8A@mail.gmail.com>

On Wed, Jul 10, 2013 at 10:08:50PM +0800, Haojian Zhuang wrote:
> On Wed, Jul 10, 2013 at 8:24 PM, Jason Cooper <jason@lakedaemon.net> wrote:
> > On Wed, Jul 10, 2013 at 04:19:46PM +0800, Haojian Zhuang wrote:
> >> On Tue, Jul 9, 2013 at 8:49 PM, Jason Cooper <jason@lakedaemon.net> wrote:
> >> > Neil,
> >> >
> >> > On Tue, Jul 09, 2013 at 02:42:44PM +0800, Neil Zhang wrote:
> >> >> The documented vendor prefix for Marvell is 'marvell', not 'mrvl', so
> >> >> let's change it.
> >> >>
> >> >> Signed-off-by: Neil Zhang <zhangwm@marvell.com>
> >> >> ---
> >> >>  .../devicetree/bindings/arm/mrvl/intc.txt          |   16 +++---
> >> >>  .../devicetree/bindings/arm/mrvl/mrvl.txt          |    6 +-
> >> >>  .../devicetree/bindings/arm/mrvl/timer.txt         |    4 +-
> >> >>  Documentation/devicetree/bindings/i2c/i2c-pxa.txt  |   14 +++---
> >> >>  .../devicetree/bindings/mmc/sdhci-pxa.txt          |    8 ++--
> >> >>  .../devicetree/bindings/rtc/sa1100-rtc.txt         |    4 +-
> >> >>  .../devicetree/bindings/serial/mrvl-serial.txt     |    2 +-
> >> >>  arch/arm/boot/dts/mmp2-brownstone.dts              |    2 +-
> >> >>  arch/arm/boot/dts/mmp2.dtsi                        |   56 ++++++++++----------
> >> >>  arch/arm/boot/dts/pxa168-aspenite.dts              |    2 +-
> >> >>  arch/arm/boot/dts/pxa168.dtsi                      |   24 ++++----
> >> >>  arch/arm/boot/dts/pxa2xx.dtsi                      |   16 +++---
> >> >>  arch/arm/boot/dts/pxa3xx.dtsi                      |    2 +-
> >> >>  arch/arm/boot/dts/pxa910-dkb.dts                   |    2 +-
> >> >>  arch/arm/boot/dts/pxa910.dtsi                      |   27 +++++-----
> >> >>  arch/arm/mach-mmp/irq.c                            |   16 +++---
> >> >>  arch/arm/mach-mmp/mmp-dt.c                         |   28 +++++-----
> >> >>  arch/arm/mach-mmp/mmp2-dt.c                        |   16 +++---
> >> >>  arch/arm/mach-mmp/time.c                           |    2 +-
> >> >>  arch/arm/mach-pxa/pxa-dt.c                         |   14 +++---
> >> >>  drivers/i2c/busses/i2c-pxa.c                       |   10 ++--
> >> >>  drivers/mmc/host/sdhci-pxav2.c                     |    4 +-
> >> >>  drivers/mmc/host/sdhci-pxav3.c                     |    4 +-
> >> >>  drivers/rtc/rtc-sa1100.c                           |    4 +-
> >> >>  drivers/tty/serial/pxa.c                           |    4 +-
> >> >>  25 files changed, 144 insertions(+), 143 deletions(-)
> >> >
> >> > I agree with the need to change, however, this has been in the binding
> >> > documentation since v3.5.  I wish we had caught this when we decided
> >> > against using stock ticker symbols (not all stock markets use
> >> > alphabetical abbreviated names, not all companies are listed on any
> >> > stock exchange).
> >> >
> >> > To do this properly, the drivers are going to have to be compatible with
> >> > the old and the new names, and the binding docs updated to reflect the
> >> > legacy name and the preferred name.
> >> >
> >>
> >> It's better to only use the new names.
> >
> > In the dts{i}, yes.  But we don't want to break systems in the field
> > with "mrvl,..." compatible strings.  Therefore, at least the drivers
> > need an extra compatible string to support "mrvl,...".
> >
> > If it had just been since v3.9, it'd be different/simpler.  However,
> > several vendors have opted to use kernels newer than v3.5, which makes
> > this scenario a real possibility.
> >
> > thx,
> >
> > Jason.
> 
> Is there any vendor using DT for this Marvell chip? I think the answer is no.

Well, Daniel Drake spoke up for OLPC.  Does that count?

thx,

Jason.


  reply	other threads:[~2013-07-10 21:50 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-09  6:42 [PATCH V3 0/3] bring up pxa988 with DT Neil Zhang
2013-07-09  6:42 ` [PATCH V3 1/3] dts: change Marvell prefix to 'marvell' Neil Zhang
2013-07-09 12:49   ` Jason Cooper
2013-07-10  7:25     ` Neil Zhang
2013-07-10 12:20       ` Jason Cooper
2013-07-10 14:41         ` Daniel Drake
2013-07-10  8:19     ` Haojian Zhuang
2013-07-10 12:24       ` Jason Cooper
2013-07-10 14:08         ` Haojian Zhuang
2013-07-10 21:50           ` Jason Cooper [this message]
2013-07-11 23:54             ` Haojian Zhuang
2013-07-12 15:10               ` Daniel Drake
2013-07-12 15:57                 ` Jason Cooper
2013-07-12 16:05                   ` Daniel Drake
2013-07-12 16:14                     ` Jason Cooper
2013-07-13  0:35                 ` Haojian Zhuang
2013-07-13 14:30                   ` Daniel Drake
2013-07-13 19:56             ` Olof Johansson
2013-07-15  4:39               ` Jason Cooper
2013-07-10 20:50     ` Matt Sealey
2013-07-10 21:49       ` Jason Cooper
2013-07-11 11:20         ` Neil Zhang
2013-07-14 19:29           ` Arnd Bergmann
2013-07-17 13:37             ` Neil Zhang
2013-07-09  6:42 ` [PATCH V3 2/3] clocksource: mmp: support CLOCKSOURCE OF DECLARE Neil Zhang
2013-07-09 16:14   ` Thomas Petazzoni
2013-07-09 21:16     ` Arnd Bergmann
2013-07-10  5:58       ` Haojian Zhuang
2013-07-11 11:23         ` Neil Zhang
2013-07-11 23:51           ` Haojian Zhuang
2013-07-09  6:42 ` [PATCH V3 3/3] ARM: mmp: bring up pxa988 with device tree support Neil Zhang
2013-07-09 22:05   ` Arnd Bergmann
2013-07-11 11:35     ` Neil Zhang

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=20130710215041.GR11908@titan.lakedaemon.net \
    --to=jason@lakedaemon.net \
    --cc=arnd@arndb.de \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=grant.likely@linaro.org \
    --cc=haojian.zhuang@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=zhangwm@marvell.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

all inboxes | Powered by JetHome®