From: Takashi Iwai <tiwai@suse.de>
To: Cezary Rojewski <cezary.rojewski@intel.com>
Cc: alsa-devel@alsa-project.org, upstream@semihalf.com,
Kai Vehmanen <kai.vehmanen@linux.intel.com>,
harshapriya.n@intel.com, rad@semihalf.com,
pierre-louis.bossart@linux.intel.com, tiwai@suse.com,
hdegoede@redhat.com, broonie@kernel.org,
cujomalainey@chromium.org, lma@semihalf.com
Subject: Re: [PATCH 3/4] ALSA: hda: Update and expose codec register procedures
Date: Tue, 08 Feb 2022 18:14:16 +0100 [thread overview]
Message-ID: <s5hiltpqo0n.wl-tiwai@suse.de> (raw)
In-Reply-To: <c144c67d-e6a8-1baa-82e8-37065c053919@intel.com>
On Tue, 08 Feb 2022 17:34:47 +0100,
Cezary Rojewski wrote:
>
> On 2022-02-08 4:54 PM, Kai Vehmanen wrote:
> > Hi,
> >
> > On Mon, 7 Feb 2022, Cezary Rojewski wrote:
> >
> >> With few changes, snd_hda_codec_register() and its
> >> unregister-counterpart can be re-used by ASoC drivers. While at it,
> >> provide kernel doc for the exposed functions.
> >
> > thanks, there is no doubt room to improve the HDA<->asoc interaction
> > still and increase reuse. Some questions:
>
> Thanks for taking time in reviewing the patches, Kai!
>
> >> Due to ALSA-device vs ASoC-component organization differences, new
> >> 'snddev_managed' argument is specified allowing for better control over
> >> codec registration process.
> >
> > Can you maybe clarify this? The existing code to handle the different
> > paths is already quite hairy (e.g. code in
> > hda_codec.c:snd_hda_codec_dev_free() that does different actions
> > depending on whether "codec->core.type == HDA_DEV_LEGACY) is true or
> > false), so we'd need to have very clear semantics for the
> > "snddev_managed".
>
> It's rather straightforward - ASoC does not provide you with pointer
> to struct snd_card until all components are accounted
> for. snd_hda_codec_device_new() in its current form needs such
> information upfront though. As we want to create only as many DAIs
> (and other ASoC components like links and routes) as needed, codec's
> ->pcm_list_head needs to be built before codec's probing can be
> completed. But in order to have hda codec to fill ->pcm_list_head for,
> you need to create it. And in order to create it you need snd_card
> pointer which ASoC won't give you before you complete component
> probing.
>
> Typical chicken and egg problem. And that's why additional option is
> provided - it solves that problem.
Hmm, but snd_hda_codec_device_new() also does the actual hardware
initialization including the power-up sequence, and there is a call
snd_component_add() with the card instance. How the function would
work properly before the card instantiation? You seem to have handled
only snd_device_new() and not touching other code where the card (or
the hardware access) is involved.
If the purpose is to get the fields of snd_hda_codec to be
initialized, those init code can be factored out to another function,
so that it works certainly without card.
Takashi
next prev parent reply other threads:[~2022-02-08 17:15 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-07 11:49 [PATCH 0/4] ALSA: hda: Expose codec organization functions Cezary Rojewski
2022-02-07 11:49 ` [PATCH 1/4] ALSA: hda: Add snd_hdac_ext_bus_link_at() helper Cezary Rojewski
2022-02-07 11:49 ` [PATCH 2/4] ALSA: hda: Update and expose snd_hda_codec_device_init() Cezary Rojewski
2022-02-07 11:49 ` [PATCH 3/4] ALSA: hda: Update and expose codec register procedures Cezary Rojewski
2022-02-08 15:54 ` Kai Vehmanen
2022-02-08 16:34 ` Cezary Rojewski
2022-02-08 17:14 ` Takashi Iwai [this message]
2022-02-09 10:21 ` Cezary Rojewski
2022-02-09 10:38 ` Cezary Rojewski
2022-02-09 14:19 ` Takashi Iwai
2022-02-08 17:46 ` Pierre-Louis Bossart
2022-02-09 12:05 ` Cezary Rojewski
2022-02-09 16:08 ` Pierre-Louis Bossart
2022-02-11 14:42 ` Cezary Rojewski
2022-02-11 15:23 ` Pierre-Louis Bossart
2022-02-14 9:54 ` Cezary Rojewski
2022-02-07 11:49 ` [PATCH 4/4] ALSA: hda: Expose codec cleanup and power-save functions Cezary Rojewski
2022-02-07 12:35 ` [PATCH 0/4] ALSA: hda: Expose codec organization functions Pierre-Louis Bossart
2022-02-08 10:00 ` 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=s5hiltpqo0n.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=cezary.rojewski@intel.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox