From: Jonathan Cameron <jic23@kernel.org>
To: Charles Keepax <ckeepax@opensource.cirrus.com>
Cc: <knaack.h@gmx.de>, <lars@metafoo.de>, <pmeerw@pmeerw.net>,
<linux-iio@vger.kernel.org>
Subject: Re: [PATCH RESEND] iio: accel: bcm150: Remove handling for regmap raw_read_max
Date: Sat, 28 Apr 2018 17:02:33 +0100 [thread overview]
Message-ID: <20180428170233.1401cb9b@archlinux> (raw)
In-Reply-To: <20180424150551.14847-1-ckeepax@opensource.cirrus.com>
On Tue, 24 Apr 2018 16:05:51 +0100
Charles Keepax <ckeepax@opensource.cirrus.com> wrote:
> The regmap core now handles splitting up transactions according to
> max_raw_read, so this code is no longer required in client drivers.
>
> Signed-off-by: Charles Keepax <ckeepax@opensource.cirrus.com>
Applied to the togreg branch of iio.git and pushed out as testing
for the autobuilders to play with it.
Thanks,
Jonathan
> ---
>
> The necessary changes to support this are available in Linus's tree now.
>
> Thanks,
> Charles
>
> drivers/iio/accel/bmc150-accel-core.c | 23 +++--------------------
> 1 file changed, 3 insertions(+), 20 deletions(-)
>
> diff --git a/drivers/iio/accel/bmc150-accel-core.c b/drivers/iio/accel/bmc150-accel-core.c
> index 208f2d9f0e8a..383c802eb5b8 100644
> --- a/drivers/iio/accel/bmc150-accel-core.c
> +++ b/drivers/iio/accel/bmc150-accel-core.c
> @@ -837,29 +837,12 @@ static int bmc150_accel_fifo_transfer(struct bmc150_accel_data *data,
> int sample_length = 3 * 2;
> int ret;
> int total_length = samples * sample_length;
> - int i;
> - size_t step = regmap_get_raw_read_max(data->regmap);
> -
> - if (!step || step > total_length)
> - step = total_length;
> - else if (step < total_length)
> - step = sample_length;
> -
> - /*
> - * Seems we have a bus with size limitation so we have to execute
> - * multiple reads
> - */
> - for (i = 0; i < total_length; i += step) {
> - ret = regmap_raw_read(data->regmap, BMC150_ACCEL_REG_FIFO_DATA,
> - &buffer[i], step);
> - if (ret)
> - break;
> - }
>
> + ret = regmap_raw_read(data->regmap, BMC150_ACCEL_REG_FIFO_DATA,
> + buffer, total_length);
> if (ret)
> dev_err(dev,
> - "Error transferring data from fifo in single steps of %zu\n",
> - step);
> + "Error transferring data from fifo: %d\n", ret);
>
> return ret;
> }
prev parent reply other threads:[~2018-04-28 16:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-24 15:05 [PATCH RESEND] iio: accel: bcm150: Remove handling for regmap raw_read_max Charles Keepax
2018-04-28 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=20180428170233.1401cb9b@archlinux \
--to=jic23@kernel.org \
--cc=ckeepax@opensource.cirrus.com \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=pmeerw@pmeerw.net \
/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