From: Srinivasa Rao Mandadapu <quic_srivasam@quicinc.com>
To: Stephen Boyd <swboyd@chromium.org>, <agross@kernel.org>,
<alsa-devel@alsa-project.org>, <andersson@kernel.org>,
<bgoswami@quicinc.com>, <broonie@kernel.org>,
<devicetree@vger.kernel.org>, <judyhsiao@chromium.org>,
<lgirdwood@gmail.com>, <linux-arm-msm@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <perex@perex.cz>,
<quic_plai@quicinc.com>, <quic_rohkumar@quicinc.com>,
<robh+dt@kernel.org>, <srinivas.kandagatla@linaro.org>,
<tiwai@suse.com>
Subject: Re: [PATCH v2] ASoC: qcom: lpass-cpu: mark HDMI TX registers as volatile
Date: Sat, 15 Oct 2022 14:53:09 +0530 [thread overview]
Message-ID: <b0cbb2a4-088a-3f9a-8918-b95687ef2acd@quicinc.com> (raw)
In-Reply-To: <CAE-0n53W3+MgRzpkV-9kBc6Pcvzta+ear3oxgMA-0rpNyJyJwQ@mail.gmail.com>
On 10/15/2022 2:41 AM, Stephen Boyd wrote:
> Quoting Srinivasa Rao Mandadapu (2022-10-12 22:08:31)
>> Update HDMI volatile registers list as DMA, Channel Selection registers,
>> vbit control registers are being reflected by hardware DP port
>> disconnection.
>>
>> This update is required to fix no display and no sound issue observed
>> after reconnecting TAMA/SANWA DP cables.
>> Once DP cable is unplugged, DMA control registers are being reset by
>> hardware, however at second plugin, new dma control values does not
>> updated to the dma hardware registers since new register value and
>> cached values at the time of first plugin are same.
>>
>> Fixes: 7cb37b7bd0d3 ("ASoC: qcom: Add support for lpass hdmi driver")
>>
>> Signed-off-by: Srinivasa Rao Mandadapu <quic_srivasam@quicinc.com>
>> Reported-by: Kuogee Hsieh <quic_khsieh@quicinc.com>
>> ---
> I found that another patch in this area hasn't been applied[1]. Is it
> still relevant? We're still carrying it in the chromium tree. If it is
> relevant can you please resend it.
>
> [1] https://lore.kernel.org/all/1602596728-11783-1-git-send-email-srivasam@codeaurora.org/
Thanks for Notifying this untracked patch.
Resent the patch.
-
https://patchwork.kernel.org/project/alsa-devel/patch/1665825530-7593-1-git-send-email-quic_srivasam@quicinc.com/
prev parent reply other threads:[~2022-10-15 9:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-13 5:08 Srinivasa Rao Mandadapu
2022-10-13 14:43 ` Mark Brown
2022-10-14 21:11 ` Stephen Boyd
2022-10-15 9:23 ` Srinivasa Rao Mandadapu [this message]
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=b0cbb2a4-088a-3f9a-8918-b95687ef2acd@quicinc.com \
--to=quic_srivasam@quicinc.com \
--cc=agross@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=andersson@kernel.org \
--cc=bgoswami@quicinc.com \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=judyhsiao@chromium.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=quic_plai@quicinc.com \
--cc=quic_rohkumar@quicinc.com \
--cc=robh+dt@kernel.org \
--cc=srinivas.kandagatla@linaro.org \
--cc=swboyd@chromium.org \
--cc=tiwai@suse.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®