From: Sameer Pujar <spujar@nvidia.com>
To: Dmitry Osipenko <digetx@gmail.com>,
tiwai@suse.com, broonie@kernel.org, lgirdwood@gmail.com,
robh+dt@kernel.org, thierry.reding@gmail.com, perex@perex.cz
Cc: jonathanh@nvidia.com, mkumard@nvidia.com,
alsa-devel@alsa-project.org, devicetree@vger.kernel.org,
linux-tegra@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH v2 1/3] ALSA: hda/tegra: Fix Tegra194 HDA reset failure
Date: Tue, 21 Dec 2021 11:48:57 +0530 [thread overview]
Message-ID: <f65ae56d-d289-9e3f-1c15-f0bedda3918c@nvidia.com> (raw)
In-Reply-To: <f859559c-abf1-ae37-6a0f-80329e6f747f@gmail.com>
On 12/21/2021 6:51 AM, Dmitry Osipenko wrote:
>
> All stable kernels affected by this problem that don't support the bulk
> reset API are EOL now. Please use bulk reset API like I suggested in the
> comment to v1, it will allow us to have a cleaner and nicer code.
Agree that it would be compact and cleaner, but any specific reset
failure in the group won't be obvious in the logs. In this case it
failed silently. If compactness is preferred, then may be I can keep an
error print at group level so that we see some failure context whenever
it happens.
next prev parent reply other threads:[~2021-12-21 6:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-20 17:30 [PATCH v2 0/3] Fix Tegra194 HDA regression Sameer Pujar
2021-12-20 17:30 ` [PATCH v2 1/3] ALSA: hda/tegra: Fix Tegra194 HDA reset failure Sameer Pujar
2021-12-21 1:21 ` Dmitry Osipenko
2021-12-21 6:18 ` Sameer Pujar [this message]
2021-12-21 15:20 ` Dmitry Osipenko
2021-12-21 16:03 ` Sameer Pujar
2021-12-20 17:30 ` [PATCH v2 2/3] dt-bindings: sound: tegra: Update HDA resets Sameer Pujar
2021-12-20 17:30 ` [PATCH v2 3/3] arm64: tegra: Remove non existent Tegra194 reset Sameer Pujar
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=f65ae56d-d289-9e3f-1c15-f0bedda3918c@nvidia.com \
--to=spujar@nvidia.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=digetx@gmail.com \
--cc=jonathanh@nvidia.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mkumard@nvidia.com \
--cc=perex@perex.cz \
--cc=robh+dt@kernel.org \
--cc=stable@vger.kernel.org \
--cc=thierry.reding@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).