[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <169528908296.97319.1848948668643094291.b4-ty@kernel.org>
Date: Thu, 21 Sep 2023 11:38:02 +0200
From: Vinod Koul <vkoul@...nel.org>
To: Andy Gross <agross@...nel.org>,
Bjorn Andersson <andersson@...nel.org>,
Konrad Dybcio <konrad.dybcio@...aro.org>,
Bard Liao <yung-chuan.liao@...ux.intel.com>,
Pierre-Louis Bossart <pierre-louis.bossart@...ux.intel.com>,
Sanyog Kale <sanyog.r.kale@...el.com>,
linux-arm-msm@...r.kernel.org, alsa-devel@...a-project.org,
linux-kernel@...r.kernel.org,
Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
Subject: Re: [PATCH 1/2] soundwire: qcom: use newer link status tregister
on v2.0.0
On Fri, 28 Jul 2023 13:28:47 +0200, Krzysztof Kozlowski wrote:
> Soundwire v2.0.0 comes with a new register LINK_STATUS for the
> FRAME_GEN_ENABLED field (bit indicating that an active frame is
> running). The old register COMP_STATUS is still there and still works,
> although the new one is preferred in downstream sources. Probably
> because it allows to choose Soundwire instance per CPU. Most of the
> code allowing to use new register for Soundwire v2.0.0 was already there
> as part of commit 312355a6a9f6 ("soundwire: qcom: add support for v2.0.0
> controller"), so switch to it in swrm_wait_for_frame_gen_enabled()
> function. This should not have functional impact, because the old
> register still behaves correctly.
>
> [...]
Applied, thanks!
[1/2] soundwire: qcom: use newer link status tregister on v2.0.0
commit: 5d78c7d684192e42241593a936ee60003d8ac064
[2/2] soundwire: qcom: handle command ignored interrupt
commit: 16d568c8f646933710c980783d87d3f59a89b563
Best regards,
--
~Vinod
Powered by blists - more mailing lists