Hi Mark, On 13/11/14 00:23, Mark Brown wrote: > On Wed, Nov 12, 2014 at 04:40:51PM +0200, Jyri Sarha wrote: > >> It would make the most sense to get these in trough fbdev tree. So it >> would be nice to get acked-bys (if the patches are Ok) for ASoC side >> changes from appropriate maintainers. > > So, this is a very large series which gets reposted every so often to no > apparent interest from the video side, there's been no response at all Sorry for the lack of communication. We've been discussing this series on irc. It's been mostly about how to manage the device/driver split between drivers/video/ and sound/ sides. > that I can remember and even the earlier bits of the series before it > starts touching audio don't seem to be getting merged. What's going on > here? The series is all audio in terms of functionality. The first few patches could probably be merged independently, but I've wanted this whole OMAP HDMI audio rewrite to be in one series. I'll start testing this latest series, and I hope we can merge it for the next merge window so that we'll finally get the OMAP HDMI audio working. I don't have much knowledge of the asoc architecture, so I probably can't comment much on the sound/ side design. For me the most important things are that 1) it works 2) I can easily unload/load the modules (which was broken in some of the earlier versions). As a more general discussion item, I'm still wondering why it feels like we (OMAP) are doing something totally new here. I'd imagine that almost every device with HDMI would need both video and audio side support, and those sides need to work together. And the audio side would need to get notified of things like cable disconnect (i.e. the video stream is stopped -> audio must be stopped also). But if I've understood right, there was no similar existing code to be found. Tomi
Attachment:
signature.asc
Description: OpenPGP digital signature
