From: Lorenzo Bianconi <lorenzo.bianconi83-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Jonathan Cameron <jic23-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Cc: linux-iio-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Lorenzo BIANCONI <lorenzo.bianconi-qxv4g6HH51o@public.gmane.org>,
Linus Walleij
<linus.walleij-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
Subject: Re: [PATCH 1/2] iio: imu: st_lsm6dsx: support open drain mode
Date: Sun, 25 Jun 2017 11:34:10 +0200 [thread overview]
Message-ID: <CAA2SeNJ5yPqMiW2tVSc9ZSC5Rt=Q+CRoMibzigjvPyw05Qsr5Q@mail.gmail.com> (raw)
In-Reply-To: <20170624210835.56ffdd1c-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
> On Wed, 21 Jun 2017 21:21:28 +0200
> Lorenzo Bianconi <lorenzo.bianconi83-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
>
>> Add open drain support in order to share requested IRQ line between
>> st_lsm6dsx device and other peripherals
>>
>> Signed-off-by: Lorenzo Bianconi <lorenzo.bianconi-qxv4g6HH51o@public.gmane.org>
> Issue when IRQF_RISING and open drain is set.
>
Hi Jonathan,
> Otherwise looks good.
>> ---
>> drivers/iio/imu/st_lsm6dsx/st_lsm6dsx_buffer.c | 17 +++++++++++++++++
>> 1 file changed, 17 insertions(+)
>>
>> diff --git a/drivers/iio/imu/st_lsm6dsx/st_lsm6dsx_buffer.c b/drivers/iio/imu/st_lsm6dsx/st_lsm6dsx_buffer.c
>> index 2a72acc6e049..e2737dc71b67 100644
>> --- a/drivers/iio/imu/st_lsm6dsx/st_lsm6dsx_buffer.c
>> +++ b/drivers/iio/imu/st_lsm6dsx/st_lsm6dsx_buffer.c
>> @@ -31,6 +31,8 @@
>> #include <linux/iio/iio.h>
>> #include <linux/iio/buffer.h>
>>
>> +#include <linux/platform_data/st_sensors_pdata.h>
>> +
>> #include "st_lsm6dsx.h"
>>
>> #define ST_LSM6DSX_REG_FIFO_THL_ADDR 0x06
>> @@ -39,6 +41,8 @@
>> #define ST_LSM6DSX_REG_FIFO_DEC_GXL_ADDR 0x08
>> #define ST_LSM6DSX_REG_HLACTIVE_ADDR 0x12
>> #define ST_LSM6DSX_REG_HLACTIVE_MASK BIT(5)
>> +#define ST_LSM6DSX_REG_PP_OD_ADDR 0x12
>> +#define ST_LSM6DSX_REG_PP_OD_MASK BIT(4)
>> #define ST_LSM6DSX_REG_FIFO_MODE_ADDR 0x0a
>> #define ST_LSM6DSX_FIFO_MODE_MASK GENMASK(2, 0)
>> #define ST_LSM6DSX_FIFO_ODR_MASK GENMASK(6, 3)
>> @@ -417,6 +421,8 @@ static const struct iio_buffer_setup_ops st_lsm6dsx_buffer_ops = {
>>
>> int st_lsm6dsx_fifo_setup(struct st_lsm6dsx_hw *hw)
>> {
>> + struct device_node *np = hw->dev->of_node;
>> + struct st_sensors_platform_data *pdata;
>> struct iio_buffer *buffer;
>> unsigned long irq_type;
>> bool irq_active_low;
>> @@ -444,6 +450,17 @@ int st_lsm6dsx_fifo_setup(struct st_lsm6dsx_hw *hw)
>> if (err < 0)
>> return err;
>>
>> + pdata = (struct st_sensors_platform_data *)hw->dev->platform_data;
>> + if ((np && of_property_read_bool(np, "drive-open-drain")) ||
>> + (pdata && pdata->open_drain)) {
>> + err = st_lsm6dsx_write_with_mask(hw, ST_LSM6DSX_REG_PP_OD_ADDR,
>> + ST_LSM6DSX_REG_PP_OD_MASK, 1);
>> + if (err < 0)
>> + return err;
>> +
>> + irq_type |= IRQF_SHARED;
>> + }
>> +
> In common with the mpu3050 which was the first driver in IIO to do open drain,
> I think you need to think about precedence as we allow for IRQF_RISING
> and IRQF_FALLING already. Open drain only allows for shared interrupts
> if IRQF_FALLING (I think)
>> err = devm_request_threaded_irq(hw->dev, hw->irq,
>> st_lsm6dsx_handler_irq,
>> st_lsm6dsx_handler_thread,
>
I have not got the difference between IRQF_RISING and IRQF_FALLING
when the irq line
is marked as shared (when open drain is enabled).
Looking at the code, mpu3050 gyro sensor does not support shared interrupts
with IRQF_RISING and IRQF_TRIGGER_HIGH. Is it a hw limitation?
Speaking with digital designer, lsm6dsx series allows open drain mode
even if the requested irq line
is IRQF_TRIGGER_HIGH or IRQF_RISING, we need to add a pull-down resistor.
Moreover ST framework already supports open drain if the requested
interrupt is IRQF_RISING.
Regards,
Lorenzo
--
UNIX is Sexy: who | grep -i blonde | talk; cd ~; wine; talk; touch;
unzip; touch; strip; gasp; finger; gasp; mount; fsck; more; yes; gasp;
umount; make clean; sleep
next prev parent reply other threads:[~2017-06-25 9:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-21 19:21 [PATCH 0/2] Add open drain support to st_lsm6dsx Lorenzo Bianconi
[not found] ` <20170621192129.10226-1-lorenzo.bianconi-qxv4g6HH51o@public.gmane.org>
2017-06-21 19:21 ` [PATCH 1/2] iio: imu: st_lsm6dsx: support open drain mode Lorenzo Bianconi
[not found] ` <20170621192129.10226-2-lorenzo.bianconi-qxv4g6HH51o@public.gmane.org>
2017-06-24 20:08 ` Jonathan Cameron
[not found] ` <20170624210835.56ffdd1c-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2017-06-25 9:34 ` Lorenzo Bianconi [this message]
[not found] ` <CAA2SeNJ5yPqMiW2tVSc9ZSC5Rt=Q+CRoMibzigjvPyw05Qsr5Q-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-06-25 16:01 ` Jonathan Cameron
2017-06-29 11:46 ` Linus Walleij
2017-06-21 19:21 ` [PATCH 2/2] dt-bindings: " Lorenzo Bianconi
[not found] ` <20170621192129.10226-3-lorenzo.bianconi-qxv4g6HH51o@public.gmane.org>
2017-06-25 16:03 ` Jonathan Cameron
2017-06-26 18:24 ` Rob Herring
2017-06-30 18:22 ` Jonathan Cameron
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='CAA2SeNJ5yPqMiW2tVSc9ZSC5Rt=Q+CRoMibzigjvPyw05Qsr5Q@mail.gmail.com' \
--to=lorenzo.bianconi83-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=jic23-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=linus.walleij-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
--cc=linux-iio-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=lorenzo.bianconi-qxv4g6HH51o@public.gmane.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).