From: "Niklas Söderlund" <niklas.soderlund@ragnatech.se>
To: Mauro Carvalho Chehab <mchehab@kernel.org>,
Sakari Ailus <sakari.ailus@linux.intel.com>,
linux-media@vger.kernel.org
Cc: "Kieran Bingham" <kieran.bingham@ideasonboard.com>,
linux-renesas-soc@vger.kernel.org,
"Laurent Pinchart" <laurent.pinchart@ideasonboard.com>,
"Niklas Söderlund" <niklas.soderlund+renesas@ragnatech.se>
Subject: [PATCH v2 0/2] media: entity: add operation to help map DT node to media pad
Date: Wed, 24 May 2017 02:09:05 +0200 [thread overview]
Message-ID: <20170524000907.13061-1-niklas.soderlund@ragnatech.se> (raw)
From: Niklas Söderlund <niklas.soderlund+renesas@ragnatech.se>
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 of Sakaris
pull request '[GIT PULL FOR v4.13] V4L2 fwnode support'.
* 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 pad_from_fwnode entity operation
media: entity: Add media_entity_pad_from_fwnode() function
drivers/media/media-entity.c | 39 +++++++++++++++++++++++++++++++++++++++
include/media/media-entity.h | 28 ++++++++++++++++++++++++++++
2 files changed, 67 insertions(+)
--
2.13.0
next reply other threads:[~2017-05-24 0:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-24 0:09 Niklas Söderlund [this message]
2017-05-24 0:09 ` [PATCH v2 1/2] media: entity: Add pad_from_fwnode entity operation Niklas Söderlund
2017-05-24 13:21 ` Sakari Ailus
2017-05-24 14:07 ` Niklas Söderlund
2017-05-26 21:52 ` Sakari Ailus
2017-05-24 0:09 ` [PATCH v2 2/2] media: entity: Add media_entity_pad_from_fwnode() function Niklas Söderlund
2017-05-24 13:27 ` Sakari Ailus
2017-05-24 14:09 ` Niklas Söderlund
2017-05-29 10:32 ` Hans Verkuil
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170524000907.13061-1-niklas.soderlund@ragnatech.se \
--to=niklas.soderlund@ragnatech.se \
--cc=kieran.bingham@ideasonboard.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=niklas.soderlund+renesas@ragnatech.se \
--cc=sakari.ailus@linux.intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).