From: "Yang, Libin" <libin.yang@intel.com>
To: Takashi Iwai <tiwai@suse.de>,
"libin.yang@linux.intel.com" <libin.yang@linux.intel.com>
Cc: "Lin, Mengdong" <mengdong.lin@intel.com>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>
Subject: Re: [RFC PATCH v3 1/3] ALSA: hda - add DP mst verb support
Date: Fri, 21 Oct 2016 06:52:01 +0000 [thread overview]
Message-ID: <96A12704CE18D347B625EE2D4A099D194FA4A2F6@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <s5hoa2fghwj.wl-tiwai@suse.de>
> -----Original Message-----
> From: Takashi Iwai [mailto:tiwai@suse.de]
> Sent: Thursday, October 20, 2016 11:27 PM
> To: libin.yang@linux.intel.com
> Cc: alsa-devel@alsa-project.org; Yang, Libin <libin.yang@intel.com>; Lin,
> Mengdong <mengdong.lin@intel.com>
> Subject: Re: [alsa-devel] [RFC PATCH v3 1/3] ALSA: hda - add DP mst verb
> support
>
> On Thu, 13 Oct 2016 09:49:35 +0200,
> libin.yang@linux.intel.com wrote:
> >
> > From: Libin Yang <libin.yang@linux.intel.com>
> >
> > Add snd_hda_get_dev_select() and snd_hda_set_dev_select() functions
> > for DP MST audio support.
> >
> > Signed-off-by: Libin Yang <libin.yang@linux.intel.com>
> > ---
> > sound/pci/hda/hda_codec.c | 73
> > ++++++++++++++++++++++++++++++++++++++++++++---
> > sound/pci/hda/hda_codec.h | 3 ++
> > 2 files changed, 72 insertions(+), 4 deletions(-)
> >
> > diff --git a/sound/pci/hda/hda_codec.c b/sound/pci/hda/hda_codec.c
> > index 9913be8..caa2c9d 100644
> > --- a/sound/pci/hda/hda_codec.c
> > +++ b/sound/pci/hda/hda_codec.c
> > @@ -311,9 +311,16 @@ int snd_hda_get_conn_index(struct hda_codec
> > *codec, hda_nid_t mux, }
> EXPORT_SYMBOL_GPL(snd_hda_get_conn_index);
> >
> > -
> > -/* return DEVLIST_LEN parameter of the given widget */ -static
> > unsigned int get_num_devices(struct hda_codec *codec, hda_nid_t nid)
> > +/**
> > + * snd_hda_get_num_devices - get DEVLIST_LEN parameter of the given
> > +widget
> > + * @codec: the HDA codec
> > + * @nid: NID of the pin to parse
> > + *
> > + * Get the device entry number on the given widget.
> > + * This is a feature of DP MST audio. Each pin can
> > + * have several device entries in it.
>
> Try to fill more letters aligned in 80 columns, as we don't need to write a
> Haiku here.
Get it. Thanks :)
Regards,
Libin
>
>
> Takashi
next prev parent reply other threads:[~2016-10-21 6:52 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-13 7:49 [RFC PATCH v3 0/3] support DP MST audio libin.yang
2016-10-13 7:49 ` [RFC PATCH v3 1/3] ALSA: hda - add DP mst verb support libin.yang
2016-10-20 15:27 ` Takashi Iwai
2016-10-21 6:52 ` Yang, Libin [this message]
2016-10-13 7:49 ` [RFC PATCH v3 2/3] ALSA: hda - add DP mst audio support libin.yang
2016-10-20 15:34 ` Takashi Iwai
2016-10-21 8:24 ` Yang, Libin
2016-10-21 8:43 ` Takashi Iwai
2016-10-21 8:56 ` Yang, Libin
2016-10-21 9:05 ` Takashi Iwai
2016-10-21 12:25 ` Yang, Libin
2016-10-21 12:33 ` Takashi Iwai
2016-10-21 13:25 ` Yang, Libin
2016-10-24 7:09 ` Yang, Libin
2016-10-24 8:41 ` Takashi Iwai
2016-10-24 8:52 ` Yang, Libin
2016-10-13 7:49 ` [RFC PATCH v3 3/3] ALSA: Documentation about HDA DP MST pin init and connection libin.yang
2016-10-20 7:23 ` [RFC PATCH v3 0/3] support DP MST audio Yang, Libin
2016-10-20 8:46 ` 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=96A12704CE18D347B625EE2D4A099D194FA4A2F6@SHSMSX103.ccr.corp.intel.com \
--to=libin.yang@intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=libin.yang@linux.intel.com \
--cc=mengdong.lin@intel.com \
--cc=tiwai@suse.de \
/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.