From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>, vkoul@kernel.org
Cc: linux-kernel@vger.kernel.org, alsa-devel@alsa-project.org
Subject: Re: [PATCH] soundwire: stream: use sdw_write instead of update
Date: Thu, 12 Mar 2020 05:45:32 -0500 [thread overview]
Message-ID: <b235b88a-acdc-cec4-0c00-2609c3774fa1@linux.intel.com> (raw)
In-Reply-To: <20200312100105.5293-1-srinivas.kandagatla@linaro.org>
On 3/12/20 5:01 AM, Srinivas Kandagatla wrote:
> There is no point in using update for registers with write mask
> as 0xFF, this adds unecessary traffic on the bus.
> Just use sdw_write directly.
well in theory you could have two streams share the same port, that's
allowed by the specification.
But since it clearly documented as not supported
/*
* Since bus doesn't support sharing a port across two streams,
* it is safe to reset this register
*/
this mask handing is indeed completely overkill.
Acked-by: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
>
> Signed-off-by: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
> ---
> drivers/soundwire/stream.c | 9 ++++-----
> 1 file changed, 4 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/soundwire/stream.c b/drivers/soundwire/stream.c
> index 00348d1fc606..1b43d03c79ea 100644
> --- a/drivers/soundwire/stream.c
> +++ b/drivers/soundwire/stream.c
> @@ -313,9 +313,9 @@ static int sdw_enable_disable_slave_ports(struct sdw_bus *bus,
> * it is safe to reset this register
> */
> if (en)
> - ret = sdw_update(s_rt->slave, addr, 0xFF, p_rt->ch_mask);
> + ret = sdw_write(s_rt->slave, addr, p_rt->ch_mask);
> else
> - ret = sdw_update(s_rt->slave, addr, 0xFF, 0x0);
> + ret = sdw_write(s_rt->slave, addr, 0x0);
>
> if (ret < 0)
> dev_err(&s_rt->slave->dev,
> @@ -464,10 +464,9 @@ static int sdw_prep_deprep_slave_ports(struct sdw_bus *bus,
> addr = SDW_DPN_PREPARECTRL(p_rt->num);
>
> if (prep)
> - ret = sdw_update(s_rt->slave, addr,
> - 0xFF, p_rt->ch_mask);
> + ret = sdw_write(s_rt->slave, addr, p_rt->ch_mask);
> else
> - ret = sdw_update(s_rt->slave, addr, 0xFF, 0x0);
> + ret = sdw_write(s_rt->slave, addr, 0x0);
>
> if (ret < 0) {
> dev_err(&s_rt->slave->dev,
>
next prev parent reply other threads:[~2020-03-12 11:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-12 10:01 [PATCH] soundwire: stream: use sdw_write instead of update Srinivas Kandagatla
2020-03-12 10:45 ` Pierre-Louis Bossart [this message]
2020-03-13 12:37 ` 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=b235b88a-acdc-cec4-0c00-2609c3774fa1@linux.intel.com \
--to=pierre-louis.bossart@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=linux-kernel@vger.kernel.org \
--cc=srinivas.kandagatla@linaro.org \
--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