From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: "Lin, Mengdong" <mengdong.lin@intel.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"Zanoni, Paulo R" <paulo.r.zanoni@intel.com>,
Takashi Iwai <tiwai@suse.de>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
dri-devel <dri-devel@lists.freedesktop.org>,
"Barnes, Jesse" <jesse.barnes@intel.com>
Subject: Re: Need your advice: Add a new communication inteface between HD-Audio and Gfx drivers for hotplug notification/ELD update
Date: Tue, 18 Feb 2014 16:22:32 +0200 [thread overview]
Message-ID: <20140218142232.GS3852@intel.com> (raw)
In-Reply-To: <F46914AEC2663F4A9BB62374E5EEF8F82B277FF5@SHSMSX101.ccr.corp.intel.com>
On Tue, Feb 18, 2014 at 01:58:22PM +0000, Lin, Mengdong wrote:
> Sorry to pick up this thread after a long time.
>
> > -----Original Message-----
> > From: daniel.vetter@ffwll.ch [mailto:daniel.vetter@ffwll.ch] On Behalf Of
> > Daniel Vetter
> > Sent: Thursday, January 23, 2014 4:27 PM
> > To: Takashi Iwai
>
> > On Thu, Jan 23, 2014 at 8:57 AM, Takashi Iwai <tiwai@suse.de> wrote:
> > >> Thanks for clarification!
> > >> Maybe we can add output info (eg. display port number) to the eld entries
> > under /proc/asound/cardx. Is it okay?
> > >
> > > It's possible, but the proc file is just a help. It can't be the API.
> > > For accessing the information, we'll need some new API, or let inform
> > > via sysfs of the new device.
> >
> > Links in sysfs sound like the best approach. drm already has nodes for each
> > connector, so on the gfx side there's a natural endpoint already.
> > sysfs links also avoids any naming issues from the start, e.g. the above DP
> > connector id might lead to clashes with multiple cards.
>
> Hi Daniel,
>
> Is there a 1:1 mapping between these connector nodes and ports of Gfx display engine?
> Eg. For Haswell Ultrabook, under /sys/devices/pci0000:00/0000:00:02.0/drm/card0/
> There are four connector nodes,
> card0-DP-1 -> DDI port B
> card0-eDP-1/ -> DDI port A
> card0-HDMI-A-1/ -> DDI Port C
> card0-HDMI-A-2/ -> Which DDI port ? Haswell-ULT does not support port D, and I think port E is for VGA.
There's no fixed mapping with the port and the connector name. The
number in the connector name is basically just a running number per
connector type. However I do believe we do register the connectors
in the order of the ports more or less always, so you can
*sometimes* deduce the port name from the connector.
I suppose in this example HDMI-A-1 is port B, HDMI-A-2 is port C, and
DP-1 can be either port B or port C. DP++ is the reason why we have
overlapping DP and HDMI connectors for the same port.
>
> Hi Takashi,
>
> To make user space figure out which audio output is connected to which screen (connector), maybe we can define a new ALSA control for each HDMI/DP PCM device:
> e.g. numid=x,iface=PCM,name='Screen',device=3
> Reading the control will return the name of the DRM connector nodes like ' card0-DP-1'. The audio driver can get the connector name from the gfx driver.
>
> For DP1.2 Multi-stream transport, it's not supported by i915 and HD-A driver now. But probably there will be sub-nodes for the DP connector node in the future and an index in their name can be used distinguish monitors connected to the same DP port, like card0-DP-1.1, card0-DP-1.2, card0-DP-1.3 ... These names can be used by the above ALSA PCM 'Screen' control, so we can still know which audio output is to which monitor.
>
> Thanks
> Mengdong
>
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/intel-gfx
--
Ville Syrjälä
Intel OTC
next prev parent reply other threads:[~2014-02-18 14:22 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-21 12:35 Need your advice: Add a new communication inteface between HD-Audio and Gfx drivers for hotplug notification/ELD update Lin, Mengdong
2014-01-21 13:10 ` Daniel Vetter
2014-01-21 13:11 ` Daniel Vetter
2014-01-22 12:48 ` Lin, Mengdong
2014-01-22 14:18 ` Daniel Vetter
2014-01-22 15:04 ` [Intel-gfx] " Rob Clark
2014-01-22 15:20 ` Daniel Vetter
2014-01-22 15:45 ` Rob Clark
2014-01-22 17:23 ` Takashi Iwai
2014-01-22 18:15 ` [Intel-gfx] " Rob Clark
2014-01-22 17:19 ` Takashi Iwai
2014-01-23 6:35 ` Lin, Mengdong
2014-01-23 7:57 ` Takashi Iwai
2014-01-23 8:13 ` Jaroslav Kysela
2014-01-23 8:26 ` Daniel Vetter
2014-01-24 8:23 ` Raymond Yau
2014-01-24 17:38 ` [alsa-devel] " Alex Deucher
2014-02-18 13:58 ` Lin, Mengdong
2014-02-18 14:22 ` Ville Syrjälä [this message]
2014-02-19 9:08 ` Lin, Mengdong
2014-02-19 11:29 ` Ville Syrjälä
2014-02-20 5:15 ` Lin, Mengdong
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=20140218142232.GS3852@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jesse.barnes@intel.com \
--cc=mengdong.lin@intel.com \
--cc=paulo.r.zanoni@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.