From: Jonathan Cameron <jic23@kernel.org>
To: Peter Rosin <peda@axentia.se>
Cc: Vincent Whitchurch <vincent.whitchurch@axis.com>,
devicetree@vger.kernel.org, kernel@axis.com, lars@metafoo.de,
linux-iio@vger.kernel.org, robh+dt@kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/3] Add settle time support to iio-mux
Date: Sun, 17 Oct 2021 18:31:25 +0100 [thread overview]
Message-ID: <20211017183108.1797d416@jic23-huawei> (raw)
In-Reply-To: <7c14fabc-8811-5875-15a0-67884e2da78d@axentia.se>
On Sat, 9 Oct 2021 01:09:56 +0200
Peter Rosin <peda@axentia.se> wrote:
> Hi Vincent!
>
> On 2021-10-07 15:46, Vincent Whitchurch wrote:
> > On one of our boards we use gpio-mux with iio-mux to read voltages using an ADC
> > from a few different channels, and on this board the input voltage needs some
> > time to stabilize after a switch of the mux.
> >
> > This series add devicetree and driver support for this kind of hardware which
> > requries a settle time after muxing.
> >
> > v1 -> v2:
> > - Move property support to iio-mux and delay handling to mux core as suggested
> > by Peter.
> >
> > v1: https://lore.kernel.org/all/20211004153640.20650-1-vincent.whitchurch@axis.com/
> >
> > Vincent Whitchurch (3):
> > mux: add support for delay after muxing
> > dt-bindings: iio: io-channel-mux: Add property for settle time
> > iio: multiplexer: iio-mux: Support settle-time-us property
> >
> > .../iio/multiplexer/io-channel-mux.yaml | 5 +++
> > drivers/iio/multiplexer/iio-mux.c | 7 +++-
> > drivers/mux/core.c | 36 ++++++++++++++++---
> > include/linux/mux/consumer.h | 23 +++++++++---
> > include/linux/mux/driver.h | 4 +++
> > 5 files changed, 65 insertions(+), 10 deletions(-)
> >
>
> This looks really nice, thank you! The only question I see is if it should
> go via my (virtually unused) mux tree or via the iio tree. Yes, the meat is
> in mux/core.c, but I'm happy to just ack these patches and have Jonathan
> handle them. But, I'm also fine with handling it in the mux tree (but I'm
> getting old and forgetful, and it's been so many moons that I need to
> re-learn the steps).
>
> Jonathan, you or me? If you, you can add:
>
> Acked-by: Peter Rosin <peda@axentia.se>
I don't really mind, but the 4/3 and 5/3 have broken my b4 based flow + Rob
hasn't yet given an Ack on those two, so I'll not pick any of them up just yet.
I can sort out the two oddly numbered patches if Rob is happy, though they'll
probably not have the nice link tags that b4 automates.
Note Rob didn't actually say he was happy with patch 2 yet as far as I can tell.
Thanks,
Jonathan
>
> Cheers,
> Peter
next prev parent reply other threads:[~2021-10-17 17:27 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-07 13:46 [PATCH v2 0/3] Add settle time support to iio-mux Vincent Whitchurch
2021-10-07 13:46 ` [PATCH v2 1/3] mux: add support for delay after muxing Vincent Whitchurch
2021-10-07 13:46 ` [PATCH v2 2/3] dt-bindings: iio: io-channel-mux: Add property for settle time Vincent Whitchurch
2021-10-08 2:46 ` Rob Herring
2021-10-08 13:56 ` Vincent Whitchurch
2021-10-08 15:27 ` Peter Rosin
2021-10-08 19:13 ` Rob Herring
2021-10-08 22:11 ` [PATCH 4/3] dt-bindings: iio: io-channel-mux: add optional #io-channel-cells Peter Rosin
2021-10-19 21:25 ` Rob Herring
2021-10-08 22:11 ` [PATCH 5/3] dt-bindings: iio: io-channel-mux: allow duplicate channel, labels Peter Rosin
2021-10-19 21:25 ` Rob Herring
2021-10-20 16:49 ` Jonathan Cameron
2021-10-18 19:52 ` [PATCH v2 2/3] dt-bindings: iio: io-channel-mux: Add property for settle time Rob Herring
2021-10-07 13:46 ` [PATCH v2 3/3] iio: multiplexer: iio-mux: Support settle-time-us property Vincent Whitchurch
2021-10-08 19:19 ` [PATCH v2 0/3] Add settle time support to iio-mux Lars-Peter Clausen
2021-10-19 7:03 ` Lars-Peter Clausen
2021-10-21 19:39 ` Jonathan Cameron
2021-10-08 23:09 ` Peter Rosin
2021-10-17 17:31 ` Jonathan Cameron [this message]
2021-10-17 21:08 ` Peter Rosin
2021-10-18 20:13 ` 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=20211017183108.1797d416@jic23-huawei \
--to=jic23@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kernel@axis.com \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peda@axentia.se \
--cc=robh+dt@kernel.org \
--cc=vincent.whitchurch@axis.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 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).