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
On 10/06/15 21:51, Russell King - ARM Linux wrote:
> We at least need some kind of notification system from the video part
> to the other parts, so that we can sanely transmit connect/disconnect/
> edid updates to different parts of the system*not* that I'm suggesting
> that in the case of the
>> 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
On Wed, Oct 07, 2015 at 09:48:42AM +0200, Arnaud Pouliquen wrote:
> Should ALSA bypasses or not the DRM core/API to access to DRM HDMI
> connector?
You don't need direct access to the connector - and actually, having
direct access to the connector is potentially racy. So no.
> Concerning bridge
On 10/06/2015 04:33 PM, Jean-Francois Moine wrote:
> On Tue, 6 Oct 2015 11:23:03 +0200
> Arnaud Pouliquen 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
On Tue, Oct 06, 2015 at 05:46:02PM +0100, Mark Brown wrote:
> On Tue, Oct 06, 2015 at 06:44:34PM +0300, Jyri Sarha wrote:
> > On 10/06/15 12:23, Arnaud Pouliquen wrote:
>
> > >In a first step, before going deep in discussion on the approach, it
> > >should be interesting to have maintainers
On 10/06/15 12:23, Arnaud Pouliquen wrote:
> Hello Jyri,
>
> Thanks your feedback, my answers in line
>
>
> On 10/05/2015 03:27 PM, Jyri Sarha wrote:
>> On 10/01/15 19:50, Arnaud Pouliquen wrote:
>>>
>>> Version 2:
>>> This version integrates missing features upgraded to be aligned when
>>>
On Tue, Oct 06, 2015 at 06:44:34PM +0300, Jyri Sarha wrote:
> On 10/06/15 12:23, Arnaud Pouliquen wrote:
> >In a first step, before going deep in discussion on the approach, it
> >should be interesting to have maintainers feedback, to be sure that my
> >approach could make sense from DRM and ALSA
On Tue, 6 Oct 2015 11:23:03 +0200
Arnaud Pouliquen 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
Hello Jyri,
Thanks your feedback, my answers in line
On 10/05/2015 03:27 PM, Jyri Sarha wrote:
> On 10/01/15 19:50, Arnaud Pouliquen wrote:
>>
>> Version 2:
>> This version integrates missing features upgraded to be aligned when possible
>> with patch set:
>> [PATCH RFC v4 0/8] Implement
On 10/01/15 19:50, Arnaud Pouliquen wrote:
>
> Version 2:
> This version integrates missing features upgraded to be aligned when possible
> with patch set:
> [PATCH RFC v4 0/8] Implement generic ASoC HDMI codec and use it in tda998x
>
There are still some details I would like to change if we
Version 2:
This version integrates missing features upgraded to be aligned when possible
with patch set:
[PATCH RFC v4 0/8] Implement generic ASoC HDMI codec and use it in tda998x
It does not support the abort callback, the mute and syclk ops.
This could be added in V3 or separate patch if
12 matches
Mail list logo
