All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: liam.r.girdwood@linux.intel.com, alsa-devel@alsa-project.org,
	broonie@kernel.org, Bard liao <yung-chuan.liao@linux.intel.com>
Subject: Re: [PATCH] ASoC: Intel: hdac_hdmi: add Icelake support
Date: Mon, 12 Nov 2018 08:00:36 -0600	[thread overview]
Message-ID: <ad05386f-af75-3bf2-bc76-628928fc4fea@linux.intel.com> (raw)
In-Reply-To: <s5h5zx3o6um.wl-tiwai@suse.de>


>>> Also, it'd be helpful if you fix the same for the legacy HD-audio HDMI
>>> codec driver.
>> Our intention was to revisit differences between legacy and non-legacy
>> in a separate patch if that's all right with you. We've identified
>> missing IDs and other things that should be fixed separately.
> Sure, I don't mean to fix both in a single patch, but just to remind
> you guys not to forget about that code path.

Yes, this is very much on our radar. I don't like the current approach 
where patch_hdmi.c and hdac_hdmi.c have duplicated/different definitions 
for the same things or capabilities that can't be traced back to 
hardware documentation or known issues. the main issue I am facing with 
the legacy path is ironically validation. Our team necessarily have 
access to all commercially-available platforms listed in those files or 
when we do it's not necessarily easy to work with the latest kernel or 
handle BIOS issues - we'll do what we can though.

And btw the big topic is still how we provide distributions the means to 
handle a 'graceful' fallback from DSP-enabled solutions (SST or SOF) to 
legacy HDAudio, it's already popped up for cases where we have HDaudio 
solutions with DMICs.

-Pierre

  parent reply	other threads:[~2018-11-12 14:00 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-10 21:18 [PATCH] ASoC: Intel: hdac_hdmi: add Icelake support Bard liao
2018-11-11  8:55 ` Takashi Iwai
2018-11-11 15:10   ` Pierre-Louis Bossart
2018-11-11 17:35     ` Takashi Iwai
2018-11-12 13:04       ` Bard liao
2018-11-12 13:20         ` Takashi Iwai
2018-11-12 14:00       ` Pierre-Louis Bossart [this message]
2018-11-14 14:53         ` Takashi Iwai
2018-11-14 16:23           ` Pierre-Louis Bossart
2018-11-14 16:36             ` Takashi Iwai
2018-11-14 16:41               ` Pierre-Louis Bossart
2018-11-14 16:44                 ` Takashi Iwai
2018-11-14 16:55                   ` Pierre-Louis Bossart
2018-11-16 13:49           ` Takashi Iwai
2018-11-16 14:11             ` Pierre-Louis Bossart
2018-11-16 17:44               ` Takashi Iwai
2018-11-20 16:02                 ` Pierre-Louis Bossart
2018-11-12 13:57 ` Pierre-Louis Bossart
2018-11-13 19:46 ` Applied "ASoC: Intel: hdac_hdmi: add Icelake support" to the asoc tree Mark Brown

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=ad05386f-af75-3bf2-bc76-628928fc4fea@linux.intel.com \
    --to=pierre-louis.bossart@linux.intel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=liam.r.girdwood@linux.intel.com \
    --cc=tiwai@suse.de \
    --cc=yung-chuan.liao@linux.intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.