[PATCHv2 0/9] omapdrm: hdmi4: add CEC support
Tomi Valkeinen
tomi.valkeinen at ti.com
Fri Aug 11 10:57:18 UTC 2017
Hi Hans,
Texas Instruments Finland Oy, Porkkalankatu 22, 00180 Helsinki. Y-tunnus/Business ID: 0615521-4. Kotipaikka/Domicile: Helsinki
On 02/08/17 11:53, Hans Verkuil wrote:
> From: Hans Verkuil <hans.verkuil at cisco.com>
>
> This patch series adds CEC support for the omap4. It is based on
> the 4.13-rc2 kernel with this patch series applied:
>
> http://www.spinics.net/lists/dri-devel/msg143440.html
>
> It is virtually identical to the first patch series posted in
> April:
>
> http://www.spinics.net/lists/dri-devel/msg138950.html
>
> The only two changes are in the Kconfig due to CEC Kconfig
> changes in 4.13 (it now selects CEC_CORE instead of depending on
> CEC_CORE) and a final patch was added adding a lost_hotplug op
> since for proper CEC support I have to know when the hotplug
> signal goes away.
>
> Tested with my Pandaboard.
I'm doing some testing with this series on my panda. One issue I see is
that when I unload the display modules, I get:
[ 75.180206] platform 58006000.encoder: enabled after unload, idling
[ 75.187896] platform 58001000.dispc: enabled after unload, idling
[ 75.198242] platform 58000000.dss: enabled after unload, idling
So I think something is left enabled, most likely in the HDMI driver. I
haven't debugged this yet.
The first time I loaded the modules I also got "operation stopped when
reading edid", but I haven't seen that since. Possibly not related to
this series.
Are there some simple ways to test the CEC? My buildroot fs has
cec-compliance, cec-ctl and cec-follower commands. Are you familiar with
those? Can they be used?
Tomi
More information about the dri-devel
mailing list