From: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
To: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>,
vkoul@kernel.org
Cc: alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH] soundwire: bus: Add flag to mark DPN_BlockCtrl1 as readonly
Date: Wed, 11 Mar 2020 11:30:58 +0000 [thread overview]
Message-ID: <dec47c3a-08e9-e9a0-707c-2610cb10fe64@linaro.org> (raw)
In-Reply-To: <a2b24f84-0f9a-29ab-8748-dc5a26c05ffa@linux.intel.com>
Thanks for the inputs
On 10/03/2020 15:53, Pierre-Louis Bossart wrote:
> Hi Srinivas,
>
>>> > My recommendation would be to add a DisCo property stating the
>>> WordLength value can be used by the bus code but not written to the
>>> Slave device registers.
>>
>> Does something like "mipi-sdw-read-only-wordlength" as slave property,
>> make sense?
>
> The properties can be handled at two levels.
>
> First, you'd want to change include/linux/soundwire/sdw.h, and add a new
> field in
>
> struct sdw_dpn_prop {
> u32 num;
> u32 max_word;
> u32 min_word;
> u32 num_words;
> u32 *words;
> + bool read_only_wordlength;
>
> Once this is added, along with the code that bypasses the programming of
> DPn_BlockCtrl1, the implementation has two choices:
>
> a) hard-code the field value in the codec driver.
This totally works for me.
>
> b) read the property from firmware with the DisCo helpers.
>
I would defer adding this for now till there is a real users for this.
> There is no requirement that all properties be read from firmware, and
> if you look at existing code base sdw_slave_read_prop() is currently
> unused, each codec implements its own .read_prop() callback.
>
> We really wanted to be pragmatic, and give the possibility to either
> override bad firmware or extend incomplete firmware to avoid coupling OS
> and firmware too much. If you foresee cases where this implementation
> might vary and firmware distribution is not a problem, then a property
> read would make sense.
>
> Just once procedural reminder that all 'mipi-sdw' properties are handled
> by the MIPI software WG, so we'd need to have this property added in a
> formal MIPI document update.
>
> I suggest you talk with Lior first on this.
Sure, I will talk to him.
>
> Hope this helps
> -Pierre
next prev parent reply other threads:[~2020-03-11 11:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-09 17:37 [RFC PATCH] soundwire: bus: Add flag to mark DPN_BlockCtrl1 as readonly Srinivas Kandagatla
2020-03-09 18:05 ` Pierre-Louis Bossart
2020-03-10 14:01 ` Srinivas Kandagatla
2020-03-10 15:53 ` Pierre-Louis Bossart
2020-03-11 11:30 ` Srinivas Kandagatla [this message]
2020-03-11 6:42 ` Vinod Koul
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=dec47c3a-08e9-e9a0-707c-2610cb10fe64@linaro.org \
--to=srinivas.kandagatla@linaro.org \
--cc=alsa-devel@alsa-project.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=vkoul@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