From: Takashi Iwai <tiwai@suse.de>
To: "Subhransu S. Prusty" <subhransu.s.prusty@intel.com>
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 v2 2/7] ALSA: hda - Register chmap obj as priv data instead of codec
Date: Wed, 02 Mar 2016 17:05:43 +0100 [thread overview]
Message-ID: <s5hlh60sw4o.wl-tiwai@suse.de> (raw)
In-Reply-To: <1456920208-1172-3-git-send-email-subhransu.s.prusty@intel.com>
On Wed, 02 Mar 2016 13:03:23 +0100,
Subhransu S. Prusty wrote:
>
> With this chmap object is added as private data and new ops are
> added to access driver specific chmap.
>
> Signed-off-by: Subhransu S. Prusty <subhransu.s.prusty@intel.com>
> Signed-off-by: Vinod Koul <vinod.koul@intel.com>
> ---
> include/sound/hdmi_chmap.h | 6 +++
> sound/pci/hda/patch_hdmi.c | 100 ++++++++++++++++++++++++++++++---------------
> 2 files changed, 72 insertions(+), 34 deletions(-)
>
> diff --git a/include/sound/hdmi_chmap.h b/include/sound/hdmi_chmap.h
> index 32087f1..c7702ef9 100644
> --- a/include/sound/hdmi_chmap.h
> +++ b/include/sound/hdmi_chmap.h
> @@ -30,6 +30,12 @@ struct hdmi_chmap_ops {
>
> /* check that the user-given chmap is supported */
> int (*chmap_validate)(int ca, int channels, unsigned char *chmap);
> +
> + void (*get_chmap)(struct hdac_device *hdac, int pcm_idx,
> + unsigned char *chmap);
> + void (*set_chmap)(struct hdac_device *hdac, int pcm_idx,
> + unsigned char *chmap, int prepared);
> + bool (*is_monitor_connected)(struct hdac_device *hdac, int pcm_idx);
This name is rather confusing. Actually, this function doesn't mean
the monitor connected state. It indicates rather whether any pin is
assigned to the given PCM. It may return false only for devices with
dynamic PCM assignment. For the rest, it's always true.
Takashi
next prev parent reply other threads:[~2016-03-02 16:05 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 [this message]
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
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=s5hlh60sw4o.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.