Re: HDMI codec, way forward?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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@xxxxxxxxxxxxxxxxxxxxxx>

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.)

-- 
FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up
according to speedtest.net.
_______________________________________________
dri-devel mailing list
dri-devel@xxxxxxxxxxxxxxxxxxxxx
http://lists.freedesktop.org/mailman/listinfo/dri-devel




[Index of Archives]     [Linux DRI Users]     [Linux Intel Graphics]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [XFree86]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [XFree86]
  Powered by Linux