All of lore.kernel.org
 help / color / mirror / Atom feed
From: Cezary Rojewski <cezary.rojewski@intel.com>
To: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>,
	Kai Vehmanen <kai.vehmanen@linux.intel.com>
Cc: alsa-devel@alsa-project.org, upstream@semihalf.com,
	harshapriya.n@intel.com, rad@semihalf.com, tiwai@suse.com,
	hdegoede@redhat.com, Mark Brown <broonie@kernel.org>,
	amadeuszx.slawinski@linux.intel.com, cujomalainey@chromium.org,
	lma@semihalf.com
Subject: Re: [PATCH 02/14] ASoC: codecs: Add HD-Audio codec driver
Date: Tue, 10 May 2022 09:36:55 +0200	[thread overview]
Message-ID: <b872cdd1-14b9-39fa-7d46-f6a3f20131f7@intel.com> (raw)
In-Reply-To: <914e993e-a440-74a6-e5d8-3589b0f4083b@linux.intel.com>

On 2022-05-09 5:55 PM, Pierre-Louis Bossart wrote:> On 5/9/22 09:33, Kai 
Vehmanen wrote:

>> The fixed DAI capabilities of hdac_hda.c are indeed not ideal (although in
>> practise hasn't really been an issue so far) and the approach in the new
>> hda.c seems indeed more robust. We do have a lot of existing machine
>> drivers (and shipping DSP topologies that we need to keep working), so
>> transitioning e.g. SOF machine drivers is not going to be straightforward.
>> For new mach drivers, this could be considered.
> 
> We've just simplified the HDAudio topologies to support the Analog
> playback and capture only, for both IPC3 and IPC4 cases, so there's
> really no plan to support such dynamic capabilities. I am not even aware
> of a single device available in our team where the digital inputs and
> outputs are exposed on a connector, so even if we wanted we couldn't
> test this dynamic part.


As I've explained in one of the previous posts, you can always use 
topology to limit the number of FE(s) available while still adhering to 
behavior found in sound/pci/hda. hda.c is a prime example of how ASoC 
HD-Audio can align with ALSA HD-Audio in 1:1 fashion. hdac_hda.c does 
not do that a) because of hardcodes b) following HDA_DEV_ASOC.

Having no behavioral differences is a major gain here, fix one place, 
enjoy both solutions. By 'one place' I mean sound/pci/hda of course as 
there should be no logic outside of that directory.

>> So while not ideal, maybe it makes sense to have two wrappers, hdac_hda.c
>> for mach drivers with fixed DAI configuration, and the new hda.c that
>> supports dynamic configuration (but requires mach drivers that match
>> this). If the old SST driver is deprecated, we can then proceed to remove
>> hdac_hdmi.c from the tree, so there's some savings.
> 
> Such removal isn't going to happen for at least 3+ years, the time it
> takes for the slowest distros and users to switch kernels.
> 
> that means we're going to have to maintain for the foreseeable future:
> 
> hdac_hdmi.c: used only by SST
> hdac_hda.c: used by both SST and SOF
> hda.c: used only by AVS.


I and the team maintained almost all the solutions found in 
sound/soc/intel for couple of years already, doing couple more with the 
old stuff is not a problem. Don't believe 'sit and do nothing' is the 
answer here, not sure if this is even an option - but I'm sure that the 
final effect is going to be worth the initial cost.


Regards,
Czarek

  reply	other threads:[~2022-05-10  7:38 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-27  8:18 [PATCH 00/14] ASoC: Intel: avs: Machine boards and HDA codec support Cezary Rojewski
2022-04-27  8:18 ` [PATCH 01/14] ALSA: Add snd_pcm_direction_name() helper Cezary Rojewski
2022-04-27  8:18 ` [PATCH 02/14] ASoC: codecs: Add HD-Audio codec driver Cezary Rojewski
2022-04-27 15:47   ` Pierre-Louis Bossart
2022-05-06 13:12     ` Mark Brown
2022-05-06 13:39       ` Cezary Rojewski
2022-05-06 14:56         ` Pierre-Louis Bossart
2022-05-06 15:28           ` Cezary Rojewski
2022-05-06 16:17             ` Pierre-Louis Bossart
2022-05-09 14:33               ` Kai Vehmanen
2022-05-09 15:55                 ` Pierre-Louis Bossart
2022-05-10  7:36                   ` Cezary Rojewski [this message]
2022-04-27  8:18 ` [PATCH 03/14] ASoC: Intel: avs: Add HDAudio machine board Cezary Rojewski
2022-04-27  8:18 ` [PATCH 04/14] ASoC: Intel: avs: Add DMIC " Cezary Rojewski
2022-04-27  8:18 ` [PATCH 05/14] ASoC: Intel: avs: Add ssp-test " Cezary Rojewski
2022-05-10 11:12   ` Cezary Rojewski
2022-04-27  8:18 ` [PATCH 06/14] ASoC: Intel: avs: Add rt274 " Cezary Rojewski
2022-04-27  8:18 ` [PATCH 07/14] ASoC: Intel: avs: Add rt286 " Cezary Rojewski
2022-04-27  8:18 ` [PATCH 08/14] ASoC: Intel: avs: Add rt298 " Cezary Rojewski
2022-04-27  8:18 ` [PATCH 09/14] ASoC: Intel: avs: Add rt5682 " Cezary Rojewski
2022-04-27  8:18 ` [PATCH 10/14] ASoC: Intel: avs: Add nau8825 " Cezary Rojewski
2022-04-27  8:18 ` [PATCH 11/14] ASoC: Intel: avs: Add ssm4567 " Cezary Rojewski
2022-04-27  8:19 ` [PATCH 12/14] ASoC: Intel: avs: Add max98357a " Cezary Rojewski
2022-04-27  8:19 ` [PATCH 13/14] ASoC: Intel: avs: Add max98373 " Cezary Rojewski
2022-04-27  8:19 ` [PATCH 14/14] ASoC: Intel: avs: Add da7219 " Cezary Rojewski

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=b872cdd1-14b9-39fa-7d46-f6a3f20131f7@intel.com \
    --to=cezary.rojewski@intel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=amadeuszx.slawinski@linux.intel.com \
    --cc=broonie@kernel.org \
    --cc=cujomalainey@chromium.org \
    --cc=harshapriya.n@intel.com \
    --cc=hdegoede@redhat.com \
    --cc=kai.vehmanen@linux.intel.com \
    --cc=lma@semihalf.com \
    --cc=pierre-louis.bossart@linux.intel.com \
    --cc=rad@semihalf.com \
    --cc=tiwai@suse.com \
    --cc=upstream@semihalf.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.