public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: William Breathitt Gray <william.gray@linaro.org>
Cc: Lars-Peter Clausen <lars@metafoo.de>,
	linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
	Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Subject: Re: [PATCH v5 0/6] Migrate STX104 to the regmap API
Date: Fri, 7 Apr 2023 17:49:31 +0100	[thread overview]
Message-ID: <20230407174841.2ca510f5@jic23-huawei> (raw)
In-Reply-To: <cover.1680790580.git.william.gray@linaro.org>

On Thu,  6 Apr 2023 10:40:09 -0400
William Breathitt Gray <william.gray@linaro.org> wrote:

Series applied to the togreg branch of iio.git and pushed out initially as
testing.  If anyone wants to offer tags / remaining comments there will
still be a few days before I push this out in a non rebasing form.

Thanks,

Jonathan


> Changes in v5:
>  - Explicitly check for negative val for IIO_CHAN_INFO_RAW case in
>    stx104_write_raw(); this avoids the explicit case previously used
>  - Use U16_MAX rather than hardcoding unsigned 16-bit maximum value
>  - Improve ADC conversion comment format and use proper SI units format
> Changes in v4:
>  - Fix race conditions in stx104_read_raw() and stx104_write_raw() by
>    utilizing a mutex
>  - Improve indentation in stx104_write_raw() by bailing out early if
>    chan->output is false in for the IIO_CHAN_INFO_RAW case
>  - Remove regmap_config max_register lines as superfluous
>  - Utilize BIT() for gain calculation in stx104_read_raw()
> Changes in v3:
>  - Add STX104_ prefixes to defines to avoid potential name classes
>  - Rename SAME_CHANNEL() to STX104_SINGLE_CHANNEL() to convey intention
>    better
>  - Utilize u8_encode_bits() to define STX104_SOFTWARE_TRIGGER
>  - Adjust to utilize reg_base members in regmap_config structures
>  - Fix off-by-one errors in aio_data_wr_ranges[], aio_data_rd_ranges[],
>    and aio_data_regmap_config max_register
>  - Inline gpio_config initialization to avoid zeroing it at declaration
>  - Add blank lines between register map init blocks for clarity
>  - Utilize regmap_read_poll_timeout() for ADC conversion status poll
> Changes in v2:
>  - Relocate struct stx104_iio for the sake of a clearer patch diff
>  - Replace FIELD_PREP() and FIELD_GET() with u8_encode_bits() and
>    u8_get_bits()
> 
> The regmap API supports IO port accessors so we can take advantage of
> regmap abstractions rather than handling access to the device registers
> directly in the driver.
> 
> To make the git history cleaner, precursor patches to use a define
> rather than hardcoded limit and to improve indentation in
> stx104_write_raw(), and a follow-up patch to utilize
> regmap_read_poll_timeout() for polling the ADC conversion status are
> included.
> 
> William Breathitt Gray (6):
>   iio: addac: stx104: Fix race condition for stx104_write_raw()
>   iio: addac: stx104: Fix race condition when converting
>     analog-to-digital
>   iio: addac: stx104: Use define rather than hardcoded limit for write
>     val
>   iio: addac: stx104: Improve indentation in stx104_write_raw()
>   iio: addac: stx104: Migrate to the regmap API
>   iio: addac: stx104: Use regmap_read_poll_timeout() for conversion poll
> 
>  drivers/iio/addac/Kconfig  |   2 +
>  drivers/iio/addac/stx104.c | 460 +++++++++++++++++++++----------------
>  2 files changed, 264 insertions(+), 198 deletions(-)
> 
> 
> base-commit: f73df43e957a6fc705a9bd6d143585bdf1b13365


      parent reply	other threads:[~2023-04-07 16:34 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-06 14:40 [PATCH v5 0/6] Migrate STX104 to the regmap API William Breathitt Gray
2023-04-06 14:40 ` [PATCH v5 1/6] iio: addac: stx104: Fix race condition for stx104_write_raw() William Breathitt Gray
2023-04-07 16:51   ` Jonathan Cameron
2023-04-06 14:40 ` [PATCH v5 2/6] iio: addac: stx104: Fix race condition when converting analog-to-digital William Breathitt Gray
2023-04-06 14:40 ` [PATCH v5 3/6] iio: addac: stx104: Use define rather than hardcoded limit for write val William Breathitt Gray
2023-04-06 14:40 ` [PATCH v5 4/6] iio: addac: stx104: Improve indentation in stx104_write_raw() William Breathitt Gray
2023-04-06 14:40 ` [PATCH v5 5/6] iio: addac: stx104: Migrate to the regmap API William Breathitt Gray
2023-04-06 14:40 ` [PATCH v5 6/6] iio: addac: stx104: Use regmap_read_poll_timeout() for conversion poll William Breathitt Gray
2023-04-07 16:49 ` 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=20230407174841.2ca510f5@jic23-huawei \
    --to=jic23@kernel.org \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=william.gray@linaro.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