From: denis.ciocca@st.com (Denis CIOCCA)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH 0/3] DT support for ST micro accelerometers and gyroscopes
Date: Mon, 25 Nov 2013 09:37:26 +0100 [thread overview]
Message-ID: <52930C46.801@st.com> (raw)
In-Reply-To: <52926901.9080004@kernel.org>
Hi Jonathan,
>> 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.
Ok, I understood the point. Thanks,
Denis
next prev parent reply other threads:[~2013-11-25 8:37 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 [this message]
2013-11-25 9:40 ` Maxime Ripard
2013-11-30 12:02 ` Jonathan Cameron
2013-11-30 13:04 ` Jean Delvare
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=52930C46.801@st.com \
--to=denis.ciocca@st.com \
--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).