On Mon, Sep 07, 2015 at 03:44:36PM +0200, Hans Verkuil wrote: > From: Hans Verkuil <hans.verkuil at cisco.com> > > The added HDMI CEC framework provides a generic kernel interface for > HDMI CEC devices. > > Signed-off-by: Hans Verkuil <hansverk at cisco.com> > [k.debski at samsung.com: Merged CEC Updates commit by Hans Verkuil] > [k.debski at samsung.com: Merged Update author commit by Hans Verkuil] > [k.debski at samsung.com: change kthread handling when setting logical > address] > [k.debski at samsung.com: code cleanup and fixes] > [k.debski at samsung.com: add missing CEC commands to match spec] > [k.debski at samsung.com: add RC framework support] > [k.debski at samsung.com: move and edit documentation] > [k.debski at samsung.com: add vendor id reporting] > [k.debski at samsung.com: add possibility to clear assigned logical > addresses] > [k.debski at samsung.com: documentation fixes, clenaup and expansion] > [k.debski at samsung.com: reorder of API structs and add reserved fields] > [k.debski at samsung.com: fix handling of events and fix 32/64bit timespec > problem] > [k.debski at samsung.com: add cec.h to include/uapi/linux/Kbuild] > [k.debski at samsung.com: add sequence number handling] > [k.debski at samsung.com: add passthrough mode] > [k.debski at samsung.com: fix CEC defines, add missing CEC 2.0 commands] > minor additions] > Signed-off-by: Kamil Debski <kamil at wypas.org> > Signed-off-by: Hans Verkuil <hans.verkuil at cisco.com>
I don't see much in the way of support for source devices in this: how do we handle hotplug of the sink, and how to do we configure the physical address? Surely you aren't proposing that drivers should write directly to adap->phys_addr without calling some notification function that the physical address has changed? Please can you give some guidance on how a HDMI source bridge driver should deal with these issues. Thanks. -- FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up according to speedtest.net.
