From: Takashi Iwai <tiwai@suse.de>
To: Vinod Koul <vinod.koul@intel.com>
Cc: patches.audio@intel.com, alsa-devel@alsa-project.org,
broonie@kernel.org,
"Subhransu S. Prusty" <subhransu.s.prusty@intel.com>,
lgirdwood@gmail.com
Subject: Re: [PATCH v3 14/15] ASoC: hdac_hdmi: Add jack reporting for user space
Date: Tue, 08 Dec 2015 08:52:10 +0100 [thread overview]
Message-ID: <s5hio491iol.wl-tiwai@suse.de> (raw)
In-Reply-To: <20151208074216.GO1854@localhost>
On Tue, 08 Dec 2015 08:42:16 +0100,
Vinod Koul wrote:
>
> On Tue, Dec 08, 2015 at 07:38:46AM +0100, Takashi Iwai wrote:
> > On Tue, 08 Dec 2015 07:31:36 +0100,
> > Vinod Koul wrote:
> > >
> > > On Mon, Dec 07, 2015 at 05:18:06PM +0100, Takashi Iwai wrote:
> > > > On Mon, 07 Dec 2015 22:24:28 +0100,
> > > > > + sprintf(jack_name, "HDMI/DP, Pin=%d Jack", pin->nid);
> > > >
> > > > Such a name makes sense only to be compatible for PA, and then this
> > > > string isn't compatible. Note that it's not about pin but for PCM
> > > > stream. You may wonder why it matters -- see the whole discussion on
> > > > MST support.
> > >
> > > So in our case we have added only one PCM Backend in DSP. In codec we have
> > > one DAI supported, thus creating a DAIlink
> > >
> > > The Codec DAI is mapped to a stream which we fix to a CVT. Future we
> > > will add two more streams which are mapped to other two CVTs.
> > >
> > > We use MUX controls to allow user to specfiy how CVT and PINs are connected
> > > togther, this way we can route stream to any pin.
> > >
> > > Extending this concept, behind a pin for MST there may be different 'ports',
> > > right? Shouldn't that be another mux configuration :) So we can treat three
> > > streams coming to codec to be routed to any pin and then any port. Since we
> > > have only 3 CVTs we will have only 3 streams...
> >
> > You can't do that easily. Remember that you may connect up to 64
> > different devices at the same time per pin, and this can switch on the
> > fly. How would you implement a MUX?
>
> somehow I was under impression that it is 3.. Btw even if 64 devices can be
> connected how many can we render to?
That's what I meant below. Although you can may connect quite a lot
of devices, the number of devices that can be actually output at the
same time is limited, actually equal with the number of converters.
> > Though, the max number of converters is limited, thus what you can
> > actually use is defined by this constraint. Due to this, we'll likely
> > manage MST for the legacy HDA by assigning MST devs dynamically to
> > pins in a certain procedure to make things compatible.
>
> but how many MST devs are you going to create?
This is exactly the point: for the legacy HDA, instead of creating the
entry for each MST devices, they are assigned dynamically to PCM at
activation. So the number of devices exposed to user-space is
limited -- or better to say, user-space won't notice the difference.
> > > Back on present :), what do you recommend for us for jack name.
> >
> > Depends on your purpose. If you want to keep it compatible, then use
> > the compatible string.
>
> Since compatible string would mean specfying PCM, which we don;t know and is
> per machine driver dailink defination, we would go ahead with logical
> "HDMI/DP, Pin=%d Jack" names.
But then it makes little sense. Multiple MST devices can be on the
same pin.
Takashi
next prev parent reply other threads:[~2015-12-08 7:52 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-07 21:17 [PATCH v3 00/15] ASoC: hdac_hdmi: Add DP & notification support Subhransu S. Prusty
2015-12-07 20:12 ` Mark Brown
2015-12-08 11:24 ` Subhransu S. Prusty
2015-12-07 21:24 ` [PATCH v3 01/15] ASoC: hdac_hdmi: Fix to check num nodes correctly Subhransu S. Prusty
2015-12-07 21:24 ` [PATCH v3 02/15] ASoC: hdac_hdmi: Fix to warn instead of err for no connected nids Subhransu S. Prusty
2015-12-07 21:24 ` [PATCH v3 03/15] ASoC: hdac_hdmi: Use list to add pins and converters Subhransu S. Prusty
2016-01-08 13:44 ` Applied "ASoC: hdac_hdmi: Use list to add pins and converters" to the asoc tree Mark Brown
2015-12-07 21:24 ` [PATCH v3 04/15] ASoC: hdac_hdmi: Add hotplug notification and read eld Subhransu S. Prusty
2015-12-07 21:24 ` [PATCH v3 05/15] ASoC: hdac_hdmi: Apply constraints based on ELD Subhransu S. Prusty
2015-12-07 21:24 ` [PATCH v3 06/15] ASoC: hdac_hdmi: Enable DP1.2 and all converters/pins Subhransu S. Prusty
2015-12-07 21:24 ` [PATCH v3 07/15] ASoC: hdac_hdmi: create dais based on number of streams Subhransu S. Prusty
2015-12-07 16:11 ` Takashi Iwai
2015-12-07 21:24 ` [PATCH v3 08/15] ASoC: hdac_hdmi: Create widget/route based on nodes enumerated Subhransu S. Prusty
2015-12-07 16:14 ` Takashi Iwai
2015-12-08 11:28 ` Subhransu S. Prusty
2015-12-07 21:24 ` [PATCH v3 09/15] ASoC: hdac_hdmi: Assign pin for stream based on dapm connection Subhransu S. Prusty
2015-12-07 21:24 ` [PATCH v3 10/15] drm/edid: Add API to help find connection type Subhransu S. Prusty
2015-12-08 14:01 ` Jani Nikula
2015-12-07 21:24 ` [PATCH v3 11/15] ASoC: hdac_hdmi: Add infoframe support for dp audio Subhransu S. Prusty
2015-12-07 21:24 ` [PATCH v3 12/15] ASoC: hdac_hdmi: Add codec suspend/resume handler Subhransu S. Prusty
2015-12-07 21:24 ` [PATCH v3 13/15] ASoC: hdac_hdmi: Fix to keep display active while enumerating codec Subhransu S. Prusty
2015-12-07 21:24 ` [PATCH v3 14/15] ASoC: hdac_hdmi: Add jack reporting for user space Subhransu S. Prusty
2015-12-07 16:18 ` Takashi Iwai
2015-12-08 6:31 ` Vinod Koul
2015-12-08 6:38 ` Takashi Iwai
2015-12-08 7:42 ` Vinod Koul
2015-12-08 7:52 ` Takashi Iwai [this message]
2015-12-08 8:38 ` Vinod Koul
2015-12-08 8:42 ` Takashi Iwai
2015-12-08 10:20 ` Vinod Koul
2015-12-08 10:28 ` Takashi Iwai
2015-12-08 10:42 ` Vinod Koul
2015-12-08 10:51 ` Takashi Iwai
2015-12-08 10:59 ` Takashi Iwai
2015-12-09 5:44 ` Vinod Koul
2015-12-09 8:03 ` Subhransu S. Prusty
2015-12-09 8:13 ` Takashi Iwai
2015-12-09 11:14 ` Subhransu S. Prusty
2015-12-09 11:37 ` Takashi Iwai
2015-12-07 21:24 ` [PATCH v3 15/15] ASoC: hdac_hdmi: Fix to enable device configuration in hw_params 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=s5hio491iol.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.