From: Jie Gan <jie.gan@oss.qualcomm.com>
To: Mohammad Rafi Shaik <quic_mohs@quicinc.com>,
Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>, Vinod Koul <vkoul@kernel.org>,
Bard Liao <yung-chuan.liao@linux.intel.com>,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>
Cc: Pierre-Louis Bossart <pierre-louis.bossart@linux.dev>,
Sanyog Kale <sanyog.r.kale@intel.com>,
linux-arm-msm@vger.kernel.org, linux-sound@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
quic_pkumpatl@quicinc.com, kernel@oss.qualcomm.com
Subject: Re: [PATCH v6 3/4] soundwire: qcom: Add set_channel_map api support
Date: Mon, 10 Feb 2025 11:30:01 +0800 [thread overview]
Message-ID: <4ddd6855-3817-4dc4-81c4-d8ddaa039865@oss.qualcomm.com> (raw)
In-Reply-To: <20250206112225.3270400-4-quic_mohs@quicinc.com>
On 2/6/2025 7:22 PM, Mohammad Rafi Shaik wrote:
> Added qcom_swrm_set_channel_map api to set the master channel mask for
> TX and RX paths based on the provided slots.
>
> Added a new field ch_mask to the qcom_swrm_port_config structure.
> This field is used to store the master channel mask, which allows more
> flexible to configure channel mask in runtime for specific active
> soundwire ports.
>
> Modified the qcom_swrm_port_enable function to configure master
> channel mask. If the ch_mask is set to SWR_INVALID_PARAM or is zero,
> the function will use the default channel mask.
>
> Signed-off-by: Mohammad Rafi Shaik <quic_mohs@quicinc.com>
> Acked-by: Vinod Koul <vkoul@kernel.org>
> ---
> drivers/soundwire/qcom.c | 26 ++++++++++++++++++++++++++
> 1 file changed, 26 insertions(+)
>
> diff --git a/drivers/soundwire/qcom.c b/drivers/soundwire/qcom.c
> index 0f45e3404756..295a46dc2be7 100644
> --- a/drivers/soundwire/qcom.c
> +++ b/drivers/soundwire/qcom.c
> @@ -156,6 +156,7 @@ struct qcom_swrm_port_config {
> u8 word_length;
> u8 blk_group_count;
> u8 lane_control;
> + u8 ch_mask;
> };
>
> /*
> @@ -1048,9 +1049,13 @@ static int qcom_swrm_port_enable(struct sdw_bus *bus,
> {
> u32 reg = SWRM_DP_PORT_CTRL_BANK(enable_ch->port_num, bank);
> struct qcom_swrm_ctrl *ctrl = to_qcom_sdw(bus);
> + struct qcom_swrm_port_config *pcfg;
> u32 val;
>
> + pcfg = &ctrl->pconfig[enable_ch->port_num];
> ctrl->reg_read(ctrl, reg, &val);
> + if (pcfg->ch_mask != SWR_INVALID_PARAM && pcfg->ch_mask != 0)
> + enable_ch->ch_mask = pcfg->ch_mask;
>
> if (enable_ch->enable)
> val |= (enable_ch->ch_mask << SWRM_DP_PORT_CTRL_EN_CHAN_SHFT);
> @@ -1270,6 +1275,26 @@ static void *qcom_swrm_get_sdw_stream(struct snd_soc_dai *dai, int direction)
> return ctrl->sruntime[dai->id];
> }
>
> +static int qcom_swrm_set_channel_map(struct snd_soc_dai *dai,
> + unsigned int tx_num, const unsigned int *tx_slot,
> + unsigned int rx_num, const unsigned int *rx_slot)
> +{
> + struct qcom_swrm_ctrl *ctrl = dev_get_drvdata(dai->dev);
> + int i;
> +
> + if (tx_slot) {
> + for (i = 0; i < tx_num; i++)
> + ctrl->pconfig[i].ch_mask = tx_slot[i];
> + }
> +
> + if (rx_slot) {
> + for (i = 0; i < rx_num; i++)
> + ctrl->pconfig[i].ch_mask = rx_slot[i];
> + }
> +
It looks like a hack.
Consider the situation: if(tx_slot) is true and if(rx_slot) is true. So
the ch_mask always overwritten by rx_slot?
> + return 0;
I think you dont need the return value here. Just void is ok.
Thanks,
Jie
> +}
> +
> static int qcom_swrm_startup(struct snd_pcm_substream *substream,
> struct snd_soc_dai *dai)
> {
> @@ -1306,6 +1331,7 @@ static const struct snd_soc_dai_ops qcom_swrm_pdm_dai_ops = {
> .shutdown = qcom_swrm_shutdown,
> .set_stream = qcom_swrm_set_sdw_stream,
> .get_stream = qcom_swrm_get_sdw_stream,
> + .set_channel_map = qcom_swrm_set_channel_map,
> };
>
> static const struct snd_soc_component_driver qcom_swrm_dai_component = {
next prev parent reply other threads:[~2025-02-10 3:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-06 11:22 [PATCH v6 0/4] Add static channel mapping between soundwire master and slave Mohammad Rafi Shaik
2025-02-06 11:22 ` [PATCH v6 1/4] ASoC: dt-bindings: wcd937x-sdw: Add static channel mapping support Mohammad Rafi Shaik
2025-02-06 11:22 ` [PATCH v6 2/4] ASoC: codecs: wcd937x: Add static channel mapping support in wcd937x-sdw Mohammad Rafi Shaik
2025-02-06 11:22 ` [PATCH v6 3/4] soundwire: qcom: Add set_channel_map api support Mohammad Rafi Shaik
2025-02-10 3:30 ` Jie Gan [this message]
2025-05-08 7:18 ` Yongqin Liu
2025-06-27 20:59 ` Dan Carpenter
2025-02-06 11:22 ` [PATCH v6 4/4] ASoC: qcom: sdw: Add get and set channel maps support from codec to cpu dais Mohammad Rafi Shaik
2025-02-07 14:02 ` [PATCH v6 0/4] Add static channel mapping between soundwire master and slave Mark Brown
2025-04-22 14:59 ` Xilin Wu
2025-04-23 6:47 ` Xilin Wu
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=4ddd6855-3817-4dc4-81c4-d8ddaa039865@oss.qualcomm.com \
--to=jie.gan@oss.qualcomm.com \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kernel@oss.qualcomm.com \
--cc=krzk+dt@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=perex@perex.cz \
--cc=pierre-louis.bossart@linux.dev \
--cc=quic_mohs@quicinc.com \
--cc=quic_pkumpatl@quicinc.com \
--cc=robh@kernel.org \
--cc=sanyog.r.kale@intel.com \
--cc=srinivas.kandagatla@linaro.org \
--cc=tiwai@suse.com \
--cc=vkoul@kernel.org \
--cc=yung-chuan.liao@linux.intel.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®