From: Himanshu Jha <himanshujha199640@gmail.com>
To: David Frey <dpfrey@gmail.com>
Cc: linux-iio <linux-iio@vger.kernel.org>
Subject: Re: Idea: regmap_config.use_single_rw -> use_single_read, use_single_write
Date: Fri, 31 Aug 2018 22:50:27 +0530 [thread overview]
Message-ID: <20180831172027.GA10477@himanshu-Vostro-3559> (raw)
In-Reply-To: <20180831170907.GA10015@himanshu-Vostro-3559>
On Fri, Aug 31, 2018 at 10:39:07PM +0530, Himanshu Jha wrote:
> On Fri, Aug 31, 2018 at 07:55:36AM -0700, David Frey wrote:
> > On 8/29/2018 10:35 AM, David Frey wrote:
> > > Hi,
> > >
> > > I just want to float an idea and see if it gets any support.
> > >
> > > In struct regmap_config, there is a member "bool use_single_rw" which is
> > > documented as follows:
> > >
> > > "If set, converts the bulk read and write operations into a series of
> > > single read and write operations. This is useful for device that does
> > > not support bulk read and write."
> > >
> > > My idea is to split this into:
> > > bool use_single_read;
> > > bool use_single_write;
> > >
> > > I think this would be useful because at least one device that I'm using
> > > (Bosch bmi160 IMU) supports bulk reads, but not bulk writes. It would
> > > be convenient to be able to use regmap_bulk_read and regmap_bulk_write
> > > and have only regmap_bulk_write split the writes apart. This change
> > > would also support the case where a device supports bulk writes, but not
> > > bulk reads. I don't know of such a device, but I haven't made any
> > > attempt to find one.
> > >
> > > What do you think?
Btw, if device doesn't support a bulk write and instead only supports a bulk
read as we see in BMI160, wouldn't the following suffice the problem:
.use_single_rw = true,
.can_multi_write = false, // or probably not setting it up(clear)
313 * @can_multi_write: If set, the device supports the multi write mode of bulk
314 * write operations, if clear multi write requests will be
315 * split into individual write operations
Thanks
--
Himanshu Jha
Undergraduate Student
Department of Electronics & Communication
Guru Tegh Bahadur Institute of Technology
next prev parent reply other threads:[~2018-08-31 21:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-29 17:35 Idea: regmap_config.use_single_rw -> use_single_read, use_single_write David Frey
2018-08-31 14:55 ` David Frey
2018-08-31 17:09 ` Himanshu Jha
2018-08-31 17:20 ` Himanshu Jha [this message]
2018-08-31 17:40 ` David Frey
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=20180831172027.GA10477@himanshu-Vostro-3559 \
--to=himanshujha199640@gmail.com \
--cc=dpfrey@gmail.com \
--cc=linux-iio@vger.kernel.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