From: Jonathan Cameron <jic23@jic23.retrosnub.co.uk>
To: Gwendal Grignou <gwendal@chromium.org>
Cc: robh+dt@kernel.org, lars@metafoo.de, swboyd@chromium.org,
andy.shevchenko@gmail.com, linux-iio@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH v7 0/5] Expand Semtech SAR Sensors support
Date: Thu, 16 Dec 2021 16:02:04 +0000 [thread overview]
Message-ID: <20211216160153.2a523f46@jic23-huawei> (raw)
In-Reply-To: <20211216155015.7013eff9@jic23-huawei>
On Thu, 16 Dec 2021 15:50:29 +0000
Jonathan Cameron <jic23@jic23.retrosnub.co.uk> wrote:
> On Fri, 10 Dec 2021 11:23:23 -0800
> Gwendal Grignou <gwendal@chromium.org> wrote:
>
> > Add a new Semtech SAR sensor SX9324.
> > Instead of recopying 1/3 of the sx9310 driver, move common code in a new
> > file. It will be used again for the next sensor, SX9360.
>
> Series applied to the togreg branch of iio.git and pushed out as testing
> to let 0-day have a poke at it and see what it can find that we missed.
>
And pulled out again. Just noticed an issue with docs not matching
the actual ABI.
> Thanks,
>
> Jonathan
>
> >
> > Major changes in v7:
> > Fix one remaining syntax error in device tree binding documentation.
> >
> > Major changes in v6:
> > Fix syntax errors in device tree binding documentation.
> > Drop of_match_ptr and ACPI_PTR protections.
> > Fix unused variable warning.
> >
> > Major changes in v5:
> > Use iwyu to cleanup include files.
> > Use dev_err_probe() in probe routine
> > Add attribute to shift irq status register, not common among all
> > sensors.
> > Fix long line.
> >
> > Major changes in v4:
> > Use chip_info instead of info in common data.
> > Returns an error when setting negative sysfs entries
> > Fix cut and paste errors, credit.
> >
> > Major changes in v3:
> > Fix some error in binding descriptions and setting
> > Fix invalid register constant name.
> >
> > Major changes in v2:
> > Better interface between common code and drivers
> > Document SX9324 phase configuration
> >
> > Gwendal Grignou (5):
> > iio: sx9310: Add frequency in read_avail
> > iio: sx9310: Extract common Semtech sensor logic
> > iio: proximity: Add SX9324 support
> > dt-bindings: iio: Add sx9324 binding
> > iio: sx9324: Add dt_binding support
> >
> > .../ABI/testing/sysfs-bus-iio-sx9324 | 28 +
> > .../iio/proximity/semtech,sx9324.yaml | 161 +++
> > drivers/iio/proximity/Kconfig | 18 +
> > drivers/iio/proximity/Makefile | 2 +
> > drivers/iio/proximity/sx9310.c | 714 ++---------
> > drivers/iio/proximity/sx9324.c | 1076 +++++++++++++++++
> > drivers/iio/proximity/sx_common.c | 576 +++++++++
> > drivers/iio/proximity/sx_common.h | 163 +++
> > 8 files changed, 2127 insertions(+), 611 deletions(-)
> > create mode 100644 Documentation/ABI/testing/sysfs-bus-iio-sx9324
> > create mode 100644 Documentation/devicetree/bindings/iio/proximity/semtech,sx9324.yaml
> > create mode 100644 drivers/iio/proximity/sx9324.c
> > create mode 100644 drivers/iio/proximity/sx_common.c
> > create mode 100644 drivers/iio/proximity/sx_common.h
> >
>
prev parent reply other threads:[~2021-12-16 15:56 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-10 19:23 [PATCH v7 0/5] Expand Semtech SAR Sensors support Gwendal Grignou
2021-12-10 19:23 ` [PATCH v7 1/5] iio: sx9310: Add frequency in read_avail Gwendal Grignou
2021-12-15 1:06 ` Stephen Boyd
2021-12-10 19:23 ` [PATCH v7 2/5] iio: sx9310: Extract common Semtech sensor logic Gwendal Grignou
2021-12-15 1:11 ` Stephen Boyd
2021-12-10 19:23 ` [PATCH v7 3/5] iio: proximity: Add SX9324 support Gwendal Grignou
2021-12-15 1:11 ` Stephen Boyd
2021-12-16 16:04 ` Jonathan Cameron
2021-12-10 19:23 ` [PATCH v7 4/5] dt-bindings: iio: Add sx9324 binding Gwendal Grignou
2021-12-14 16:08 ` Rob Herring
2021-12-15 1:03 ` Stephen Boyd
2021-12-10 19:23 ` [PATCH v7 5/5] iio: sx9324: Add dt_binding support Gwendal Grignou
2021-12-15 1:13 ` Stephen Boyd
2021-12-18 0:18 ` Gwendal Grignou
2021-12-16 15:50 ` [PATCH v7 0/5] Expand Semtech SAR Sensors support Jonathan Cameron
2021-12-16 16:02 ` Jonathan Cameron [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=20211216160153.2a523f46@jic23-huawei \
--to=jic23@jic23.retrosnub.co.uk \
--cc=andy.shevchenko@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=gwendal@chromium.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--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).