From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Kai Vehmanen <kai.vehmanen@linux.intel.com>
Cc: tiwai@suse.de, alsa-devel@alsa-project.org,
Mark Brown <broonie@kernel.org>
Subject: Re: [alsa-devel] [PATCH v4 0/9] adapt SOF to use snd-hda-codec-hdmi
Date: Tue, 17 Sep 2019 09:38:05 -0500 [thread overview]
Message-ID: <c646b50d-7212-92a2-ce31-71971d88f85c@linux.intel.com> (raw)
In-Reply-To: <alpine.DEB.2.21.1909171415520.16459@zeliteleevi>
On 9/17/19 6:32 AM, Kai Vehmanen wrote:
> Hi,
>
> On Mon, 16 Sep 2019, Pierre-Louis Bossart wrote:
>
>> The series looks good to me so
>> Reviewed-by: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
>
> thank you Pierre and Takashi for the reviews!
>
>> 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 current patchset actually does allow that. You can select the common
> HDMI codec in kernel config, build both SOF and SST drivers and based on
> runtime selection of the platform, either SOF with patch_hdmi.c will be
> used or SST with hdac-hdmi. This is achieved by setting the
> common-hdmi-codec mach-params flag in sof/intel/hda.c, so with SST
> drivers, this will never be set.
>
> To change SST to use patch_hdmi.c as well, is a bigger effort. There
> are more (and much older) platforms impacted by the alsa mixer name
> changes. I'm not sure whether this is worth the trouble. But open to
> ideas here.
If the i915 interface was set in stone yes we could probably leave the
Skylake driver alone. But there are changes from time to time and bug
fixes that will require Intel to work on two parts of the tree, so
really wondering if we shouldn't just move to this common mode across
the board and remove hdac_hdmi.c. it doesn't need to be done at once but
it's not that crazy to aim for the next kernel release.
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
https://mailman.alsa-project.org/mailman/listinfo/alsa-devel
prev parent reply other threads:[~2019-09-17 14:39 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
2019-09-17 14:32 ` Kai Vehmanen
2019-09-17 11:32 ` Kai Vehmanen
2019-09-17 14:38 ` Pierre-Louis Bossart [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=c646b50d-7212-92a2-ce31-71971d88f85c@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