From: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
To: Mark Brown <broonie@kernel.org>
Cc: perex@perex.cz, tiwai@suse.com, lgirdwood@gmail.com,
ckeepax@opensource.cirrus.com, kuninori.morimoto.gx@renesas.com,
linux-kernel@vger.kernel.org,
pierre-louis.bossart@linux.intel.com,
alsa-devel@alsa-project.org
Subject: Re: [PATCH 1/2] ASoC: codecs: wsa883x: do not set can_multi_write flag
Date: Wed, 24 May 2023 11:09:32 +0100 [thread overview]
Message-ID: <bdceb6e4-9de8-07ab-502b-c526e97a592d@linaro.org> (raw)
In-Reply-To: <c24b2f1c-3b08-492f-954c-c4f10ae5ad81@sirena.org.uk>
On 24/05/2023 10:48, Mark Brown wrote:
> On Wed, May 24, 2023 at 10:42:21AM +0100, Srinivas Kandagatla wrote:
>> On 24/05/2023 09:57, Mark Brown wrote:
>
>>> I'm unclear, is this a limitation of the hardware or of the current
>>> Soundwire code?
>
>> Its both.
>
>> Codec itself does not have any private write callback to support this and
>> AFAIU Qualcomm Soundwire controller does not have any such hw facility to
>> program multi-registers for device at one shot.
>
> How about the *CODEC* hardware?
>
No, Codec does not have any such interface to write to device registers
directly without going via Soundwire.
>> Is write callback used for both Bulk writes and multi-writes?
>
> Only multi-write at this point but we probably should consider redoing
> bulk writes to use it as well.
By the looks of the code, its other way around.
>
>> Is multi-write feature of regmap bus or device?
>
> Well, I don't think any buses that understand registers have implemented
> it yet but there's nothing fundamental that means that a bus couldn't
> usefully do something with multi-write. The current users all use raw
> buses that don't know anything about registers or values.
next prev parent reply other threads:[~2023-05-24 10:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-23 15:46 Srinivas Kandagatla
2023-05-23 15:46 ` [PATCH 2/2] ASoC: codecs: wsa881x: " Srinivas Kandagatla
2023-05-23 16:55 ` [PATCH 1/2] ASoC: codecs: wsa883x: " Mark Brown
2023-05-24 8:51 ` Srinivas Kandagatla
2023-05-24 8:57 ` Mark Brown
2023-05-24 9:42 ` Srinivas Kandagatla
2023-05-24 9:48 ` Mark Brown
2023-05-24 10:09 ` Srinivas Kandagatla [this message]
2023-05-24 10:14 ` Mark Brown
2023-05-24 11:28 ` Mark Brown
2023-06-05 8:08 ` Johan Hovold
2023-06-05 12:24 ` Mark Brown
2023-06-05 12:31 ` Johan Hovold
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=bdceb6e4-9de8-07ab-502b-c526e97a592d@linaro.org \
--to=srinivas.kandagatla@linaro.org \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=ckeepax@opensource.cirrus.com \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=tiwai@suse.com \
/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®