From: Takashi Iwai <tiwai@suse.de>
To: Aaron Kling <webgeek1234@gmail.com>
Cc: Thierry Reding <thierry.reding@kernel.org>,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
Jonathan Hunter <jonathanh@nvidia.com>,
Thierry Reding <treding@nvidia.com>,
linux-sound@vger.kernel.org, linux-tegra@vger.kernel.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH] ALSA: hda/tegra: Re-enable SDO workaround for Tegra194
Date: Tue, 29 Sep 2026 20:11:16 +0200 [thread overview]
Message-ID: <87a4p0ylkr.wl-tiwai@suse.de> (raw)
In-Reply-To: <CALHNRZ8RLs6mXkYiZ4qRimmf4WzpWpnJ9racWTPH__Op2Nk8kg@mail.gmail.com>
On Tue, 29 Sep 2026 19:22:25 +0200,
Aaron Kling wrote:
>
> On Tue, Sep 29, 2026 at 6:12 AM Thierry Reding
> <thierry.reding@kernel.org> wrote:
> >
> > On Sat, Sep 26, 2026 at 02:24:19AM -0500, Aaron Kling via B4 Relay wrote:
> > > From: Aaron Kling <webgeek1234@gmail.com>
> > >
> > > This workaround was originally added for Tegra194, but no longer gets
> > > applied for it. Commit 615d43540043 ("ALSA: hda/tegra: fix tegra-hda on
> > > tegra30 soc") changed the guard to tegra30-hda, which worked because all
> > > affected archs had the fallback compatible. However, commit 7f0ea5acfc19
> > > ("arm64: tegra: Use correct compatible string for Tegra194 HDA") removed
> > > the fallback compatible for Tegra194, causing this to break.
> > >
> > > Fixes: 7f0ea5acfc19 ("arm64: tegra: Use correct compatible string for Tegra194 HDA")
> > > Cc: stable@vger.kernel.org
> > > Assisted-by: LLM
> > > Signed-off-by: Aaron Kling <webgeek1234@gmail.com>
> > > ---
> > > ALSA: hda/tegra: Re-enable SDO workaround for Tegra194
> > > ---
> > > sound/hda/controllers/tegra.c | 3 ++-
> > > 1 file changed, 2 insertions(+), 1 deletion(-)
> >
> > Maybe we should move this out of of_device_is_compatible() conditionals
> > and into hda_tegra_soc instead. That would make the checks for this a
> > lot more consistent and robust.
>
> I received a notification from Takashi Iwai that this has already been
> picked up, but it was only sent to me and not the list. Not sure why.
> But looking at -next, it's already there. Not sure if you would want
> to have that pulled back for updates or do followups later.
Ah, I overlooked that your mail had 'Reply-To', and my mailer followed
it as default.
And yes, the patch was already queued for 7.4. But if anyone has a
better alternative, feel free to submit as an incremental fix.
thanks,
Takashi
prev parent reply other threads:[~2026-09-29 18:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-26 7:24 Aaron Kling via B4 Relay
2026-09-29 7:22 ` Jon Hunter
2026-09-29 11:12 ` Thierry Reding
2026-09-29 17:22 ` Aaron Kling
2026-09-29 18:11 ` Takashi Iwai [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=87a4p0ylkr.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=perex@perex.cz \
--cc=stable@vger.kernel.org \
--cc=thierry.reding@kernel.org \
--cc=tiwai@suse.com \
--cc=treding@nvidia.com \
--cc=webgeek1234@gmail.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®