linux-iio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Stephen Boyd <swboyd@chromium.org>
Cc: linux-kernel@vger.kernel.org, linux-iio@vger.kernel.org,
	Hartmut Knaack <knaack.h@gmx.de>,
	Lars-Peter Clausen <lars@metafoo.de>,
	Peter Meerwald-Stadler <pmeerw@pmeerw.net>,
	Rob Herring <robh+dt@kernel.org>,
	Douglas Anderson <dianders@chromium.org>,
	Daniel Campello <campello@chromium.org>
Subject: Re: [PATCH 0/3] Some sx9310 iio driver updates
Date: Sun, 26 Jul 2020 12:56:36 +0100	[thread overview]
Message-ID: <20200726125636.3aa003ad@archlinux> (raw)
In-Reply-To: <20200724213329.899216-1-swboyd@chromium.org>

On Fri, 24 Jul 2020 14:33:24 -0700
Stephen Boyd <swboyd@chromium.org> wrote:

> These patches are only related because I'm looking at this driver. The
> first one resends the DT binding for the driver that was merged in
> v5.8-rc1 with a small change to update for proper regulators. The second
> patch fixes a few printks that are missing newlines and should be
> totally non-trivial to apply. The third patch changes whoami to unsigned
> to avoid confusing. The fourth patch drops channel_users because it's
> unused. The final patch adds support to enable the svdd and vdd supplies
> so that this driver can work on a board I have where the svdd supply
> isn't enabled at boot and needs to be turned on before this driver
> starts to communicate with the chip.
Hi Stephen,

I clearly made a mess of picking this driver up in the first place.

Anyhow, we now have two series in flight for the driver that, whilst
mostly independent (I think) will result in at least some fuzz.
If possible could you work with Daniel to send me one single series
with all the changes?

Thanks,

Jonathan

> 
> Changes from v1:
>  * Two new patches for whoami and channel_uesrs
>  * Use bulk regulator APIs for supplies patch
>  * Support both regulators
> 
> Daniel Campello (1):
>   dt-bindings: iio: Add bindings for sx9310 sensor
> 
> Stephen Boyd (4):
>   iio: sx9310: Add newlines to printks
>   iio: sx9310: whoami is unsigned
>   iio: sx9310: Drop channel_users[]
>   iio: sx9310: Enable vdd and svdd regulators at probe
> 
>  .../iio/proximity/semtech,sx9310.yaml         | 60 +++++++++++++++++++
>  drivers/iio/proximity/sx9310.c                | 46 +++++++++++---
>  2 files changed, 97 insertions(+), 9 deletions(-)
>  create mode 100644 Documentation/devicetree/bindings/iio/proximity/semtech,sx9310.yaml
> 
> Cc: Hartmut Knaack <knaack.h@gmx.de>
> Cc: Lars-Peter Clausen <lars@metafoo.de>
> Cc: Peter Meerwald-Stadler <pmeerw@pmeerw.net>
> Cc: Rob Herring <robh+dt@kernel.org>
> Cc: Douglas Anderson <dianders@chromium.org>
> Cc: Daniel Campello <campello@chromium.org>
> 
> base-commit: b3a9e3b9622ae10064826dccb4f7a52bd88c7407


  parent reply	other threads:[~2020-07-26 11:56 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-24 21:33 [PATCH 0/3] Some sx9310 iio driver updates Stephen Boyd
2020-07-24 21:33 ` [PATCH v2 1/5] dt-bindings: iio: Add bindings for sx9310 sensor Stephen Boyd
2020-07-24 21:36   ` Stephen Boyd
2020-07-24 21:33 ` [PATCH v2 2/5] iio: sx9310: Add newlines to printks Stephen Boyd
2020-07-24 21:33 ` [PATCH v2 3/5] iio: sx9310: whoami is unsigned Stephen Boyd
2020-07-24 21:56   ` Doug Anderson
2020-07-25  0:14   ` Daniel Campello
2020-07-24 21:33 ` [PATCH v2 4/5] iio: sx9310: Drop channel_users[] Stephen Boyd
2020-07-24 21:57   ` Doug Anderson
2020-07-25  0:17   ` Daniel Campello
2020-07-24 21:33 ` [PATCH v2 5/5] iio: sx9310: Enable vdd and svdd regulators at probe Stephen Boyd
2020-07-24 22:02   ` Doug Anderson
2020-07-25  0:38     ` Stephen Boyd
2020-07-26 11:56 ` Jonathan Cameron [this message]
2020-07-27 20:02   ` [PATCH 0/3] Some sx9310 iio driver updates Stephen Boyd
  -- strict thread matches above, loose matches on Subject: below --
2020-07-23 23:03 Stephen Boyd

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=20200726125636.3aa003ad@archlinux \
    --to=jic23@kernel.org \
    --cc=campello@chromium.org \
    --cc=dianders@chromium.org \
    --cc=knaack.h@gmx.de \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pmeerw@pmeerw.net \
    --cc=robh+dt@kernel.org \
    --cc=swboyd@chromium.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).