From: Takashi Iwai <tiwai@suse.de>
To: "Jie, Yang" <yang.jie@intel.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"broonie@kernel.org" <broonie@kernel.org>,
"Girdwood, Liam R" <liam.r.girdwood@intel.com>,
David Henningsson <david.henningsson@canonical.com>
Subject: Re: [PATCH v4 0/5] ALSA: jack: Refactoring for jack kctls
Date: Wed, 08 Apr 2015 11:22:23 +0200 [thread overview]
Message-ID: <s5hr3rvnfe8.wl-tiwai@suse.de> (raw)
In-Reply-To: <E7B1D079BA13FB44A978CC8F69C7D6A905506247@shsmsx102.ccr.corp.intel.com>
At Wed, 8 Apr 2015 09:18:10 +0000,
Jie, Yang wrote:
>
> > >> }
> > >>
> > >> Now the HDA looks more like the ASoC variant. Yang, what do you think
> > >> about that? That would make the API simpler, wouldn't it?
> > >
> > > Here repeat what I stated in another reply:
> > >
> > > For jack creating, we use the same API -- snd_jack_new();
> > >
> > > For kctl creating, yes, we use different APIs:
> > > snd_jack_kctl_new() for input jacks(HDA),
> > > snd_jack_add_kctls() for kctl jacks(ASoC).
> > >
> > > There are 2 reasons that I made them different:
> > > 1. a. for HDA phantom jack, in the old/exist logic,
> > > __snd_hda_jack_add_kctl() will also call snd_kctl_jack_new() and
> > > snd_hda_ctl_add(), it will create kctls and add them to card(also
> > > assigning some arrays, they are different with calling
> > > snd_ctl_add() only, which is what we will do for ASoC kctl adding);
> >
> > Actually, now that I look at snd_hda_ctl_add, I don't know why we need to
> > call it for HDA jacks. There does not seem to be anything relevant for HDA
> > jacks there. I think we can just call snd_ctl_add for HDA jacks too.
>
> OK, then it may make life easier. Hi Takashi, you agree with this?
> Do we need add those kctls to the HDA codec, or to hda_nid_item?
It's been added in the local list to manage the kctls belonging to a
codec more easily. But if snd_hda_codec_free() and _reset() can
remove them gracefully, there is no big reason to keep tracking
there.
Takashi
next prev parent reply other threads:[~2015-04-08 9:22 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-03 12:07 [PATCH v4 0/5] ALSA: jack: Refactoring for jack kctls Jie Yang
2015-04-03 12:07 ` [PATCH v4 1/5] ALSA: jack: create jack kcontrols for every jack input Jie Yang
2015-04-03 12:07 ` [PATCH v4 2/5] ALSA: jack: add a parameter to pass kctl for snd_jack_new Jie Yang
2015-04-03 12:07 ` [PATCH v4 3/5] ALSA: hda - Update to use the new jack kctls method Jie Yang
2015-04-03 12:07 ` [PATCH v4 4/5] ASoC: jack: create kctls according to jack pins info Jie Yang
2015-04-03 12:07 ` [PATCH v4 5/5] ALSA: jack: remove export snd_kctl_jack_new() Jie Yang
2015-04-06 16:11 ` [PATCH v4 0/5] ALSA: jack: Refactoring for jack kctls Mark Brown
2015-04-07 16:06 ` Takashi Iwai
2015-04-08 2:53 ` Jie, Yang
2015-04-08 4:39 ` Raymond Yau
2015-04-08 7:20 ` David Henningsson
2015-04-08 7:34 ` Takashi Iwai
2015-04-08 7:49 ` David Henningsson
2015-04-08 7:59 ` Jie, Yang
2015-04-08 8:27 ` David Henningsson
2015-04-08 9:18 ` Jie, Yang
2015-04-08 9:22 ` Takashi Iwai [this message]
2015-04-08 14:14 ` Jie, Yang
2015-04-08 14:29 ` Takashi Iwai
2015-04-08 18:47 ` David Henningsson
2015-04-08 18:55 ` Takashi Iwai
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=s5hr3rvnfe8.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=david.henningsson@canonical.com \
--cc=liam.r.girdwood@intel.com \
--cc=yang.jie@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox