From: "Ser, Simon" <simon.ser@intel.com>
To: "daniel@ffwll.ch" <daniel@ffwll.ch>,
"christian.koenig@amd.com" <christian.koenig@amd.com>
Cc: "sunpeng.li@amd.com" <sunpeng.li@amd.com>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"Nicholas.Kazlauskas@amd.com" <Nicholas.Kazlauskas@amd.com>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>
Subject: Re: Linking ALSA playback devices and DRM connectors
Date: Thu, 6 Jun 2019 09:17:38 +0000 [thread overview]
Message-ID: <6bafad8875cf21abdd3c0f2a093c8bd2625b33df.camel@intel.com> (raw)
In-Reply-To: <CAKMK7uHQ-hS7s_OZuyGjn19tqmz3f-DtcRiD=bjujK1oYHO9tA@mail.gmail.com>
On Tue, 2019-06-04 at 17:24 +0200, Daniel Vetter wrote:
> On Tue, Jun 4, 2019 at 5:15 PM Christian König
> <ckoenig.leichtzumerken@gmail.com> wrote:
> > Am 04.06.19 um 17:05 schrieb Ser, Simon:
> > > Hi,
> > >
> > > I'm trying to link ALSA playback devices and DRM connectors. In other
> > > words, I'd like to be able to know which ALSA device I should open to
> > > play audio on a given connector.
> > >
> > > Unfortunately, I haven't found a way to extract this information. I
> > > know /proc/asound/cardN/eld* expose the EDID-like data. However by
> > > looking at the ALSA API (also: aplay -l and -L) I can't find a way to
> > > figure out which PCM device maps to the ELD.
> > >
> > > Am I missing something?
> >
> > Is that actually fixed on all hardware? Or do we maybe have some
> > hardware with only one audio codec and multiple connectors?
> >
> > > If not, what would be the best way to expose this?
> > >
> > > - A symlink to the ALSA audio PCM device in
> > > /sys/class/drm/cardN-CONNECTOR?
> > > - A symlink to the DRM connector in /sys/class/sound/pcm*?
> >
> > If it's fixed than those two options sound sane to me.
> >
> > > - A DRM connector property?
> >
> > If it's configurable than that sounds like a good option to me.
> >
> > Anyway added our DC team, stuff like that is their construction site.
> >
> > Regards,
> > Christian.
> >
> > > - Somehow expose the connector name via the ALSA API?
> > > - Expose the connector EDID via ALSA?
> > > - Other ideas?
>
> I think on our MST hw you get a combination of CRTCs x CONNECTORs on
> the alsa side. I.e. for every pair of connector and crtc you get a
> separate alsa pin. This is because with mst, you could have up to
> num_crtcs streams on a single connector. Not sure how to model that.
I assume this means "up to num_crtcs streams an a physical connector".
With MST a physical connector can back more than one DRM connector.
> Bigger question: How do you want to make the cooperation happen?
> There's been some ideas floating about making the hdmi connection
> between drm and alsa somehow represented in the code, but nothing ever
> really happened. there's drm_audio_component.h, but that's just the
> interface, it doesn't really solve how to make the connection. Also
> only used by i915/hda.
To be completely honest I have no idea. That's why I sent this e-
mail. :P
Indeed, it seems that the interface isn't enough (get_eld and pin2port
are interesting though).
> > > Thanks!
> > >
> > > Simon Ser
> > > _______________________________________________
> > > dri-devel mailing list
> > > dri-devel@lists.freedesktop.org
> > > https://lists.freedesktop.org/mailman/listinfo/dri-devel
> >
> > _______________________________________________
> > dri-devel mailing list
> > dri-devel@lists.freedesktop.org
> > https://lists.freedesktop.org/mailman/listinfo/dri-devel
>
>
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2019-06-06 9:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-04 15:05 Linking ALSA playback devices and DRM connectors Ser, Simon
2019-06-04 15:15 ` Christian König
2019-06-04 15:24 ` Daniel Vetter
2019-06-04 16:25 ` Ville Syrjälä
2019-06-11 10:01 ` [alsa-devel] " Takashi Iwai
2019-06-06 9:17 ` Ser, Simon [this message]
2019-06-06 9:13 ` Ser, Simon
2019-06-06 9:20 ` Koenig, Christian
2019-06-07 17:02 ` Ville Syrjälä
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=6bafad8875cf21abdd3c0f2a093c8bd2625b33df.camel@intel.com \
--to=simon.ser@intel.com \
--cc=Nicholas.Kazlauskas@amd.com \
--cc=alsa-devel@alsa-project.org \
--cc=christian.koenig@amd.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=sunpeng.li@amd.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).