From: Arnaud Pouliquen <arnaud.pouliquen@st.com>
To: Jean-Francois Moine <moinejf@free.fr>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"linux@arm.linux.org.uk" <linux@arm.linux.org.uk>,
Benjamin Gaignard <benjamin.gaignard@linaro.org>,
David Airlie <airlied@linux.ie>,
"broonie@kernel.org" <broonie@kernel.org>,
"lgirdwood@gmail.com" <lgirdwood@gmail.com>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"peter.ujfalusi@ti.com" <peter.ujfalusi@ti.com>,
Takashi Iwai <tiwai@suse.de>,
"tony@atomide.com" <tony@atomide.com>,
"tomi.valkeinen@ti.com" <tomi.valkeinen@ti.com>,
Jyri Sarha <jsarha@ti.com>,
"bcousson@baylibre.com" <bcousson@baylibre.com>
Subject: Re: [PATCH RFC V2 0/5] another generic audio hdmi codec proposal
Date: Wed, 7 Oct 2015 09:48:42 +0200 [thread overview]
Message-ID: <5614CE5A.1080406@st.com> (raw)
In-Reply-To: <20151006163311.03067bb5@OPI2>
On 10/06/2015 04:33 PM, Jean-Francois Moine wrote:
> On Tue, 6 Oct 2015 11:23:03 +0200
> Arnaud Pouliquen <arnaud.pouliquen@st.com> wrote:
> [snip]
>> As API is defined in DRM, it seems more logical to match it with the one
>> defined for video. From my windows, i didn't see any blocking point to
>> connect codec callback with this API.
>> But anyway, this API is not freezed, it could be improved with your help.
>
> Arnaud, your implementation seems more heavy than Jyri's, and I don't
> feel the DRM bridge.
>
> For HDMI, the exchanges between DRM and ALSA are only:
> - DRM -> ALSA
> - device connection with the audio constraints
> - device disconnection
> - ALSA -> DRM
> - start audio with the chosen audio parameters
> - stop audio
>
> and, in the system, the HDMI devices are seen as DRM connectors (video
> view) and as ASoC CODECs (audio view).
>
> We just need a link between these entities.
> I don't think that the bridge offers this.
Not so heavy...
In fact another way to differentiate the twice approaches could be to
answer to this question:
Should ALSA bypasses or not the DRM core/API to access to DRM HDMI
connector?
Concerning bridge usage, I tried to found a link to address DRM driver
trough DRM API. Bridge seemed a good candidate. Perhaps the DRM encoder
API could be an other option to study...
Ken ar wech all/ best Regards
Arnaud
next prev parent reply other threads:[~2015-10-07 7:48 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-01 16:50 [PATCH RFC V2 0/5] another generic audio hdmi codec proposal Arnaud Pouliquen
2015-10-01 16:50 ` [PATCH RFC V2 1/5] video: hdmi: add helper function for N and CTS Arnaud Pouliquen
2015-10-01 16:50 ` Arnaud Pouliquen
2015-10-01 16:50 ` [PATCH RFC V2 2/5] drm: add helper functions to add audio capabilities for bridge Arnaud Pouliquen
2015-10-01 16:50 ` [PATCH RFC V2 3/5] ASoC: codec: hdmi drm codec driver Arnaud Pouliquen
2015-10-01 16:50 ` [PATCH RFC V2 4/5] drm: sti: connect audio driver Arnaud Pouliquen
2015-10-01 16:50 ` [PATCH RFC V2 5/5] DT: sti: add audio HDMI dai link in audio card Arnaud Pouliquen
2015-10-05 13:27 ` [PATCH RFC V2 0/5] another generic audio hdmi codec proposal Jyri Sarha
2015-10-06 9:23 ` Arnaud Pouliquen
2015-10-06 14:33 ` [alsa-devel] " Jean-Francois Moine
2015-10-07 7:48 ` Arnaud Pouliquen [this message]
2015-10-07 9:05 ` Russell King - ARM Linux
2015-10-06 15:44 ` Jyri Sarha
2015-10-06 16:46 ` Mark Brown
2015-10-06 18:51 ` [alsa-devel] " Russell King - ARM Linux
2015-10-07 7:36 ` Jyri Sarha
2015-10-07 8:19 ` Arnaud Pouliquen
2015-10-07 10:21 ` Lars-Peter Clausen
2015-10-07 10:21 ` [alsa-devel] " Lars-Peter Clausen
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=5614CE5A.1080406@st.com \
--to=arnaud.pouliquen@st.com \
--cc=airlied@linux.ie \
--cc=alsa-devel@alsa-project.org \
--cc=bcousson@baylibre.com \
--cc=benjamin.gaignard@linaro.org \
--cc=broonie@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=jsarha@ti.com \
--cc=lgirdwood@gmail.com \
--cc=linux@arm.linux.org.uk \
--cc=moinejf@free.fr \
--cc=peter.ujfalusi@ti.com \
--cc=tiwai@suse.de \
--cc=tomi.valkeinen@ti.com \
--cc=tony@atomide.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.