Testing HDMI on E3

[jacopo mondi <jacopo@jmondi.org>]

[-- Attachment #1: Type: text/plain, Size: 1473 bytes --]

Hi Laurent
   +Niklas in CC for support
   +renesas-socs to document the procedure

In order to test HDMI capture on D3 and Salvator-x boards, I have
always used Niklas' great vin-tests suite
git://git.ragnatech.se/vin-tests

And I suggest to do the same for E3.

* Add E3 support to vin-tests/boards.sh
  E3 has a video input pipeline similar to Salvator-X, and HDMI input
  connected to an adv7482, connected to a CSI-2 port, then to VIN.

  I cannot tell the exact entity names, but it is easy enough for you
  to find them out.

  I think you only need to tweak vin-tests/boards.sh to add Ebisu
  board there (look at my series doing that for D3, for E3 it's even
  simpler). Once the board is recognized, you can use other scripts.

* Set EDID on the HDMI port
  #vin-tests/set-edid
  You need to cross-compile vin-tests/src/edid/ in advance

  If this succeeds, the board is recognized.

* Capture with yavta
  Run
  #vin-tests/yavta-hdmi $VIN_INSTANCE

  The script configure links and set formats on all entities along the
  pipeline. At this point, I think the better thing to do is to try,
  see where it fails and adjust the entity names as required. Again,
  being this a 'standard' Gen3 capture pipeline, it should be easy
  enough.

- Before all that, I hope my Ebisu support series creates a proper media
  graph with all entities in place. No need to tell you, but check
  with media-ctl if everything looks correct for the E3 board.

Hope this helps.
   j

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]