From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org, Mark Brown <broonie@kernel.org>,
Kai Vehmanen <kai.vehmanen@linux.intel.com>
Subject: Re: [alsa-devel] [PATCH v4 0/9] adapt SOF to use snd-hda-codec-hdmi
Date: Mon, 16 Sep 2019 15:01:52 -0500 [thread overview]
Message-ID: <2ff72482-41a5-2655-d713-b91efd2601f5@linux.intel.com> (raw)
In-Reply-To: <s5hpnk0xcbu.wl-tiwai@suse.de>
On 9/16/19 2:36 PM, Takashi Iwai wrote:
> On Mon, 16 Sep 2019 17:59:06 +0200,
> Pierre-Louis Bossart wrote:
>>
>> On 9/12/19 9:21 AM, Kai Vehmanen wrote:
>>> Hi all,
>>>
>>> here's the 4th round for this series that adapts SOF to use
>>> snd-hda-codec-hdmi (patch_hdmi.c) codec driver instead of hdac_hdmi
>>> (soc/codecs/hdac_hdmi.c). The primary goal is to unify the HDMI codec
>>> implementation between DSP and non-DSP HDA configurations, offer same
>>> interface to user-space and reduce maintenance load for all.
>>
>> The series looks good to me so
>>
>> Reviewed-by: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
>>
>> I would recommend that we have a matching change for the Skylake
>> driver and validation that both SOF and cAVS/SST drivers can operate
>> with this mode set. Our goal is still to have coexistence between the
>> two drivers in a single build/distro, e.g. cAVS for SKL/KBL/APL and
>> SOF for newer platforms. This can be done in a follow-up patch but it
>> needs to be done before distros start selecting this common HDMI mode.
>>
>> The other concern I have is that we have other changes coming for
>> soc-acpi and machine drivers to deal with SoundWire, so it'd be nice
>> to have the changes mirrored between Mark and Takashi trees e.g. with
>> the merge of a fixed branch.
>
> In general it's already a bit too late to merge for 5.4, so the whole
> series will be after that, at most, hence we still have enough time :)
yes indeed, this was just to let you know we'll need extra work to
synchronize between you/Mark/Vinod, not to rush things through.
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
https://mailman.alsa-project.org/mailman/listinfo/alsa-devel
next prev parent reply other threads:[~2019-09-16 20:02 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-12 14:21 [alsa-devel] [PATCH v4 0/9] adapt SOF to use snd-hda-codec-hdmi Kai Vehmanen
2019-09-12 14:21 ` [alsa-devel] [PATCH v4 1/9] ALSA: hda/hdmi - implement mst_no_extra_pcms flag Kai Vehmanen
2019-09-15 9:39 ` Takashi Iwai
2019-09-12 14:21 ` [alsa-devel] [PATCH v4 2/9] ASoC: hdac_hda: add support for HDMI/DP as a HDA codec Kai Vehmanen
2019-09-12 14:21 ` [alsa-devel] [PATCH v4 3/9] ASoC: Intel: skl-hda-dsp-generic: use snd-hda-codec-hdmi Kai Vehmanen
2019-09-12 14:21 ` [alsa-devel] [PATCH v4 4/9] ASoC: Intel: skl-hda-dsp-generic: fix include guard name Kai Vehmanen
2019-09-12 14:21 ` [alsa-devel] [PATCH v4 5/9] ASoC: SOF: Intel: add support for snd-hda-codec-hdmi Kai Vehmanen
2019-09-12 14:21 ` [alsa-devel] [PATCH v4 6/9] ASoC: Intel: bxt-da7219-max98357a: common hdmi codec support Kai Vehmanen
2019-09-12 14:21 ` [alsa-devel] [PATCH v4 7/9] ASoC: Intel: glk_rt5682_max98357a: " Kai Vehmanen
2019-09-12 14:21 ` [alsa-devel] [PATCH v4 8/9] ASoC: intel: sof_rt5682: " Kai Vehmanen
2019-09-12 14:22 ` [alsa-devel] [PATCH v4 9/9] ASoC: Intel: bxt_rt298: " Kai Vehmanen
2019-09-16 15:59 ` [alsa-devel] [PATCH v4 0/9] adapt SOF to use snd-hda-codec-hdmi Pierre-Louis Bossart
2019-09-16 19:36 ` Takashi Iwai
2019-09-16 20:01 ` Pierre-Louis Bossart [this message]
2019-09-17 14:32 ` Kai Vehmanen
2019-09-17 11:32 ` Kai Vehmanen
2019-09-17 14:38 ` Pierre-Louis Bossart
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=2ff72482-41a5-2655-d713-b91efd2601f5@linux.intel.com \
--to=pierre-louis.bossart@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=kai.vehmanen@linux.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