Date:   Tue, 7 Dec 2021 09:21:39 +0100
From:   Thierry Reding <thierry.reding@gmail.com>
To:     Takashi Iwai <tiwai@suse.de>
Cc:     Sameer Pujar <spujar@nvidia.com>, tiwai@suse.com,
        broonie@kernel.org, lgirdwood@gmail.com, robh+dt@kernel.org,
        perex@perex.cz, jonathanh@nvidia.com, digetx@gmail.com,
        alsa-devel@alsa-project.org, devicetree@vger.kernel.org,
        linux-tegra@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] Fix Tegra194 HDA regression
Message-ID: <Ya8Zk/9n7nAtjvSe@orome.fritz.box>
References: <1638858770-22594-1-git-send-email-spujar@nvidia.com>
 <s5hy24won6h.wl-tiwai@suse.de>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;
        protocol="application/pgp-signature"; boundary="49TuLyavIf+IS4GG"
Content-Disposition: inline
In-Reply-To: <s5hy24won6h.wl-tiwai@suse.de>
User-Agent: Mutt/2.1.3 (987dde4c) (2021-09-10)
Precedence: bulk


--49TuLyavIf+IS4GG
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Tue, Dec 07, 2021 at 09:04:54AM +0100, Takashi Iwai wrote:
> On Tue, 07 Dec 2021 07:32:47 +0100,
> Sameer Pujar wrote:
> >=20
> > HDA probe failure is observed on Tegra194 based platforms and this
> > happens due to a reset failure. The series fixes this problem by
> > avoiding explicit resets on BPMP based devices.
> >=20
> > Sameer Pujar (3):
> >   ALSA: hda/tegra: Skip reset on BPMP devices
> >   dt-bindings: sound: tegra: Update HDA resets
> >   arm64: tegra: Remove non existent Tegra194 reset
>=20
> The change in HDA drier looks fine, and the question how to take those
> patches.  If other people can give acks, I can take those to sound.git
> tree destined for 5.16.
>=20
> Or, if anyone else prefers taking those, feel free to do: for the
> first patch,
>=20
> Reviewed-by: Takashi Iwai <tiwai@suse.de>

My understanding is that patches 1-2 are mostly independent of patch 3,
with the latter being mostly a complementary cleanup. Patch 1 will
effectively ignore the non-existent reset on Tegra194 anyway. Patch 1
(and potentially 2) could go into v5.16 to fix the regression via
sound.git, but the cleanup in patch 3 isn't time-critical, so I could
just queue that up for v5.17 via the Tegra tree.

Sameer, any objections to that? Did I miss anything?

Thierry

--49TuLyavIf+IS4GG
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAABCAAdFiEEiOrDCAFJzPfAjcif3SOs138+s6EFAmGvGZMACgkQ3SOs138+
s6HgkQ/+N8u8Xz+5+Ee5hefCCyEjNub0t9cEf0+Tk5v0L2TrMzxSmeHNItD0WBBi
udtQ8EZAti4dd4czN/XGVZRlM5WwLCB6OyDinnP4ORVr9AFQZnsY3ypiJmaeE8Bo
6Kz0bVYlnBCUZEizjETjYdHWz+b8dBKtAykaU7+qDG2Dp+cjx8nUWTvtbb4yMg+I
TvDsGs0tcvJ4KBb0Ryf6rgpxJ4NE/5Vi/qczIsJtqOtiRlw3ktNuvOlw9HmHLG6N
exMCoTxydM2iImudrVjobsHzVrxjMIfFCCmxXmwAAuwJuwechDb4C6eLVTbVag4B
tdv2y44xJXI9zax8PJjahOcyZKu6wuCmckQAoIPYAXgOJNSLGfqTom8iF+vn+vaF
+DbLzjsJOeokOXg47iDDsNQ3ZGRYs2pjArwmQ+A6m0oOGqjl3ucpnzjSxTMTMiaD
p/0qj/KawuoakssmZ0lwVRsy3kO299UDd4DLQ/iQ2sSOOCp20NTnVaHsxmq/3wnD
jkqELDynjSVSM8q7GB1yETfBth6mJfXBXcuMaXLRTlU3nG8tTIyi3/jL908qmZN7
C4bwgD4e7gZ97h9iaCMlihkrO+LFzI7vJyhaaBiITeuA8BC0kerIJYSc2OMJ40Zy
zn+AOY/uo5gx8rh7tVWX9CuWWz2btkKq0zp4/8w9UtAgcM3Bahc=
=Lb4G
-----END PGP SIGNATURE-----

--49TuLyavIf+IS4GG--