[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5e50e8a1-5436-b543-f15d-50c5089304e3@nvidia.com>
Date: Tue, 7 Dec 2021 11:02:45 +0000
From: Jon Hunter <jonathanh@...dia.com>
To: Dmitry Osipenko <digetx@...il.com>,
Sameer Pujar <spujar@...dia.com>, tiwai@...e.com,
broonie@...nel.org, lgirdwood@...il.com, robh+dt@...nel.org,
thierry.reding@...il.com, perex@...ex.cz
Cc: alsa-devel@...a-project.org, devicetree@...r.kernel.org,
linux-tegra@...r.kernel.org, linux-kernel@...r.kernel.org,
stable@...r.kernel.org
Subject: Re: [PATCH 1/3] ALSA: hda/tegra: Skip reset on BPMP devices
On 07/12/2021 10:58, Dmitry Osipenko wrote:
> 07.12.2021 13:44, Dmitry Osipenko пишет:
>> 07.12.2021 13:22, Dmitry Osipenko пишет:
>>> 07.12.2021 09:32, Sameer Pujar пишет:
>>>> HDA regression is recently reported on Tegra194 based platforms.
>>>> This happens because "hda2codec_2x" reset does not really exist
>>>> in Tegra194 and it causes probe failure. All the HDA based audio
>>>> tests fail at the moment. This underlying issue is exposed by
>>>> commit c045ceb5a145 ("reset: tegra-bpmp: Handle errors in BPMP
>>>> response") which now checks return code of BPMP command response.
>
> I see that this BPMP commit already has been reverted. There is no
> problem in this hda_tegra driver at all.
That is temporary until this fix is merged and then we will revert the
revert.
Jon
--
nvpublic
Powered by blists - more mailing lists