linux-media.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Philipp Zabel <p.zabel@pengutronix.de>
To: Steve Longerbeam <slongerbeam@gmail.com>,
	Yong Zhi <yong.zhi@intel.com>,
	Sakari Ailus <sakari.ailus@linux.intel.com>,
	Mauro Carvalho Chehab <mchehab@kernel.org>,
	Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
	niklas.soderlund@ragnatech.se, Sebastian Reichel <sre@kernel.org>,
	Hans Verkuil <hans.verkuil@cisco.com>
Cc: linux-media@vger.kernel.org,
	Steve Longerbeam <steve_longerbeam@mentor.com>
Subject: Re: [PATCH v4 00/14] media: imx: Switch to subdev notifiers
Date: Mon, 14 May 2018 11:37:06 +0200	[thread overview]
Message-ID: <1526290626.4936.6.camel@pengutronix.de> (raw)
In-Reply-To: <1525906023-827-1-git-send-email-steve_longerbeam@mentor.com>

Hi Steve,

thank you for the update.

On Wed, 2018-05-09 at 15:46 -0700, Steve Longerbeam wrote:
> This patchset converts the imx-media driver and its dependent
> subdevs to use subdev notifiers.
> 
> There are a couple shortcomings in v4l2-core that prevented
> subdev notifiers from working correctly in imx-media:
> 
> 1. v4l2_async_notifier_fwnode_parse_endpoint() treats a fwnode
>    endpoint that is not connected to a remote device as an error.
>    But in the case of the video-mux subdev, this is not an error,
>    it is OK if some of the mux inputs have no connection. Also,
>    Documentation/devicetree/bindings/media/video-interfaces.txt explicitly
>    states that the 'remote-endpoint' property is optional. So the first
>    patch is a small modification to ignore empty endpoints in
>    v4l2_async_notifier_fwnode_parse_endpoint() and allow
>    __v4l2_async_notifier_parse_fwnode_endpoints() to continue to
>    parse the remaining port endpoints of the device.
> 
> 2. In the imx-media graph, multiple subdevs will encounter the same
>    upstream subdev (such as the imx6-mipi-csi2 receiver), and so
>    v4l2_async_notifier_parse_fwnode_endpoints() will add imx6-mipi-csi2
>    multiple times. This is treated as an error by
>    v4l2_async_notifier_register() later.
> 
>    To get around this problem, add an v4l2_async_notifier_add_subdev()
>    which first verifies the provided asd does not already exist in the
>    given notifier asd list or in other registered notifiers. If the asd
>    exists, the function returns -EEXIST and it's up to the caller to
>    decide if that is an error (in imx-media case it is never an error).
> 
>    Patches 2-5 deal with adding that support.
> 
> 3. Patch 6 adds v4l2_async_register_fwnode_subdev(), which is a
>    convenience function for parsing a subdev's fwnode port endpoints
>    for connected remote subdevs, registering a subdev notifier, and
>    then registering the sub-device itself.
> 
> The remaining patches update the subdev drivers to register a
> subdev notifier with endpoint parsing, and the changes to imx-media
> to support that.
> 
> Signed-off-by: Steve Longerbeam <steve_longerbeam@mentor.com>
> Acked-by: Philipp Zabel <p.zabel@pengutronix.de>

Patches 07-14 (video-mux and the imx patches) are
Reviewed-by: Philipp Zabel <p.zabel@pengutronix.de>

The series is
Tested-by: Philipp Zabel <p.zabel@pengutronix.de>
on i.MX6 with Toshiba TC358743 connected via MIPI CSI-2.

regards
Philipp

      parent reply	other threads:[~2018-05-14  9:37 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-09 22:46 [PATCH v4 00/14] media: imx: Switch to subdev notifiers Steve Longerbeam
2018-05-09 22:46 ` [PATCH v4 01/14] media: v4l2-fwnode: ignore endpoints that have no remote port parent Steve Longerbeam
2018-05-09 22:46 ` [PATCH v4 02/14] media: v4l2: async: Allow searching for asd of any type Steve Longerbeam
2018-05-09 22:46 ` [PATCH v4 03/14] media: v4l2: async: Add v4l2_async_notifier_add_subdev Steve Longerbeam
2018-05-09 22:46 ` [PATCH v4 04/14] media: v4l2: async: Add convenience functions to allocate and add asd's Steve Longerbeam
2018-05-09 22:46 ` [PATCH v4 05/14] media: v4l2-fwnode: Switch to v4l2_async_notifier_add_subdev Steve Longerbeam
2018-05-09 22:46 ` [PATCH v4 06/14] media: v4l2-fwnode: Add a convenience function for registering subdevs with notifiers Steve Longerbeam
2018-05-09 22:46 ` [PATCH v4 07/14] media: platform: video-mux: Register a subdev notifier Steve Longerbeam
2018-05-09 22:46 ` [PATCH v4 08/14] media: imx: csi: " Steve Longerbeam
2018-05-09 22:46 ` [PATCH v4 09/14] media: imx: mipi csi-2: " Steve Longerbeam
2018-05-09 22:46 ` [PATCH v4 10/14] media: staging/imx: of: Remove recursive graph walk Steve Longerbeam
2018-05-09 22:47 ` [PATCH v4 11/14] media: staging/imx: Loop through all registered subdevs for media links Steve Longerbeam
2018-05-09 22:47 ` [PATCH v4 12/14] media: staging/imx: Rename root notifier Steve Longerbeam
2018-05-09 22:47 ` [PATCH v4 13/14] media: staging/imx: Switch to v4l2_async_notifier_add_*_subdev Steve Longerbeam
2018-05-09 22:47 ` [PATCH v4 14/14] media: staging/imx: TODO: Remove one assumption about OF graph parsing Steve Longerbeam
2018-05-14  9:37 ` Philipp Zabel [this message]

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=1526290626.4936.6.camel@pengutronix.de \
    --to=p.zabel@pengutronix.de \
    --cc=hans.verkuil@cisco.com \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --cc=niklas.soderlund@ragnatech.se \
    --cc=sakari.ailus@linux.intel.com \
    --cc=slongerbeam@gmail.com \
    --cc=sre@kernel.org \
    --cc=steve_longerbeam@mentor.com \
    --cc=yong.zhi@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).