Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Date:   Tue, 13 Sep 2022 09:52:37 +0200
Message-ID: <871qsfhfsq.wl-tiwai@suse.de>
From:   Takashi Iwai <tiwai@suse.de>
To:     Mohan Kumar D <mkumard@nvidia.com>
Cc:     tiwai@suse.com, perex@perex.cz, thierry.reding@gmail.com,
        jonathanh@nvidia.com, linux-tegra@vger.kernel.org,
        alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org
Subject: Re: [v2] ALSA: hda: Fix Nvidia dp infoframe
In-Reply-To: <5f7d294a-5040-a7a7-cee2-d62cfef5b48e@nvidia.com>
References: <20220913065818.13015-1-mkumard@nvidia.com>
        <874jxbhhin.wl-tiwai@suse.de>
        <5f7d294a-5040-a7a7-cee2-d62cfef5b48e@nvidia.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/27.2 Mule/6.0
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Precedence: bulk

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@nvidia.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