From: Lars Poeschel <poeschel@lemonage.de>
To: Mark Rutland <mark.rutland@arm.com>
Cc: Lars Poeschel <larsi@wh2.tu-dresden.de>,
"grant.likely@linaro.org" <grant.likely@linaro.org>,
"linus.walleij@linaro.org" <linus.walleij@linaro.org>,
"rob.herring@calxeda.com" <rob.herring@calxeda.com>,
Pawel Moll <Pawel.Moll@arm.com>,
"swarren@wwwdotorg.org" <swarren@wwwdotorg.org>,
"ian.campbell@citrix.com" <ian.campbell@citrix.com>,
"rob@landley.net" <rob@landley.net>,
"arnd@arndb.de" <arnd@arndb.de>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>
Subject: Re: [PATCH 1/2] gpio: mcp23s08: rename the device tree property
Date: Fri, 23 Aug 2013 17:22:10 +0200 [thread overview]
Message-ID: <201308231722.10392.poeschel@lemonage.de> (raw)
In-Reply-To: <20130823142421.GK25856@e106331-lin.cambridge.arm.com>
On Friday 23 August 2013 at 16:24:21, Mark Rutland wrote:
> On Thu, Aug 22, 2013 at 10:56:17AM +0100, Lars Poeschel wrote:
> > From: Lars Poeschel <poeschel@lemonage.de>
> >
> > The device tree property should be more descriptive.
> > microchip seems more reasonable than mcp. As there are no
> > in tree users of this property, so the rename can still be
> > done without pain.
>
> Are there definitely no users? I see there are no dts with a
> "mcp,mcp23***" compatible string, but are there any boards already out
> there with this hardware that someone might be using and a currently
> release kernel supports?
What do you mean by "release"? The device tree support for the gpio-
mcp23s08 driver and thus the "mcp" string came in with v3.9. This is stable
but not longterm.
> With the bcm/broadcom => brcm change, we marked the old vendor prefix as
> deprecated (but left the support code).
>
> If we can 100% guarantee no-one's using the compatible string, I'm happy
> to change it. Otherwise we just have to mark the old string as
> deprecated.
I am the developer of the device tree support for that driver and I am not
aware of any user, but surely I can not guarantee it.
I never imagined how hard it would be. ;-)
I presented both variants:
1.) simply add mcp to vendor-prefixes.txt
2.) change the driver to microchip and add microchip to vendor-prefixes.txt
May one of the maintainers decide which one to take or even take none of
the patches.
Or do you need a third variant with both strings in the driver and
microchip in vendor-prefixes?
Lars
next prev parent reply other threads:[~2013-08-23 15:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-22 9:56 Lars Poeschel
2013-08-22 9:56 ` [PATCH 2/2] of: add vendor prefix for Microchip Technology Inc Lars Poeschel
2013-08-23 14:20 ` Mark Rutland
2013-08-23 14:24 ` [PATCH 1/2] gpio: mcp23s08: rename the device tree property Mark Rutland
2013-08-23 15:22 ` Lars Poeschel [this message]
2013-08-23 16:48 ` Mark Rutland
2013-08-23 19:10 ` Linus Walleij
2013-08-25 10:06 ` Lars Poeschel
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=201308231722.10392.poeschel@lemonage.de \
--to=poeschel@lemonage.de \
--cc=Pawel.Moll@arm.com \
--cc=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=grant.likely@linaro.org \
--cc=ian.campbell@citrix.com \
--cc=larsi@wh2.tu-dresden.de \
--cc=linus.walleij@linaro.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=rob.herring@calxeda.com \
--cc=rob@landley.net \
--cc=swarren@wwwdotorg.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
all inboxes | Powered by JetHome®