From: Takashi Iwai <tiwai@suse.de>
To: Vinod Koul <vinod.koul@intel.com>
Cc: patches.audio@intel.com, alsa-devel@alsa-project.org,
broonie@kernel.org,
"Subhransu S. Prusty" <subhransu.s.prusty@intel.com>,
lgirdwood@gmail.com
Subject: Re: [PATCH v2 5/7] ALSA: hda - Use ops instead of directly accessing chmap helpers
Date: Thu, 03 Mar 2016 12:39:05 +0100 [thread overview]
Message-ID: <s5hr3fr6bae.wl-tiwai@suse.de> (raw)
In-Reply-To: <20160303112923.GK11154@localhost>
On Thu, 03 Mar 2016 12:29:23 +0100,
Vinod Koul wrote:
>
> On Wed, Mar 02, 2016 at 05:03:10PM +0100, Takashi Iwai wrote:
> > On Wed, 02 Mar 2016 13:03:26 +0100,
> > Subhransu S. Prusty wrote:
> > >
> > > Added more ops to the chmap object, so most of the helpers can be
> > > accessed through ops instead instead of directly calling them.
> >
> > Too many instead :)
> >
> > > With this moving the chmap helpers to core will be easy.
> >
> > Well, although I asked about reduction of exported stuff, I don't
> > think it's worth to put everything in ops. If any of them would be
> > overridden, it's good to have as an ops. If not, it's fine to have
> > exported symbols. These are just a few entries, not over 20.
>
> I think the thought was that patch_hdmi and ASoC driver will use defaults
> whereas the patch_nvidia etc will override with their own stuff..
Yes, but are these new ops overridden actually?
Takashi
next prev parent reply other threads:[~2016-03-03 11:39 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-02 12:03 [PATCH v2 0/7] ALSA: hda: Move chmap helpers to core Subhransu S. Prusty
2016-03-02 12:03 ` [PATCH v2 1/7] ALSA: hda - Create common chmap object Subhransu S. Prusty
2016-03-02 12:03 ` [PATCH v2 2/7] ALSA: hda - Register chmap obj as priv data instead of codec Subhransu S. Prusty
2016-03-02 16:05 ` Takashi Iwai
2016-03-02 12:03 ` [PATCH v2 3/7] ALSA: hda - Use hdmi name space for CEA spk alloc structure Subhransu S. Prusty
2016-03-02 16:09 ` Takashi Iwai
2016-03-02 12:03 ` [PATCH v2 4/7] ALSA: hda - Add hdmi chmap verb programming ops to chmap object Subhransu S. Prusty
2016-03-02 12:03 ` [PATCH v2 5/7] ALSA: hda - Use ops instead of directly accessing chmap helpers Subhransu S. Prusty
2016-03-02 16:03 ` Takashi Iwai
2016-03-03 11:29 ` Vinod Koul
2016-03-03 11:39 ` Takashi Iwai [this message]
2016-03-03 11:54 ` Subhransu S. Prusty
2016-03-03 13:37 ` Takashi Iwai
2016-03-02 12:03 ` [PATCH v2 6/7] ALSA: hda - Move chmap support helpers/ops to core Subhransu S. Prusty
2016-03-02 12:03 ` [PATCH v2 7/7] ALSA: hda - Use snd_hdmi namespace prefix for printing ch alloc api Subhransu S. Prusty
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=s5hr3fr6bae.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=patches.audio@intel.com \
--cc=subhransu.s.prusty@intel.com \
--cc=vinod.koul@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 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.