All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Libin Yang <libin.yang@linux.intel.com>
Cc: alsa-devel@alsa-project.org, intel-gfx@lists.freedesktop.org,
	Dave Airlie <airlied@redhat.com>,
	daniel.vetter@intel.com
Subject: Re: [PATCH V4 2/2] drm/i915: start adding dp mst audio
Date: Sun, 13 Dec 2015 09:27:36 +0100	[thread overview]
Message-ID: <s5hfuz6eosn.wl-tiwai@suse.de> (raw)
In-Reply-To: <s5hwpsljd2j.wl-tiwai@suse.de>

On Fri, 11 Dec 2015 15:05:08 +0100,
Takashi Iwai wrote:
> 
> On Fri, 11 Dec 2015 07:07:53 +0100,
> Libin Yang wrote:
> > 
> > Add Takashi and ALSA mail list.
> > 
> > On 12/10/2015 05:02 PM, Daniel Vetter wrote:
> > > On Tue, Dec 08, 2015 at 04:01:20PM +0800, Libin Yang wrote:
> > >> Hi all,
> > >>
> > >> Any comments on the patches?
> > >
> > > Sorry, simply fell through the cracks since Ander is on vacation. Takashi
> > > is working on some cleanup patches to have a port->encoder mapping for the
> > > audio side of i915. His patch cleans up all the existing audio code in
> > > i915, but please work together with him to align mst code with the new
> > > style.
> > >
> > > Both patches queued for next.
> > 
> > Yes, I have seen Takashi's patches. I will check the patches.
> 
> The patch like below should work; it sets/clears the reverse mapping
> dynamically for the MST encoder.

This might be too shortsighted and broken -- if multiple devices are
hook on the same port...

Now I wonder which graphics part actually corresponds to the HD-audio
widget.  So far, we supposed that each pin widget 0x05-0x07
corresponds to the digital port B-D in the fixed manner.  If so, how
is the case where two devices on the same port?  In the codec level,
we get an unsolicited event on the same pin but check with the
different device index.  What would be a unique index instead that can
be passed via the component ops?

Then, another question is which audio converter widget is used and how
is set up, if multiple devices were on the same pin.

Libin, do you have any git branch where MST really works?  I should
test it at first to confirm that it actually works on my test system.


thanks,

Takashi
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2015-12-13  8:27 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-02  6:09 [PATCH V4 1/2] dp/mst: add SDP stream support libin.yang
2015-12-02  6:09 ` [PATCH V4 2/2] drm/i915: start adding dp mst audio libin.yang
2015-12-08  8:01   ` Libin Yang
2015-12-10  9:02     ` Daniel Vetter
2015-12-11  6:07       ` Libin Yang
2015-12-11 10:43         ` Takashi Iwai
2015-12-11 13:58           ` Takashi Iwai
2015-12-21  8:31             ` [alsa-devel] " Libin Yang
2015-12-14  9:33           ` Jani Nikula
2015-12-14  9:40             ` Takashi Iwai
2015-12-14 10:34               ` Jani Nikula
2015-12-14 10:41                 ` Takashi Iwai
2015-12-11 14:05         ` Takashi Iwai
2015-12-13  8:27           ` Takashi Iwai [this message]
2015-12-11  6:09 ` [PATCH V4 1/2] dp/mst: add SDP stream support Libin Yang

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=s5hfuz6eosn.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=airlied@redhat.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=daniel.vetter@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=libin.yang@linux.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.