* Re: [alsa-devel] [PATCH RFC V2 0/5] another generic audio hdmi codec proposal
[not found] ` <5614D58F.9010102@st.com>
@ 2015-10-07 10:21 ` Lars-Peter Clausen
0 siblings, 0 replies; only message in thread
From: Lars-Peter Clausen @ 2015-10-07 10:21 UTC (permalink / raw)
To: Arnaud Pouliquen, Jyri Sarha, alsa-devel@alsa-project.org,
dri-devel@lists.freedesktop.org
Cc: moinejf@free.fr, linux@arm.linux.org.uk, Benjamin Gaignard,
David Airlie, broonie@kernel.org, lgirdwood@gmail.com,
peter.ujfalusi@ti.com, Takashi Iwai, tony@atomide.com,
tomi.valkeinen@ti.com, bcousson@baylibre.com,
linux-media@vger.kernel.org, Hans Verkuil
Added Hans, who's working a lot on the HDMI transmitter drivers (including
audio support) as well as the media list to Cc.
On 10/07/2015 10:19 AM, Arnaud Pouliquen wrote:
>
>
>>> My approach is the reverse: DRM driver does not need to know anything
>>> about audio side. As ALSA is the client of DRM, seems more logical from
>>> my point of view ...
>>> Now if a generic solution must be found for all video drivers, sure,
>>> your solution is more flexible.
>>> But if i well understood fbdev drivers are no more accepted for upstream
>>> (please correct me if I'm wrong).
>>> So i don't know we have to keep fbdev in picture...
>>>
>>
>> I am not promoting fbdev support. I am merely asking if we want to force
>> all HDMI drivers to implement a drm_bridge if they want to support audio.
>>
> Yes this is a good point... My implementation is based on hypothesis that
> HDMI drivers are now upstreamed as DRM drivers.
The other place where you can find HDMI support is in V4L2, both receive as
well as transmit. And while the hope for fbdev is that it will be phased out
V4L2 will stay around for a while. And we probably want to have a common API
that can take care of both DRM and V4L so we do not need two sets of helper
functions for things like EDID parsing etc.
- Lars
^ permalink raw reply [flat|nested] only message in thread