On 10/08/17 11:08, Archit Taneja wrote: > > > On 08/10/2017 02:26 PM, Hans Verkuil wrote: >> On 10/08/17 10:49, Archit Taneja wrote: >>> Hi Hans, >>> >>> On 07/30/2017 06:37 PM, Hans Verkuil wrote: >>>> From: Hans Verkuil <hans.verkuil@xxxxxxxxx> >>>> >>>> This patch series adds CEC support to the drm adv7511/adv7533 drivers. >>>> >>>> I have tested this with the Qualcomm Dragonboard C410 (adv7533 based) >>>> and the Renesas R-Car Koelsch board (adv7511 based). >>>> >>>> Note: the Dragonboard needs this patch: >>>> >>>> https://patchwork.kernel.org/patch/9824773/ >>>> >>>> Archit, can you confirm that this patch will go to kernel 4.14? >>>> >>>> And the Koelsch board needs this 4.13 fix: >>>> >>>> https://patchwork.kernel.org/patch/9836865/ >>>> >>>> I only have the Koelsch board to test with, but it looks like other >>>> R-Car boards use the same adv7511. It would be nice if someone can >>>> add CEC support to the other R-Car boards as well. The main thing >>>> to check is if they all use the same 12 MHz fixed CEC clock source. >>>> >>>> Anyone who wants to test this will need the CEC utilities that >>>> are part of the v4l-utils git repository: >>>> >>>> git clone git://linuxtv.org/v4l-utils.git >>>> cd v4l-utils >>>> ./bootstrap.sh >>>> ./configure >>>> make >>>> sudo make install >>>> >>>> Now configure the CEC adapter as a Playback device: >>>> >>>> cec-ctl --playback >>>> >>>> Discover other CEC devices: >>>> >>>> cec-ctl -S >>> >>> I tried the instructions, and I get the following output. I don't think I have >>> any CEC device connected, though. Is this the expected behaviour? >>> >>> #cec-ctl -S >>> Driver Info: >>> Driver Name : adv7511 >>> Adapter Name : 3-0039 >>> Capabilities : 0x0000000e >>> Logical Addresses >>> Transmit >>> Passthrough >>> Driver version : 4.13.0 >>> Available Logical Addresses: 3 >>> Physical Address : 1.0.0.0 >>> Logical Address Mask : 0x0000 >>> CEC Version : 2.0 >>> Logical Addresses : 0 >>> >>> #cec-ctl --playback >>> [ 1038.761545] cec-3-0039: cec_thread_func: message 44 timed out! >> >> This isn't right. You shouldn't see this. It never receives an interrupt >> when the transmit has finished, which causes these time outs. >> >> What are you testing this on? The Dragonboard c410? > > Yes. On top of which kernel tree are these patches applied? I can try and reproduce it. Regards, Hans
