mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jon Hunter <jonathanh@nvidia.com>
To: webgeek1234@gmail.com, Jaroslav Kysela <perex@perex.cz>,
	Takashi Iwai <tiwai@suse.com>,
	Thierry Reding <thierry.reding@kernel.org>
Cc: 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 08:22:42 +0100	[thread overview]
Message-ID: <80d4c8aa-dfa7-4d67-83aa-60f9474a5d9f@nvidia.com> (raw)
In-Reply-To: <20260926-tegra194-hda-sdo-v1-1-f7a636a07a58@gmail.com>


On 26/09/2026 08:24, 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(-)
> 
> diff --git a/sound/hda/controllers/tegra.c b/sound/hda/controllers/tegra.c
> index 31c14c4bbe683..674cc0f79c3c8 100644
> --- a/sound/hda/controllers/tegra.c
> +++ b/sound/hda/controllers/tegra.c
> @@ -374,7 +374,8 @@ static int hda_tegra_first_init(struct azx *chip, struct platform_device *pdev)
>   	 * in powers of 2, next available ratio is 16 which can be
>   	 * used as a limiting factor here.
>   	 */
> -	if (of_device_is_compatible(np, "nvidia,tegra30-hda"))
> +	if (of_device_is_compatible(np, "nvidia,tegra30-hda") ||
> +	    of_device_is_compatible(np, "nvidia,tegra194-hda"))
>   		chip->bus.core.sdo_limit = 16;
>   
>   	/* codec detection */
> 
> ---
> base-commit: 4c253ac4b29b8c6cc6fdef8f92d4facde62e63b9
> change-id: 20260926-tegra194-hda-sdo-1d84c6085198
I would be tempted to change the fixes tag to be 615d43540043
("ALSA: hda/tegra: fix tegra-hda on tegra30 soc") because technically
the Tegra194 device-tree was incorrect and after commit 615d43540043
is present, we always want the above. Otherwise ...

Reviewed-by: Jon Hunter <jonathanh@nvidia.com>

Thanks!
Jon

-- 
nvpublic


  reply	other threads:[~2026-09-29  7:22 UTC|newest]

Thread overview: 3+ 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 [this message]
2026-09-29 11:12 ` Thierry Reding

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=80d4c8aa-dfa7-4d67-83aa-60f9474a5d9f@nvidia.com \
    --to=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®