From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Jonathan Cameron <jic23@kernel.org>
Cc: Hartmut Knaack <knaack.h@gmx.de>,
Lars-Peter Clausen <lars@metafoo.de>,
Peter Meerwald-Stadler <pmeerw@pmeerw.net>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>, <devicetree@vger.kernel.org>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Subject: Re: [PATCH v2 2/7] iio: adc: max1027: Make it optional to use interrupts
Date: Mon, 7 Oct 2019 12:01:22 +0200 [thread overview]
Message-ID: <20191007120122.6d41532f@xps13> (raw)
In-Reply-To: <20191006111837.33fdfe25@archlinux>
Hi Jonathan,
Jonathan Cameron <jic23@kernel.org> wrote on Sun, 6 Oct 2019 11:18:37
+0100:
> On Thu, 3 Oct 2019 19:33:56 +0200
> Miquel Raynal <miquel.raynal@bootlin.com> wrote:
>
> > The chip has a 'start conversion' and a 'end of conversion' pair of
> > pins. They can be used but this is absolutely not mandatory as regular
> > polling of the value is totally fine with the current internal
> > clocking setup. Turn the interrupts optional and do not error out if
> > they are not inquired in the device tree. This has the effect to
> > prevent triggered buffers use though.
> >
> > Signed-off-by: Miquel Raynal <miquel.raynal@bootlin.com>
>
> Hmm. I haven't looked a this in a great deal of depth but if we support
> single channel reads it should be possible to allow the use of a
> trigger from elsewhere. Looks like a fair bit of new code would be needed
> to support that though. So perhaps this is a good first step.
>
> It's a bit annoying that the hardware doesn't provide a EOC bit
> anywhere in the registers. That would have allowed us to be a bit
> cleverer.
I totally agree. Actually, this chip does not support any 'register
read', the only things we can read are measures (temperature/voltages).
Thanks,
Miquèl
WARNING: multiple messages have this Message-ID (diff)
From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Jonathan Cameron <jic23@kernel.org>
Cc: Hartmut Knaack <knaack.h@gmx.de>,
Lars-Peter Clausen <lars@metafoo.de>,
Peter Meerwald-Stadler <pmeerw@pmeerw.net>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
devicetree@vger.kernel.org, linux-iio@vger.kernel.org,
linux-kernel@vger.kernel.org,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Subject: Re: [PATCH v2 2/7] iio: adc: max1027: Make it optional to use interrupts
Date: Mon, 7 Oct 2019 12:01:22 +0200 [thread overview]
Message-ID: <20191007120122.6d41532f@xps13> (raw)
In-Reply-To: <20191006111837.33fdfe25@archlinux>
Hi Jonathan,
Jonathan Cameron <jic23@kernel.org> wrote on Sun, 6 Oct 2019 11:18:37
+0100:
> On Thu, 3 Oct 2019 19:33:56 +0200
> Miquel Raynal <miquel.raynal@bootlin.com> wrote:
>
> > The chip has a 'start conversion' and a 'end of conversion' pair of
> > pins. They can be used but this is absolutely not mandatory as regular
> > polling of the value is totally fine with the current internal
> > clocking setup. Turn the interrupts optional and do not error out if
> > they are not inquired in the device tree. This has the effect to
> > prevent triggered buffers use though.
> >
> > Signed-off-by: Miquel Raynal <miquel.raynal@bootlin.com>
>
> Hmm. I haven't looked a this in a great deal of depth but if we support
> single channel reads it should be possible to allow the use of a
> trigger from elsewhere. Looks like a fair bit of new code would be needed
> to support that though. So perhaps this is a good first step.
>
> It's a bit annoying that the hardware doesn't provide a EOC bit
> anywhere in the registers. That would have allowed us to be a bit
> cleverer.
I totally agree. Actually, this chip does not support any 'register
read', the only things we can read are measures (temperature/voltages).
Thanks,
Miquèl
next prev parent reply other threads:[~2019-10-07 10:01 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-03 17:33 [PATCH v2 0/7] Introduce max12xx ADC support Miquel Raynal
2019-10-03 17:33 ` Miquel Raynal
2019-10-03 17:33 ` [PATCH v2 1/7] iio: adc: max1027: Add debugfs register read support Miquel Raynal
2019-10-03 17:33 ` Miquel Raynal
2019-10-06 10:04 ` Jonathan Cameron
2019-10-06 10:04 ` Jonathan Cameron
2019-10-07 10:00 ` Miquel Raynal
2019-10-07 10:00 ` Miquel Raynal
2019-10-12 13:56 ` Jonathan Cameron
2019-10-12 13:56 ` Jonathan Cameron
2019-10-03 17:33 ` [PATCH v2 2/7] iio: adc: max1027: Make it optional to use interrupts Miquel Raynal
2019-10-03 17:33 ` Miquel Raynal
2019-10-06 10:18 ` Jonathan Cameron
2019-10-06 10:18 ` Jonathan Cameron
2019-10-07 10:01 ` Miquel Raynal [this message]
2019-10-07 10:01 ` Miquel Raynal
2019-10-07 11:44 ` Jonathan Cameron
2019-10-07 11:44 ` Jonathan Cameron
2019-10-03 17:33 ` [PATCH v2 3/7] iio: adc: max1027: Reset the device at probe time Miquel Raynal
2019-10-03 17:33 ` Miquel Raynal
2019-10-03 17:33 ` [PATCH v2 4/7] iio: adc: max1027: Prepare the introduction of different resolutions Miquel Raynal
2019-10-03 17:33 ` Miquel Raynal
2019-10-06 10:22 ` Jonathan Cameron
2019-10-06 10:22 ` Jonathan Cameron
2019-10-07 10:03 ` Miquel Raynal
2019-10-07 10:03 ` Miquel Raynal
2019-10-03 17:33 ` [PATCH v2 5/7] iio: adc: max1027: Introduce 12-bit devices support Miquel Raynal
2019-10-03 17:33 ` Miquel Raynal
2019-10-06 10:24 ` Jonathan Cameron
2019-10-06 10:24 ` Jonathan Cameron
2019-10-03 17:34 ` [PATCH v2 6/7] dt-bindings: iio: adc: max1027: Mark interrupts as optional Miquel Raynal
2019-10-03 17:34 ` Miquel Raynal
2019-10-03 17:34 ` [PATCH v2 7/7] dt-bindings: iio: adc: max1027: Document max12xx series compatibles Miquel Raynal
2019-10-03 17:34 ` Miquel Raynal
2019-10-06 10:27 ` Jonathan Cameron
2019-10-06 10:27 ` Jonathan Cameron
2019-10-07 10:04 ` Miquel Raynal
2019-10-07 10:04 ` Miquel Raynal
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=20191007120122.6d41532f@xps13 \
--to=miquel.raynal@bootlin.com \
--cc=devicetree@vger.kernel.org \
--cc=jic23@kernel.org \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pmeerw@pmeerw.net \
--cc=robh+dt@kernel.org \
--cc=thomas.petazzoni@bootlin.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.