Re: HDMI codec, way forward?

[Vinod Koul <vinod.koul@intel.com>]

On Sun, Oct 18, 2015 at 04:20:48PM +0100, Russell King - ARM Linux wrote:
> On Sun, Oct 18, 2015 at 08:38:34PM +0530, Vinod Koul wrote:
> > On Fri, Oct 16, 2015 at 02:37:17PM +0100, Russell King - ARM Linux wrote:
> > > I've sent one proposal which uses a notifier to inform audio and CEC
> > > drivers about state changes in the HDMI video side, and had precisely
> > > zero replies to it - people seemed to prefer discussing stuff rather
> > > than reviewing code and coming up with actual solutions.
> > 
> > Do you mind sending me a pointer to this series, I would like to read this
> > up
> 
> It isn't a series.  It's a prototype patch that I posted in one of the
> previous threads earlier this month:
> 
> Date: Tue, 6 Oct 2015 19:51:57 +0100
> Subject: Re: [alsa-devel] [PATCH RFC V2 0/5] another generic audio hdmi codec
>  proposal
> Message-ID: <20151006185157.GT21513@n2100.arm.linux.org.uk>
> 
> As I've said there, audio is not the only issue here, CEC also needs to
> have access to much the same information that audio needs.
> 
> CEC needs to know two things: when the HDMI sink is disconnected, and
> when the HDMI sink's EDID is available (specifically, CEC needs to know
> the HDMI physical address for itself, which is passed as a number via
> the EDID HDMI vendor block.)

Right but can I ask why you didn't try making video as component and then
CEC, audio and others receive the notification over this. I don't know if
there are any limitations to this since you wrote component bits you are the
best person to comment...

-- 
~Vinod