Hi, This series add a new entity operation which will aid capture drivers to map a port/endpoint in DT to a media graph pad.
This series is implemented support for the ongoing ADV748x work by Kieran Bingham. In his work he have a driver which registers more then one subdevice. So when a driver finds this subdevice it must be able to ask the subdevice itself which pad number correspond to the DT endpoint the driver used to bind subdevice in the first place. This is tested on Renesas H3 and M3-W together with the Renesas CSI-2 and VIN Gen3 driver (posted separately). It is based on top media-tree. * Changes since v2 - Renamed pad_from_fwnode to get_fwnode_pad as suggested by Sakari. - Return pad number instead of passing it as a pointer to both get_fwnode_pad() and media_entity_pad_from_fwnode(). - Document possible flags of the direction argument to media_entity_pad_from_fwnode(). - Use unsigned int instead of int for bitmask. - Fix numerous spelling mistakes, thanks Hans! - Rebased to latest media-tree. * Changes since v1 - Rebased work ontop of Sakaris fwnode branch and make use of the fwnode instead of the raw DT port/reg numbers. - Do not assume DT port is equal to pad number if the driver do not implement the lookup function. Instead search for the first pad with the correct direction and use that. Thanks Sakari for the suggestion! - Use ENXIO instead of EINVAL to signal lookup error. Niklas Söderlund (2): media: entity: Add get_fwnode_pad entity operation media: entity: Add media_entity_get_fwnode_pad() function drivers/media/media-entity.c | 35 +++++++++++++++++++++++++++++++++++ include/media/media-entity.h | 28 ++++++++++++++++++++++++++++ 2 files changed, 63 insertions(+) -- 2.13.1
