From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Philipp Zabel <p.zabel@pengutronix.de>
Cc: Mauro Carvalho Chehab <m.chehab@samsung.com>,
linux-media@vger.kernel.org, kernel@pengutronix.de
Subject: Re: [PATCH v2 2/5] [media] mt9v032: register v4l2 asynchronous subdevice
Date: Wed, 04 Jun 2014 16:16:30 +0200 [thread overview]
Message-ID: <2505444.YzkDIeOsnF@avalon> (raw)
In-Reply-To: <1401788155-3690-3-git-send-email-p.zabel@pengutronix.de>
Hi Philipp,
Thank you for the patch.
On Tuesday 03 June 2014 11:35:52 Philipp Zabel wrote:
> Add support for registering the sensor subdevice using the v4l2-async API.
>
> Signed-off-by: Philipp Zabel <p.zabel@pengutronix.de>
> ---
> Changes since v1:
> - Fixed cleanup and error handling
> ---
> drivers/media/i2c/mt9v032.c | 13 ++++++++++++-
> 1 file changed, 12 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/media/i2c/mt9v032.c b/drivers/media/i2c/mt9v032.c
> index 29d8d8f..83ae8ca6d 100644
> --- a/drivers/media/i2c/mt9v032.c
> +++ b/drivers/media/i2c/mt9v032.c
> @@ -985,10 +985,20 @@ static int mt9v032_probe(struct i2c_client *client,
>
> mt9v032->pad.flags = MEDIA_PAD_FL_SOURCE;
> ret = media_entity_init(&mt9v032->subdev.entity, 1, &mt9v032->pad, 0);
> + if (ret < 0)
> + goto err_entity;
>
> + mt9v032->subdev.dev = &client->dev;
> + ret = v4l2_async_register_subdev(&mt9v032->subdev);
> if (ret < 0)
> - v4l2_ctrl_handler_free(&mt9v032->ctrls);
> + goto err_async;
> +
> + return 0;
>
> +err_async:
> + media_entity_cleanup(&mt9v032->subdev.entity);
media_entity_cleanup() can safely be called on an unintialized entity,
provided the memory has been zeroed. You could thus merge the err_async and
err_entity labels into a single error label.
> +err_entity:
> + v4l2_ctrl_handler_free(&mt9v032->ctrls);
> return ret;
> }
>
> @@ -997,6 +1007,7 @@ static int mt9v032_remove(struct i2c_client *client)
> struct v4l2_subdev *subdev = i2c_get_clientdata(client);
> struct mt9v032 *mt9v032 = to_mt9v032(subdev);
>
> + v4l2_async_unregister_subdev(subdev);
> v4l2_ctrl_handler_free(&mt9v032->ctrls);
> v4l2_device_unregister_subdev(subdev);
> media_entity_cleanup(&subdev->entity);
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2014-06-04 14:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-03 9:35 [PATCH v2 0/5] mt9v032: add support for v4l2-async, mt9v02x, and regmap Philipp Zabel
2014-06-03 9:35 ` [PATCH v2 1/5] [media] mt9v032: reset is self clearing Philipp Zabel
2014-06-04 14:49 ` Laurent Pinchart
2014-06-04 15:03 ` Philipp Zabel
2014-06-03 9:35 ` [PATCH v2 2/5] [media] mt9v032: register v4l2 asynchronous subdevice Philipp Zabel
2014-06-04 14:16 ` Laurent Pinchart [this message]
2014-06-04 15:04 ` Philipp Zabel
2014-06-03 9:35 ` [PATCH v2 3/5] [media] mt9v032: do not clear reserved bits in read mode register Philipp Zabel
2014-06-04 14:50 ` Laurent Pinchart
2014-06-03 9:35 ` [PATCH v2 4/5] [media] mt9v032: add support for mt9v022 and mt9v024 Philipp Zabel
2014-06-04 14:54 ` Laurent Pinchart
2014-06-03 9:35 ` [PATCH v2 5/5] [media] mt9v032: use regmap Philipp Zabel
2014-06-04 15:44 ` Laurent Pinchart
2014-06-04 16:45 ` Philipp Zabel
2014-06-04 23:46 ` Laurent Pinchart
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=2505444.YzkDIeOsnF@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=kernel@pengutronix.de \
--cc=linux-media@vger.kernel.org \
--cc=m.chehab@samsung.com \
--cc=p.zabel@pengutronix.de \
/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).