All of lore.kernel.org
 help / color / mirror / Atom feed
From: Helen Koike <helen.koike@collabora.com>
To: Sakari Ailus <sakari.ailus@linux.intel.com>, linux-media@vger.kernel.org
Cc: Hans Verkuil <hverkuil@xs4all.nl>,
	kernel@collabora.com,
	Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
	Kieran Bingham <kieran.bingham+renesas@ideasonboard.com>,
	Jacopo Mondi <jacopo@jmondi.org>,
	niklas.soderlund+renesas@ragnatech.se,
	Dafna Hirschfeld <dafna.hirschfeld@collabora.com>,
	Hugues Fruchet <hugues.fruchet@st.com>,
	Nicolas Ferre <nicolas.ferre@microchip.com>,
	Yong Zhi <yong.zhi@intel.com>,
	Sylwester Nawrocki <s.nawrocki@samsung.com>,
	Maxime Ripard <mripard@kernel.org>,
	Robert Foss <robert.foss@linaro.org>,
	Philipp Zabel <p.zabel@pengutronix.de>,
	Ezequiel Garcia <ezequiel@collabora.com>
Subject: Re: [PATCH v3 05/14] media: st-mipid02: Use v4l2_async_notifier_add_fwnode_remote_subdev
Date: Mon, 25 Jan 2021 14:22:29 -0300	[thread overview]
Message-ID: <2e9d2224-fd75-aa20-ff3f-fa1e06a75231@collabora.com> (raw)
In-Reply-To: <20210125132230.6600-20-sakari.ailus@linux.intel.com>



On 1/25/21 10:22 AM, Sakari Ailus wrote:
> From: Ezequiel Garcia <ezequiel@collabora.com>
> 
> The use of v4l2_async_notifier_add_subdev will be discouraged.
> Drivers are instead encouraged to use a helper such as
> v4l2_async_notifier_add_fwnode_remote_subdev.
> 
> This fixes a misuse of the API, as v4l2_async_notifier_add_subdev
> should get a kmalloc'ed struct v4l2_async_subdev,
> removing some boilerplate code while at it.
> 
> Use the appropriate helper v4l2_async_notifier_add_fwnode_remote_subdev,
> which handles the needed setup, instead of open-coding it.
> 
> Signed-off-by: Ezequiel Garcia <ezequiel@collabora.com>
> Reviewed-by: Jacopo Mondi <jacopo+renesas@jmondi.org>
> Signed-off-by: Sakari Ailus <sakari.ailus@linux.intel.com>

Reviewed-by: Helen Koike <helen.koike@collabora.com>

