[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <925e2586-39dd-b1d9-174a-bda3367ab668@codeaurora.org>
Date: Sat, 3 Oct 2020 17:06:06 +0530
From: Srinivasa Rao Mandadapu <srivasam@...eaurora.org>
To: Srinivas Kandagatla <srinivas.kandagatla@...aro.org>,
agross@...nel.org, bjorn.andersson@...aro.org, lgirdwood@...il.com,
broonie@...nel.org, robh+dt@...nel.org, plai@...eaurora.org,
bgoswami@...eaurora.org, perex@...ex.cz, tiwai@...e.com,
rohitkr@...eaurora.org, linux-arm-msm@...r.kernel.org,
alsa-devel@...a-project.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org
Cc: V Sujith Kumar Reddy <vsujithk@...eaurora.org>
Subject: Re: [PATCH v8 5/7] ASoC: qcom: Add support for lpass hdmi driver
Thanks for bringing up this point Srinivas!!!
On 9/30/2020 8:57 PM, Srinivas Kandagatla wrote:
>
>
> On 30/09/2020 07:39, Srinivasa Rao Mandadapu wrote:
>> +}
>> +
>> +static bool lpass_hdmi_regmap_volatile(struct device *dev, unsigned
>> int reg)
>> +{
>> + return true;
>> +}
>
> I did ask this question in multiple reviews, but never got an answer!
> Are all the dp/hdmi port register range really volatile!?
Sorry for incomplete response in last review comment reply.
With making only specific DMA registers and interrupts registers true,
aplay was stuck.
Now we identified issue causing register and made it volatile.
With that change it seems working fine. After doing all the tests we
will share v9 series patch.
>
>
>
> --srini
>> +
>> +struct regmap_config lpass_hdmi_regmap_config = {
>> + .reg_bits = 32,
>> + .reg_stride = 4,
>> + .val_bits = 32,
>> + .writeable_reg = lpass_hdmi_regmap_writeable,
>> + .readable_reg = lpass_hdmi_regmap_readable,
>> + .volatile_reg = lpass_hdmi_regmap_volatile,
--
Qualcomm India Private Limited, on behalf of Qualcomm Innovation Center, Inc.,
is a member of Code Aurora Forum, a Linux Foundation Collaborative Project.
Powered by blists - more mailing lists