From: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
To: Mark Brown <broonie@kernel.org>
Cc: gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org,
alsa-devel@alsa-project.org
Subject: Re: [PATCH] regmap: slimbus: add support to raw read/writes
Date: Thu, 5 Jul 2018 17:13:21 +0100 [thread overview]
Message-ID: <3c958e52-d720-c008-913b-4ff29ea35c00@linaro.org> (raw)
In-Reply-To: <20180705150857.GA6227@sirena.org.uk>
On 05/07/18 16:08, Mark Brown wrote:
> On Thu, Jul 05, 2018 at 12:37:00PM +0100, Srinivas Kandagatla wrote:
>
>> SLIMbus supports upto 16 bytes in value management messages,
>> so add support to raw read/writes upto 16 bytes.
> That's not what raw access is. It's unmediated access to existing
> registers, not some other thing with completely different register sizes
> which you can't see through the register map. The intended use is for
> things like fast firmware downloads. If it's not part of the register
> map we shouldn't be going through regmap to get to it.
Thanks for explaining this in detail.
I think I got it wrong by looking at _regmap_bus_read() implementation
which calls _regmap_raw_read(), this made me think that read/writes
callbacks imply raw read/writes. Looks like that is not the case.
These bus read/write callbacks are just simple multiple register
read/writes.
All am trying to do is support paged registers, which seems to be only
possible via read/write support at bus level.
Does reg_read/reg_write become redundant if we implement read/write
callbacks at bus regmap level?
>
>> Also useful for paged register access on SLIMbus interfaced codecs.
> That needs a bunch more explanation... in what way does raw access
> relate to paged register maps?
Yes, this is nothing to do with raw access! I got it wrong!
WCD9335 codec has paged registers which is what I need!
I will fix the patch and commit message removing the raw related parts
and resend.
Does that sound okay?
thanks,
srini
next prev parent reply other threads:[~2018-07-05 16:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-05 11:37 Srinivas Kandagatla
2018-07-05 15:08 ` Mark Brown
2018-07-05 16:13 ` Srinivas Kandagatla [this message]
2018-07-05 16:50 ` Mark Brown
2018-07-05 17:20 ` Srinivas Kandagatla
2018-07-05 17:30 ` Mark Brown
2018-07-05 17:39 ` Srinivas Kandagatla
2018-07-05 17:47 ` Mark Brown
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=3c958e52-d720-c008-913b-4ff29ea35c00@linaro.org \
--to=srinivas.kandagatla@linaro.org \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®