From: Jonathan Cameron <Jonathan.Cameron@Huawei.com>
To: George Stark <gnstark@sberdevices.ru>
Cc: <jic23@kernel.org>, <lars@metafoo.de>,
<neil.armstrong@linaro.org>, <khilman@baylibre.com>,
<jbrunet@baylibre.com>, <martin.blumenstingl@googlemail.com>,
<andriy.shevchenko@linux.intel.com>, <nuno.sa@analog.com>,
<linux-iio@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>,
<linux-amlogic@lists.infradead.org>, <kernel@sberdevices.ru>
Subject: Re: [PATCH v3 0/5] meson saradc: add iio channels to read channel 7 mux inputs
Date: Sun, 2 Jul 2023 17:11:36 +0800 [thread overview]
Message-ID: <20230702171136.00003950@Huawei.com> (raw)
In-Reply-To: <20230627224017.1724097-1-gnstark@sberdevices.ru>
On Wed, 28 Jun 2023 01:37:13 +0300
George Stark <gnstark@sberdevices.ru> wrote:
> From: George Stark <GNStark@sberdevices.ru>
>
> Changelog:
>
> v1->v2:
> split refactoring patch [1] into 4 smaller patches, fix comment style
>
> [1] https://lore.kernel.org/lkml/20230621062715.455652-2-gnstark@sberdevices.ru/
>
> v2->v3:
> remove patch 'meson saradc: unite iio channel array definitions' [1] after discussion
>
> patch 'meson saradc: add enum for iio channel array indexes'
> - change enum items prefix from INDEX_ to NUM_ since name 'channel index' is
> more relevant to channel array index in iio world and with 2 tables our array index is
> not always equal to channel number
> - resolve conflicts after deleting [1]
> - update commit message, previous patch [2]
> - return channel number for temp channel. It wasn't used and isn't used currently
> but may need later
>
> patch meson saradc: support reading from channel 7 mux inputs
> - resolve conflicts after deleting [1]
> - update commit message, previous patch [3]
> - add routine find_channel_by_num to get channel by channel number
>
> [1] https://lore.kernel.org/lkml/20230623022334.791026-4-gnstark@sberdevices.ru/
> [2] https://lore.kernel.org/lkml/20230623022334.791026-5-gnstark@sberdevices.ru/
> [3] https://lore.kernel.org/lkml/20230623022334.791026-7-gnstark@sberdevices.ru/
>
> George Stark (5):
> meson saradc: move enums declaration before variables declaration
> meson saradc: move meson_sar_adc_set_chan7_mux routine upper
> meson saradc: add enum for iio channel numbers
> meson saradc: add channel labels
> meson saradc: support reading from channel 7 mux inputs
iio: adc: meson: ....
to make it clear these are changing the IIO driver.
Jonathan
`
>
> drivers/iio/adc/meson_saradc.c | 165 +++++++++++++++++++++++++--------
> 1 file changed, 126 insertions(+), 39 deletions(-)
>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2023-07-02 9:12 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-27 22:37 [PATCH v3 0/5] meson saradc: add iio channels to read channel 7 mux inputs George Stark
2023-06-27 22:37 ` [PATCH v3 1/5] meson saradc: move enums declaration before variables declaration George Stark
2023-07-02 9:14 ` Jonathan Cameron
2023-07-04 0:39 ` George Stark
2023-06-27 22:37 ` [PATCH v3 2/5] meson saradc: move meson_sar_adc_set_chan7_mux routine upper George Stark
2023-06-27 22:37 ` [PATCH v3 3/5] meson saradc: add enum for iio channel numbers George Stark
2023-06-27 22:37 ` [PATCH v3 4/5] meson saradc: add channel labels George Stark
2023-07-02 9:16 ` Jonathan Cameron
2023-07-04 1:32 ` George Stark
2023-06-27 22:37 ` [PATCH v3 5/5] meson saradc: support reading from channel 7 mux inputs George Stark
2023-06-28 10:06 ` Andy Shevchenko
2023-07-02 9:21 ` Jonathan Cameron
2023-07-03 19:39 ` Martin Blumenstingl
2023-07-04 8:08 ` George Stark
[not found] ` <6ee38b3a-8e2f-15d6-f7bd-06ef567d2b68@sberdevices.ru>
2023-07-05 8:04 ` Jonathan Cameron
2023-07-02 9:11 ` 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=20230702171136.00003950@Huawei.com \
--to=jonathan.cameron@huawei.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=gnstark@sberdevices.ru \
--cc=jbrunet@baylibre.com \
--cc=jic23@kernel.org \
--cc=kernel@sberdevices.ru \
--cc=khilman@baylibre.com \
--cc=lars@metafoo.de \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.blumenstingl@googlemail.com \
--cc=neil.armstrong@linaro.org \
--cc=nuno.sa@analog.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).