public inbox for linux-tegra@vger.kernel.org
 help / color / mirror / Atom feed
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
Date: Tue, 13 Sep 2022 09:52:37 +0200	[thread overview]
Message-ID: <871qsfhfsq.wl-tiwai@suse.de> (raw)
In-Reply-To: <5f7d294a-5040-a7a7-cee2-d62cfef5b48e@nvidia.com>

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

      reply	other threads:[~2022-09-13  7:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-13  6:58 [v2] ALSA: hda: Fix Nvidia dp infoframe Mohan Kumar
2022-09-13  7:15 ` Takashi Iwai
2022-09-13  7:18   ` Mohan Kumar D
2022-09-13  7:52     ` 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=871qsfhfsq.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=jonathanh@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=mkumard@nvidia.com \
    --cc=perex@perex.cz \
    --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