linux-kernel - Re: [v2] ALSA: hda: Fix Nvidia dp infoframe

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <871qsfhfsq.wl-tiwai@suse.de>
Date:   Tue, 13 Sep 2022 09:52:37 +0200
From:   Takashi Iwai <tiwai@...e.de>
To:     Mohan Kumar D <mkumard@...dia.com>
Cc:     tiwai@...e.com, perex@...ex.cz, thierry.reding@...il.com,
        jonathanh@...dia.com, linux-tegra@...r.kernel.org,
        alsa-devel@...a-project.org, linux-kernel@...r.kernel.org
Subject: Re: [v2] ALSA: hda: Fix Nvidia dp infoframe

On Tue, 13 Sep 2022 09:18:52 +0200,
Mohan Kumar D wrote:
> 
> 
> On 9/13/2022 12:45 PM, Takashi Iwai wrote:
> > External email: Use caution opening links or attachments
> > 
> > 
> > On Tue, 13 Sep 2022 08:58:18 +0200,
> > Mohan Kumar wrote:
> >> Nvidia HDA HW expects infoframe data bytes order same for both
> >> HDMI and DP i.e infoframe data starts from 5th bytes offset. As
> >> dp infoframe structure has 4th byte as valid infoframe data, use
> >> hdmi infoframe structure for nvidia dp infoframe to match HW behvaior.
> >> 
> >> Signed-off-by: Mohan Kumar <mkumard@...dia.com>
> > Aha, so this affects on all Nvidia devices, not only on Tegra, but
> > also on PC?  Then we should put cc-to-stable definitely.
> Yes, The HDA HW design was common for dGPU and Tegra.
> > 
> > (No need to resend, I can put it locally.)
> Thanks!.

OK, applied now.


thanks,

Takashi