From: "Subhransu S. Prusty" <subhransu.s.prusty@intel.com>
To: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
Cc: Takashi Iwai <tiwai@suse.de>,
Sriram Periyasamy <sriramx.periyasamy@intel.com>,
alsa-devel@alsa-project.org, broonie@kernel.org
Subject: Re: [PATCH v2] ALSA: hda - program ICT bits to support HBR audio
Date: Mon, 25 Sep 2017 20:26:53 +0530 [thread overview]
Message-ID: <20170925145649.GA5063@subhransu-desktop> (raw)
In-Reply-To: <8af5af38-f220-f58a-e7be-4e25dfff452a@linux.intel.com>
On Wed, Sep 20, 2017 at 08:12:36AM -0500, Pierre-Louis Bossart wrote:
> On 9/20/17 5:00 AM, Takashi Iwai wrote:
> >On Wed, 20 Sep 2017 00:25:05 +0200,
> >Pierre-Louis Bossart wrote:
> >>
> >>From: Sriram Periyasamy <sriramx.periyasamy@intel.com>
> >>
> >>On recent Intel platforms (Haswell, Broadwell, Skylake, ApolloLake,
> >>KabyLake, ...), the IEC Coding Type (ICT) bitfield in the Digital
> >>Converter Control #3 needs to be set explicitly for HDMI/DisplayPort
> >>High Bit Rate (HBR) audio playback to work. This was not required in
> >>earlier platforms when HBR was first introduced. The ICT bits are
> >>defined in Section 7.3.3.9 of the HDaudio 1.0a specification.
> >>
> >>Since the ICT bitfield was not specified for HDAudio 1.0 devices
> >>(before 2009), we only program it on machines more recent than
> >>Haswell.
> >>
> >>We tested that this fix is not needed on Baytrail-I (MinnowBoard
> >>Turbot) and believe by extension it also does not apply to Braswell.
> >>
> >>Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=98797
> >>
> >>Signed-off-by: Sriram Periyasamy <sriramx.periyasamy@intel.com>
> >>Signed-off-by: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
> >>Signed-off-by: Subhransu S. Prusty <subhransu.s.prusty@intel.com>
> >>---
> >>v2: move digi3 verb in Set section, only set ICT for haswell and newer
> >
> >Applied now with a slight fix (moving *_SET_* definition to the right
> >place).
>
> Thanks Takashi. Not sure what happened since I have a clear memory
> of doing that change and making a note of it...
Hi Takashi,
I think this patch should have also gone to stable. We didn't cc. Please
suggest whether we should submit it separately for stable.
Regards,
Subhransu
> _______________________________________________
> Alsa-devel mailing list
> Alsa-devel@alsa-project.org
> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
--
next prev parent reply other threads:[~2017-09-25 16:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-19 22:25 [PATCH v2] ALSA: hda - program ICT bits to support HBR audio Pierre-Louis Bossart
2017-09-20 10:00 ` Takashi Iwai
2017-09-20 13:12 ` Pierre-Louis Bossart
2017-09-25 14:56 ` Subhransu S. Prusty [this message]
2017-10-02 9:26 ` Takashi Iwai
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=20170925145649.GA5063@subhransu-desktop \
--to=subhransu.s.prusty@intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=sriramx.periyasamy@intel.com \
--cc=tiwai@suse.de \
/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