mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Srinivas Kandagatla <srinivas.kandagatla@linaro.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:50:11 +0100	[thread overview]
Message-ID: <20180705165011.GC6227@sirena.org.uk> (raw)
In-Reply-To: <3c958e52-d720-c008-913b-4ff29ea35c00@linaro.org>

[-- Attachment #1: Type: text/plain, Size: 732 bytes --]

On Thu, Jul 05, 2018 at 05:13:21PM +0100, Srinivas Kandagatla wrote:

> 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.

They are reads and writes, the thing is that they're reads and writes of
the register map that's also accessible for other operations rather than
something separate.

> All am trying to do is support paged registers, which seems to be only
> possible via read/write support at bus level.

Could you explain what you mean by paged registers?  There's framework
support for what's normally called pages but perhaps this is some
slimbus specific thing?

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2018-07-05 16:50 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
2018-07-05 16:50     ` Mark Brown [this message]
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=20180705165011.GC6227@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=srinivas.kandagatla@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

all inboxes | Powered by JetHome®