alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: "Subhransu S. Prusty" <subhransu.s.prusty@intel.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: patches.audio@intel.com, Vinod Koul <vinod.koul@intel.com>,
	alsa-devel@alsa-project.org, broonie@kernel.org,
	lgirdwood@gmail.com
Subject: Re: [PATCH 2/3] ALSA: hda - Move chmap support helpers/structures to core
Date: Mon, 22 Feb 2016 16:23:34 +0530	[thread overview]
Message-ID: <20160222105330.GA8048@subhransu-desktop> (raw)
In-Reply-To: <s5hwppx2i5i.wl-tiwai@suse.de>

On Mon, Feb 22, 2016 at 10:44:57AM +0100, Takashi Iwai wrote:
> On Mon, 22 Feb 2016 09:00:39 +0100,
> Subhransu S. Prusty wrote:
> > +void snd_hdmi_init_channel_allocations(void);
> > +int snd_hdmi_get_channel_allocation_order(int ca);
> > +int snd_hdmi_get_active_channels(int ca);
> > +struct cea_channel_speaker_allocation *snd_hdmi_get_ch_alloc_from_ca(int ca);
> > +void snd_hdmi_print_channel_allocation(int spk_alloc, char *buf, int buflen);
> > +int snd_hdmi_channel_allocation(struct hdac_device *codec,
> > +		   int spk_alloc, int channels);
> > +int snd_hdmi_to_spk_mask(unsigned char c);
> > +int snd_hdmi_spk_to_chmap(int spk);
> > +int snd_hdmi_manual_channel_allocation(int chs, unsigned char *map);
> > +void snd_hdmi_setup_channel_mapping(struct hdmi_chmap *chmap,
> > +		       hda_nid_t pin_nid, bool non_pcm, int ca,
> > +		       int channels, unsigned char *map,
> > +		       bool chmap_set);
> > +int snd_hdmi_pin_set_slot_channel(struct hdac_device *codec, hda_nid_t pin_nid,
> > +					     int asp_slot, int channel);
> > +int snd_hdmi_pin_get_slot_channel(struct hdac_device *codec, hda_nid_t pin_nid,
> > +					     int asp_slot);
> > +void snd_hdmi_set_channel_count(struct hdac_device *codec,
> > +			   hda_nid_t cvt_nid, int chs);
> > +int snd_hdmi_chmap_cea_alloc_validate_get_type(
> > +		struct cea_channel_speaker_allocation *cap,
> > +		int channels);
> > +void snd_hdmi_cea_alloc_to_tlv_chmap(
> > +		struct cea_channel_speaker_allocation *cap,
> > +		unsigned int *chmap, int channels);
> > +int snd_hdmi_add_chmap_ctls(struct snd_pcm *pcm, int pcm_idx,
> > +				struct hdmi_chmap *chmap);
> 
> Do we really need to export all these?  Can't be they somehow
> self-contained?

Yes, I think we can do this by using common chmap ops instance and driver
can override the specific handlers. Will check for other APIs as well.

> 
> 
> Takashi

-- 

  reply	other threads:[~2016-02-22 10:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-22  8:00 [PATCH 0/3] ALSA: hda: Move chmap helpers to core Subhransu S. Prusty
2016-02-22  8:00 ` [PATCH 1/3] ALSA: hda - Create common chmap object Subhransu S. Prusty
2016-02-22  9:32   ` Takashi Iwai
2016-02-22  9:44     ` Subhransu S. Prusty
2016-02-22  8:00 ` [PATCH 2/3] ALSA: hda - Move chmap support helpers/structures to core Subhransu S. Prusty
2016-02-22  9:44   ` Takashi Iwai
2016-02-22 10:53     ` Subhransu S. Prusty [this message]
2016-02-22  8:00 ` [PATCH 3/3] ALSA: hda - Use the helpers from HDA core 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=20160222105330.GA8048@subhransu-desktop \
    --to=subhransu.s.prusty@intel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=lgirdwood@gmail.com \
    --cc=patches.audio@intel.com \
    --cc=tiwai@suse.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).