From: Jacek Anaszewski <j.anaszewski@samsung.com>
To: linux-iio@vger.kernel.org
Subject: Re: [PATCH 2/2] iio: ak8975: Implement data ready interrupt handling
Date: Tue, 07 May 2013 11:17:11 +0200 [thread overview]
Message-ID: <kmagqi$guj$2@ger.gmane.org> (raw)
In-Reply-To: <5187DF32.7060107@kernel.org>
On 05/06/2013 06:49 PM, Jonathan Cameron wrote:
> On 04/16/2013 03:37 PM, Jacek Anaszewski wrote:
>> Implement "data ready" interrupt handling in addition to the
>> two existing read modes - DRDY GPIO polling and ST1 register
>> DRDY bit polling.
>>
>> Signed-off-by: Jacek Anaszewski<j.anaszewski@samsung.com>
>> Signed-off-by: Kyungmin Park<kyungmin.park@samsung.com>
>> Cc: Andrew Chew<achew@nvidia.com>
>
> Allowing either the gpio or the interrupt is a little ususual, but
> I suppose does avoid having to change existing users to gain interrupt
> support (if their gpio subsystem happens to support interrupts).
Thanks for the review. I am going to send new series promptly.
Regarding the gpio issue - I can imagine the situation when there is no
available interrupt pin at the CPU, as they were all connected to the
other devices, there are some free general purpose pins though. It is
always better to have a possibility to periodically read the state of
such a pin, instead of performing cycling I2C transmission to check the
status of DRDY bit in the ST1 register, which is a fallback in the driver.
Thanks,
Jacek Anaszewski
prev parent reply other threads:[~2013-05-07 9:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-16 14:37 iio:magnetometer:ak8975: Add support for DT and interrupt handling Jacek Anaszewski
2013-04-16 14:37 ` [PATCH 1/2] iio: ak8975: Add support for gpios DT property Jacek Anaszewski
2013-05-06 16:44 ` Jonathan Cameron
2013-05-06 18:11 ` Lars-Peter Clausen
2013-04-16 14:37 ` [PATCH 2/2] iio: ak8975: Implement data ready interrupt handling Jacek Anaszewski
2013-05-06 16:49 ` Jonathan Cameron
2013-05-07 9:17 ` Jacek Anaszewski [this message]
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='kmagqi$guj$2@ger.gmane.org' \
--to=j.anaszewski@samsung.com \
--cc=linux-iio@vger.kernel.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