linux-iio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Maxime Ripard <maxime.ripard@free-electrons.com>
To: Jonathan Cameron <jic23@kernel.org>
Cc: Shawn Guo <shawn.guo@linaro.org>,
	Denis Ciocca <denis.ciocca@st.com>,
	linux-iio@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	Alexandre Belloni <alexandre.belloni@free-electrons.com>,
	Brian Lilly <brian@crystalfontz.com>,
	Brent-Crosby <brent@crystalfontz.com>, Jim Wall <jimwall@q.com>
Subject: Re: [RFC PATCH 1/3] iio: accel: Add device tree probing for STMicro accelerometers
Date: Sat, 30 Nov 2013 14:42:47 +0100	[thread overview]
Message-ID: <20131130134247.GB3002@lukather> (raw)
In-Reply-To: <5299D444.30801@kernel.org>

[-- Attachment #1: Type: text/plain, Size: 1021 bytes --]

On Sat, Nov 30, 2013 at 12:04:20PM +0000, Jonathan Cameron wrote:
> On 11/19/13 15:50, Maxime Ripard wrote:
> > Add the compatibles supported by the st_sensors library. This uses kind
> > of a hack, since the st_sensors core will actively check at probe time
> > that the device name matches the one reported when using old style i2c
> > probing, and that this name will be different with device tree.
> > 
> > Signed-off-by: Maxime Ripard <maxime.ripard@free-electrons.com>
>
> Note that this is unnecessary give core i2c matching, until we have some
> more elements in the binding.  I'd certainly expect the interrupts
> on the relevant devices to be in the binding...

This interrupt DT thing has been stalled for monthes, I don't have any
hardware to test the interrupts, maybe we can just move forward and
wait for someone that have the need for the interrupts to do the work?

Maxime

-- 
Maxime Ripard, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2013-11-30 13:42 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 [this message]
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
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=20131130134247.GB3002@lukather \
    --to=maxime.ripard@free-electrons.com \
    --cc=alexandre.belloni@free-electrons.com \
    --cc=brent@crystalfontz.com \
    --cc=brian@crystalfontz.com \
    --cc=denis.ciocca@st.com \
    --cc=jic23@kernel.org \
    --cc=jimwall@q.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=shawn.guo@linaro.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).