> ---
>  drivers/media/i2c/st-mipid02.c | 19 +++++++++----------
>  1 file changed, 9 insertions(+), 10 deletions(-)
> 
> diff --git a/drivers/media/i2c/st-mipid02.c b/drivers/media/i2c/st-mipid02.c
> index 003ba22334cd..42549b3a62a0 100644
> --- a/drivers/media/i2c/st-mipid02.c
> +++ b/drivers/media/i2c/st-mipid02.c
> @@ -92,7 +92,6 @@ struct mipid02_dev {
>  	u64 link_frequency;
>  	struct v4l2_fwnode_endpoint tx;
>  	/* remote source */
> -	struct v4l2_async_subdev asd;
>  	struct v4l2_async_notifier notifier;
>  	struct v4l2_subdev *s_subdev;
>  	/* registers */
> @@ -844,6 +843,7 @@ static int mipid02_parse_rx_ep(struct mipid02_dev *bridge)
>  {
>  	struct v4l2_fwnode_endpoint ep = { .bus_type = V4L2_MBUS_CSI2_DPHY };
>  	struct i2c_client *client = bridge->i2c_client;
> +	struct v4l2_async_subdev *asd;
>  	struct device_node *ep_node;
>  	int ret;
>  
> @@ -875,18 +875,17 @@ static int mipid02_parse_rx_ep(struct mipid02_dev *bridge)
>  	bridge->rx = ep;
>  
>  	/* register async notifier so we get noticed when sensor is connected */
> -	bridge->asd.match.fwnode =
> -		fwnode_graph_get_remote_port_parent(of_fwnode_handle(ep_node));
> -	bridge->asd.match_type = V4L2_ASYNC_MATCH_FWNODE;
> +	v4l2_async_notifier_init(&bridge->notifier);
> +	asd = v4l2_async_notifier_add_fwnode_remote_subdev(
> +					&bridge->notifier,
> +					of_fwnode_handle(ep_node),
> +					sizeof(*asd));
>  	of_node_put(ep_node);
>  
> -	v4l2_async_notifier_init(&bridge->notifier);
> -	ret = v4l2_async_notifier_add_subdev(&bridge->notifier, &bridge->asd);
> -	if (ret) {
> +	if (IS_ERR(asd)) {
>  		dev_err(&client->dev, "fail to register asd to notifier %d",
> -			ret);
> -		fwnode_handle_put(bridge->asd.match.fwnode);
> -		return ret;
> +			PTR_ERR(asd));
> +		return PTR_ERR(asd);
>  	}
>  	bridge->notifier.ops = &mipid02_notifier_ops;
>  
> 

  reply	other threads:[~2021-01-25 17:24 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-25 13:22 [PATCH 01/14] media: v4l2-async: Clean v4l2_async_notifier_add_fwnode_remote_subdev Sakari Ailus
2021-01-25 13:22 ` [PATCH 02/14] media: atmel: Use v4l2_async_notifier_add_fwnode_remote_subdev Sakari Ailus
2021-01-25 13:22 ` [PATCH 03/14] media: stm32: " Sakari Ailus
2021-01-25 13:22 ` [PATCH 04/14] media: exynos4-is: " Sakari Ailus
2021-01-25 13:22 ` [PATCH 05/14] media: st-mipid02: " Sakari Ailus
2021-01-25 13:22 ` [PATCH 06/14] media: cadence: " Sakari Ailus
2021-01-25 13:22 ` [PATCH 07/14] media: marvell-ccic: Use v4l2_async_notifier_add_*_subdev Sakari Ailus
2021-01-25 13:59   ` Sakari Ailus
2021-01-25 13:22 ` [PATCH 08/14] media: renesas-ceu: " Sakari Ailus
2021-01-25 13:22 ` [PATCH 09/14] media: pxa-camera: " Sakari Ailus
2021-01-25 13:22 ` [PATCH 10/14] media: davinci: vpif_display: Remove unused v4l2-async code Sakari Ailus
2021-01-25 13:22 ` [PATCH 11/14] media: v4l2-async: Fix incorrect comment Sakari Ailus
2021-01-25 13:22 ` [PATCH 12/14] media: Clarify v4l2-async subdevice addition API Sakari Ailus
2021-01-25 13:22 ` [PATCH 13/14] media: v4l2-async: Discourage use of v4l2_async_notifier_add_subdev Sakari Ailus
2021-01-25 13:22 ` [PATCH 14/14] media: v4l2-async: Improve v4l2_async_notifier_add_*_subdev() API Sakari Ailus
2021-01-25 13:22 ` [PATCH v3 00/14] V4L2 Async notifier API cleanup Sakari Ailus
2021-01-25 13:22 ` [PATCH v3 01/14] media: v4l2-async: Clean v4l2_async_notifier_add_fwnode_remote_subdev Sakari Ailus
2021-01-25 15:27   ` Helen Koike
2021-01-25 16:16     ` Sakari Ailus
2021-01-25 13:22 ` [PATCH v3 02/14] media: atmel: Use v4l2_async_notifier_add_fwnode_remote_subdev Sakari Ailus
2021-01-25 13:22 ` [PATCH v3 03/14] media: stm32: " Sakari Ailus
2021-01-25 13:22 ` [PATCH v3 04/14] media: exynos4-is: " Sakari Ailus
2021-01-25 17:22   ` Helen Koike
2021-01-25 13:22 ` [PATCH v3 05/14] media: st-mipid02: " Sakari Ailus
2021-01-25 17:22   ` Helen Koike [this message]
2021-01-25 13:22 ` [PATCH v3 06/14] media: cadence: " Sakari Ailus
2021-01-25 13:22 ` [PATCH v3 07/14] media: marvell-ccic: Use v4l2_async_notifier_add_*_subdev Sakari Ailus
2021-01-25 13:22 ` [PATCH v3 08/14] media: renesas-ceu: " Sakari Ailus
2021-01-25 16:50   ` Helen Koike
2021-01-25 20:43     ` Sakari Ailus
2021-01-25 13:22 ` [PATCH v3 09/14] media: pxa-camera: " Sakari Ailus
2021-01-25 13:22 ` [PATCH v3 10/14] media: davinci: vpif_display: Remove unused v4l2-async code Sakari Ailus
2021-01-25 13:22 ` [PATCH v3 11/14] media: v4l2-async: Fix incorrect comment Sakari Ailus
2021-01-25 16:50   ` Helen Koike
2021-01-25 20:43     ` Sakari Ailus
2021-01-25 13:22 ` [PATCH v3 12/14] media: Clarify v4l2-async subdevice addition API Sakari Ailus
2021-01-25 17:22   ` Helen Koike
2021-01-25 20:42     ` Sakari Ailus
2021-01-25 13:22 ` [PATCH v3 13/14] media: v4l2-async: Discourage use of v4l2_async_notifier_add_subdev Sakari Ailus
2021-01-25 17:22   ` Helen Koike
2021-01-25 13:22 ` [PATCH v3 14/14] media: v4l2-async: Improve v4l2_async_notifier_add_*_subdev() API Sakari Ailus

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=2e9d2224-fd75-aa20-ff3f-fa1e06a75231@collabora.com \
    --to=helen.koike@collabora.com \
    --cc=dafna.hirschfeld@collabora.com \
    --cc=ezequiel@collabora.com \
    --cc=hugues.fruchet@st.com \
    --cc=hverkuil@xs4all.nl \
    --cc=jacopo@jmondi.org \
    --cc=kernel@collabora.com \
    --cc=kieran.bingham+renesas@ideasonboard.com \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-media@vger.kernel.org \
    --cc=mripard@kernel.org \
    --cc=nicolas.ferre@microchip.com \
    --cc=niklas.soderlund+renesas@ragnatech.se \
    --cc=p.zabel@pengutronix.de \
    --cc=robert.foss@linaro.org \
    --cc=s.nawrocki@samsung.com \
    --cc=sakari.ailus@linux.intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.