Hi Srinivas,
Thanks for your review!
On Fri, Dec 03, 2021 at 10:35:08AM +0000, Srinivas Kandagatla wrote:
I have tested DB410c this use case in the past using similar patch [1].
Did you use a different modem DSP firmware? (An older one maybe?) In my tests the newer ones seem to have QDSP6 audio completely broken, my DB410c simply rebooted when I tried it.
On 02/12/2021 14:55, Stephan Gerhold wrote:
The apq8016-sbc-sndcard is designed to be used with the LPASS drivers (bypassing the combined audio/modem DSP in MSM8916/APQ8016). Make it possible to use QDSP6 audio instead for the msm8916-qdsp6-sndcard.
This only requires adding some additional hooks that set up the DPCM backends correctly. Similar code is already used in drivers for newer SoCs such as apq8096.c, sdm845.c and sm8250.c.
A slightly different initialization sequence is used for the apq8016-sbc and msm8916-qdsp6 sound card by defining the apq8016_sbc_add_ops() function as device match data.
Other alternative is to reuse card->name populated from "qcom,model" property to differentiate between both of these.
This should also help in differentiating UCM configs.
I have "qdsp6" in card->components to differentiate the setups in UCM configs. I think this is a more flexible approach than adding it to the card model. It can be checked in UCM using ${CardComponents}.
In my setup the card "model" identifies the device in use (e.g. smartphone X with a stereo speaker setup). This device might use the DSP bypass (apq8016-sbc-sndcard) or QDSP6 (msm8916-qdsp6-sndcard), depending on user preference. In UCM this is detected by checking if ${CardComponents} contains "qdsp6" or not.
The reason for supporting both setups is that they both have their advantages and disadvantages. The DSP must be used when the modem is needed, but otherwise the LPASS driver tends to give more easy control about sample rate, latency etc.
Cc: Srinivas Kandagatla srinivas.kandagatla@linaro.org Signed-off-by: Stephan Gerhold stephan@gerhold.net
Few minor nits, other than that it LGTM,
Reviewed-by: Srinivas Kandagatla srinivas.kandagatla@linaro.org
sound/soc/qcom/apq8016_sbc.c | 134 +++++++++++++++++++++++++++++++++-- 1 file changed, 129 insertions(+), 5 deletions(-)
diff --git a/sound/soc/qcom/apq8016_sbc.c b/sound/soc/qcom/apq8016_sbc.c index ba2a98268ee4..f9d69375320e 100644 --- a/sound/soc/qcom/apq8016_sbc.c +++ b/sound/soc/qcom/apq8016_sbc.c [...] +static int msm8916_qdsp6_startup(struct snd_pcm_substream *substream) +{
- struct snd_soc_pcm_runtime *rtd = substream->private_data;
- struct snd_soc_card *card = rtd->card;
- struct apq8016_sbc_data *data = snd_soc_card_get_drvdata(card);
- struct snd_soc_dai *cpu_dai = asoc_rtd_to_cpu(rtd, 0);
- int mi2s, ret;
- mi2s = qdsp6_dai_get_lpass_id(cpu_dai);
- if (mi2s < 0)
return mi2s;- if (++data->mi2s_clk_count[mi2s] > 1)
return 0;Am assuming that as you are not setting any DIGITAL CDC clock here you might be using an external codec.
For apq8016-sbc the digital clock is controlled by msm8916-wcd-digital through the reference in the device tree (<&gcc GCC_CODEC_DIGCODEC_CLK>). It must be carefully managed, because it is needed for register access in that driver.
Since QDSP6 also allows controlling this clock though LPAIF_DIG_CLK it is a bit of a hack to bypass it using the GCC driver. However, I kept the same setup for simplicity and it has been working just fine so far.
AFAICT in your commit you simply turn on the clock twice, once directly using GCC and once indirectly via LPAIF_DIG_CLK in QDSP6. :-)
- ret = snd_soc_dai_set_sysclk(cpu_dai, LPAIF_BIT_CLK, MI2S_BCLK_RATE, 0);
- if (ret)
dev_err(card->dev, "Failed to enable LPAIF bit clk: %d\n", ret);- return ret;
+}
[...] @@ -148,11 +266,16 @@ static const struct snd_soc_dapm_widget apq8016_sbc_dapm_widgets[] = { static int apq8016_sbc_platform_probe(struct platform_device *pdev) {
- void (*add_ops)(struct snd_soc_card *card); struct device *dev = &pdev->dev; struct snd_soc_card *card; struct apq8016_sbc_data *data; int ret;
- add_ops = device_get_match_data(&pdev->dev);
- if (!add_ops)
return -EINVAL;We will never hit the error case here because without a match we can not even enter the probe function.
Theoretically it's possible to create platform devices through other ways than the device tree (think of old board C files for example). I agree that nobody should do that, but having this check here at least avoids a NULL pointer dereference in this unlikely scenario.
Please let me know if I should remove it anyway, that's fine for me!
Thanks, Stephan