Hello,
I am looking forward to understand media-ctl and I understand that the commands reported in the tutorial are specific for the CSI camera interface OV5645…
In my case the C270 USB camera is /dev/media1
so:
# media-ctl -d /dev/media1 -p
Media controller API version 0.1.0
Media device information
------------------------
driver uvcvideo
model UVC Camera (046d:0825)
serial 2FB8A120
bus info 1.2
hw revision 0x12
driver version 4.9.39
Device topology
- entity 1: UVC Camera (046d:0825) (1 pad, 1 link)
type Node subtype V4L flags 1
device node name /dev/video0
pad0: Sink
<- "Extension 4":1 [ENABLED,IMMUTABLE]
- entity 5: Extension 4 (2 pads, 4 links)
type V4L2 subdev subtype Unknown flags 0
pad0: Sink
<- "Processing 2":1 [ENABLED,IMMUTABLE]
pad1: Source
-> "UVC Camera (046d:0825)":0 [ENABLED,IMMUTABLE]
-> "Extension 6":0 [ENABLED,IMMUTABLE]
-> "Extension 7":0 [ENABLED,IMMUTABLE]
- entity 8: Extension 6 (2 pads, 1 link)
type V4L2 subdev subtype Unknown flags 0
pad0: Sink
<- "Extension 4":1 [ENABLED,IMMUTABLE]
pad1: Source
- entity 11: Extension 7 (2 pads, 1 link)
type V4L2 subdev subtype Unknown flags 0
pad0: Sink
<- "Extension 4":1 [ENABLED,IMMUTABLE]
pad1: Source
- entity 14: Processing 2 (2 pads, 3 links)
type V4L2 subdev subtype Unknown flags 0
pad0: Sink
<- "Camera 1":0 [ENABLED,IMMUTABLE]
pad1: Source
-> "Extension 4":0 [ENABLED,IMMUTABLE]
-> "Extension 3":0 [ENABLED,IMMUTABLE]
- entity 17: Extension 3 (2 pads, 1 link)
type V4L2 subdev subtype Unknown flags 0
pad0: Sink
<- "Processing 2":1 [ENABLED,IMMUTABLE]
pad1: Source
- entity 20: Camera 1 (1 pad, 1 link)
type V4L2 subdev subtype Unknown flags 0
pad0: Source
-> "Processing 2":0 [ENABLED,IMMUTABLE]
From what I read on the web, now I have to build my own media-ctl
command based on the --print-topology
output. Could you suggest where to find the official media-ctl
documentation ?
However, at the moment I have a further doubt: how the APQ8016 H264 hardware encoder is being used/invoked from media-ctl and gstreamer commands ?
Regards,
Simon