From: khali@linux-fr.org (Jean Delvare)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH 0/3] DT support for ST micro accelerometers and gyroscopes
Date: Sat, 30 Nov 2013 14:04:02 +0100 [thread overview]
Message-ID: <20131130140402.21abae28@endymion.delvare> (raw)
In-Reply-To: <5299D3BA.8080700@kernel.org>
On Sat, 30 Nov 2013 12:02:02 +0000, Jonathan Cameron wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 11/25/13 09:40, Maxime Ripard wrote:
> > Hi Jonathan,
> >
> > On Sun, Nov 24, 2013 at 09:00:49PM +0000, Jonathan Cameron wrote:
> >> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
> >>
> >> On 11/21/13 13:14, Maxime Ripard wrote:
> >>> Hi Denis,
> >>>
> >>> On Thu, Nov 21, 2013 at 12:41:24PM +0100, Denis CIOCCA wrote:
> >>>> only one point: it's possible to use the same names with DT? (using _ instead of -)
> >>>
> >>> Yes, it is, but only for i2c as far as I'm aware, and usually the DT compatibles are with - as a separator (I
> >>> looked into the ePAPR, but couldn't get any explanations or requirements on this, even though it's used in all
> >>> of their examples)
> >>
> >> In other discussions, where the defacto i2c device tree bindings have been followed, the conclusion has been that
> >> to change to a - from _ would result in userspace ABI changes, so whilst no one wants _ the discussion has
> >> concluded we can't really avoid it.
> >
> > What kind of userspace ABI changes are we talking about?
> IIRC:
>
> i2c has a generic binding that matches to the name bit of the i2c_device_id
> array. That is then exported in sysfs. There are quite a lot of instances
> of underscores out there in these names. Thus unforutnately they can't
> be changed without possibly breaking userspace. Typically those same names
> are also output by IIO though obviously we could keep that the same whilst
> changing the dt binding.
>
> Also the i2c binding allows binding after dropping the vendor prefix which
> is even more 'interesting'. See of_modialias_node in drivers/of/base.c
>
> I'd therefore argue in favour of just leaving the underscores in existing
> drivers as a nasty bit of legacy and doing our best to not introduce any
> new ones!
I don't know what is the problem with underscores, but please note that
hwmon i2c devices are NOT allowed to have dashes in their name because
that would break libsensors.
--
Jean Delvare
next prev parent reply other threads:[~2013-11-30 13:04 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-19 15:50 [RFC PATCH 0/3] DT support for ST micro accelerometers and gyroscopes Maxime Ripard
2013-11-19 15:50 ` [RFC PATCH 1/3] iio: accel: Add device tree probing for STMicro accelerometers Maxime Ripard
2013-11-30 12:04 ` Jonathan Cameron
2013-11-30 13:42 ` Maxime Ripard
2013-11-19 15:50 ` [RFC PATCH 2/3] iio: accel: Add device tree probing for STMicro gyroscopes Maxime Ripard
2013-11-19 15:50 ` [RFC PATCH 3/3] ARM: cfa10057: Add the accelerometer and gyroscope to the device tree Maxime Ripard
2013-11-21 11:41 ` [RFC PATCH 0/3] DT support for ST micro accelerometers and gyroscopes Denis CIOCCA
2013-11-21 13:14 ` Maxime Ripard
2013-11-24 21:00 ` Jonathan Cameron
2013-11-25 8:37 ` Denis CIOCCA
2013-11-25 9:40 ` Maxime Ripard
2013-11-30 12:02 ` Jonathan Cameron
2013-11-30 13:04 ` Jean Delvare [this message]
2013-12-03 21:29 ` Maxime Ripard
2013-12-03 21:39 ` Jean Delvare
2013-11-30 14:13 ` Maxime Ripard
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=20131130140402.21abae28@endymion.delvare \
--to=khali@linux-fr.org \
--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).