All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rui Miguel Silva <rmfrfs@gmail.com>
To: Hans Verkuil <hverkuil@xs4all.nl>
Cc: devel@driverdev.osuosl.org, devicetree@vger.kernel.org,
	sakari.ailus@linux.intel.com,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Philipp Zabel <p.zabel@pengutronix.de>,
	Steve Longerbeam <slongerbeam@gmail.com>,
	linux-media@vger.kernel.org
Subject: Re: [PATCH v14 05/13] media: staging/imx7: add MIPI CSI-2 receiver subdev for i.MX7
Date: Wed, 20 Feb 2019 11:26:42 +0000	[thread overview]
Message-ID: <m35zteu2dp.fsf@gmail.com> (raw)
In-Reply-To: <6c6c0e29-d65b-3796-578c-2e3e6f742d11@xs4all.nl>

Hi Hans,
On Wed 20 Feb 2019 at 08:56, Hans Verkuil wrote:
> On 2/6/19 4:13 PM, Rui Miguel Silva wrote:
>> Adds MIPI CSI-2 subdev for i.MX7 to connect with sensors with a 
>> MIPI
>> CSI-2 interface.
>> 
>> Signed-off-by: Rui Miguel Silva <rui.silva@linaro.org>
>> ---
>>  drivers/staging/media/imx/Makefile         |    1 +
>>  drivers/staging/media/imx/imx7-mipi-csis.c | 1186 
>>  ++++++++++++++++++++
>>  2 files changed, 1187 insertions(+)
>>  create mode 100644 drivers/staging/media/imx/imx7-mipi-csis.c
>> 
>> diff --git a/drivers/staging/media/imx/Makefile 
>> b/drivers/staging/media/imx/Makefile
>> index 074f016d3519..d2d909a36239 100644
>> --- a/drivers/staging/media/imx/Makefile
>> +++ b/drivers/staging/media/imx/Makefile
>> @@ -14,3 +14,4 @@ obj-$(CONFIG_VIDEO_IMX_CSI) += 
>> imx-media-csi.o
>>  obj-$(CONFIG_VIDEO_IMX_CSI) += imx6-mipi-csi2.o
>>  
>>  obj-$(CONFIG_VIDEO_IMX7_CSI) += imx7-media-csi.o
>> +obj-$(CONFIG_VIDEO_IMX7_CSI) += imx7-mipi-csis.o
>> diff --git a/drivers/staging/media/imx/imx7-mipi-csis.c 
>> b/drivers/staging/media/imx/imx7-mipi-csis.c
>> new file mode 100644
>> index 000000000000..516d308dc44b
>> --- /dev/null
>> +++ b/drivers/staging/media/imx/imx7-mipi-csis.c
>> @@ -0,0 +1,1186 @@
>
> <snip>
>
>> +static int mipi_csi_registered(struct v4l2_subdev *mipi_sd)
>> +{
>> +	struct csi_state *state = mipi_sd_to_csis_state(mipi_sd);
>> +	unsigned int i;
>> +	int ret;
>> +
>> +	for (i = 0; i < CSIS_PADS_NUM; i++) {
>> +		state->pads[i].flags = (i == CSIS_PAD_SINK) ?
>> +			MEDIA_PAD_FL_SINK : MEDIA_PAD_FL_SOURCE;
>> +	}
>> +
>> +	/* set a default mbus format  */
>> +	ret = imx_media_init_mbus_fmt(&state->format_mbus,
>> +				      MIPI_CSIS_DEF_PIX_HEIGHT,
>> +				      MIPI_CSIS_DEF_PIX_WIDTH, 0,
>> +				      V4L2_FIELD_NONE, NULL);
>> +	if (ret)
>> +		return ret;
>> +
>> +	return media_entity_pads_init(&mipi_sd->entity, 
>> CSIS_PADS_NUM,
>> +				      state->pads);
>> +}
>> +
>> +static const struct v4l2_subdev_core_ops mipi_csis_core_ops = 
>> {
>> +	.log_status	= mipi_csis_log_status,
>> +};
>> +
>> +static const struct media_entity_operations 
>> mipi_csis_entity_ops = {
>> +	.link_setup	= mipi_csis_link_setup,
>> +	.link_validate	= v4l2_subdev_link_validate,
>> +};
>> +
>> +static const struct v4l2_subdev_video_ops mipi_csis_video_ops 
>> = {
>> +	.s_stream	= mipi_csis_s_stream,
>> +};
>> +
>> +static const struct v4l2_subdev_pad_ops mipi_csis_pad_ops = {
>> +	.init_cfg		= mipi_csis_init_cfg,
>> +	.get_fmt		= mipi_csis_get_fmt,
>> +	.set_fmt		= mipi_csis_set_fmt,
>> +};
>> +
>> +static const struct v4l2_subdev_ops mipi_csis_subdev_ops = {
>> +	.core	= &mipi_csis_core_ops,
>> +	.video	= &mipi_csis_video_ops,
>> +	.pad	= &mipi_csis_pad_ops,
>> +};
>> +
>> +static const struct v4l2_subdev_internal_ops 
>> mipi_csis_internal_ops = {
>> +	.registered = mipi_csi_registered,
>> +};
>
> This struct is not used, and therefor mipi_csi_registered() is 
> never called
> either. Should it be called or can this be removed?

Good question :), I will get back to you on this one later.

---
Cheers,
	Rui

WARNING: multiple messages have this Message-ID (diff)
From: Rui Miguel Silva <rmfrfs@gmail.com>
To: Hans Verkuil <hverkuil@xs4all.nl>
Cc: sakari.ailus@linux.intel.com,
	Steve Longerbeam <slongerbeam@gmail.com>,
	Philipp Zabel <p.zabel@pengutronix.de>,
	devel@driverdev.osuosl.org, devicetree@vger.kernel.org,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	linux-media@vger.kernel.org
Subject: Re: [PATCH v14 05/13] media: staging/imx7: add MIPI CSI-2 receiver subdev for i.MX7
Date: Wed, 20 Feb 2019 11:26:42 +0000	[thread overview]
Message-ID: <m35zteu2dp.fsf@gmail.com> (raw)
In-Reply-To: <6c6c0e29-d65b-3796-578c-2e3e6f742d11@xs4all.nl>

Hi Hans,
On Wed 20 Feb 2019 at 08:56, Hans Verkuil wrote:
> On 2/6/19 4:13 PM, Rui Miguel Silva wrote:
>> Adds MIPI CSI-2 subdev for i.MX7 to connect with sensors with a 
>> MIPI
>> CSI-2 interface.
>> 
>> Signed-off-by: Rui Miguel Silva <rui.silva@linaro.org>
>> ---
>>  drivers/staging/media/imx/Makefile         |    1 +
>>  drivers/staging/media/imx/imx7-mipi-csis.c | 1186 
>>  ++++++++++++++++++++
>>  2 files changed, 1187 insertions(+)
>>  create mode 100644 drivers/staging/media/imx/imx7-mipi-csis.c
>> 
>> diff --git a/drivers/staging/media/imx/Makefile 
>> b/drivers/staging/media/imx/Makefile
>> index 074f016d3519..d2d909a36239 100644
>> --- a/drivers/staging/media/imx/Makefile
>> +++ b/drivers/staging/media/imx/Makefile
>> @@ -14,3 +14,4 @@ obj-$(CONFIG_VIDEO_IMX_CSI) += 
>> imx-media-csi.o
>>  obj-$(CONFIG_VIDEO_IMX_CSI) += imx6-mipi-csi2.o
>>  
>>  obj-$(CONFIG_VIDEO_IMX7_CSI) += imx7-media-csi.o
>> +obj-$(CONFIG_VIDEO_IMX7_CSI) += imx7-mipi-csis.o
>> diff --git a/drivers/staging/media/imx/imx7-mipi-csis.c 
>> b/drivers/staging/media/imx/imx7-mipi-csis.c
>> new file mode 100644
>> index 000000000000..516d308dc44b
>> --- /dev/null
>> +++ b/drivers/staging/media/imx/imx7-mipi-csis.c
>> @@ -0,0 +1,1186 @@
>
> <snip>
>
>> +static int mipi_csi_registered(struct v4l2_subdev *mipi_sd)
>> +{
>> +	struct csi_state *state = mipi_sd_to_csis_state(mipi_sd);
>> +	unsigned int i;
>> +	int ret;
>> +
>> +	for (i = 0; i < CSIS_PADS_NUM; i++) {
>> +		state->pads[i].flags = (i == CSIS_PAD_SINK) ?
>> +			MEDIA_PAD_FL_SINK : MEDIA_PAD_FL_SOURCE;
>> +	}
>> +
>> +	/* set a default mbus format  */
>> +	ret = imx_media_init_mbus_fmt(&state->format_mbus,
>> +				      MIPI_CSIS_DEF_PIX_HEIGHT,
>> +				      MIPI_CSIS_DEF_PIX_WIDTH, 0,
>> +				      V4L2_FIELD_NONE, NULL);
>> +	if (ret)
>> +		return ret;
>> +
>> +	return media_entity_pads_init(&mipi_sd->entity, 
>> CSIS_PADS_NUM,
>> +				      state->pads);
>> +}
>> +
>> +static const struct v4l2_subdev_core_ops mipi_csis_core_ops = 
>> {
>> +	.log_status	= mipi_csis_log_status,
>> +};
>> +
>> +static const struct media_entity_operations 
>> mipi_csis_entity_ops = {
>> +	.link_setup	= mipi_csis_link_setup,
>> +	.link_validate	= v4l2_subdev_link_validate,
>> +};
>> +
>> +static const struct v4l2_subdev_video_ops mipi_csis_video_ops 
>> = {
>> +	.s_stream	= mipi_csis_s_stream,
>> +};
>> +
>> +static const struct v4l2_subdev_pad_ops mipi_csis_pad_ops = {
>> +	.init_cfg		= mipi_csis_init_cfg,
>> +	.get_fmt		= mipi_csis_get_fmt,
>> +	.set_fmt		= mipi_csis_set_fmt,
>> +};
>> +
>> +static const struct v4l2_subdev_ops mipi_csis_subdev_ops = {
>> +	.core	= &mipi_csis_core_ops,
>> +	.video	= &mipi_csis_video_ops,
>> +	.pad	= &mipi_csis_pad_ops,
>> +};
>> +
>> +static const struct v4l2_subdev_internal_ops 
>> mipi_csis_internal_ops = {
>> +	.registered = mipi_csi_registered,
>> +};
>
> This struct is not used, and therefor mipi_csi_registered() is 
> never called
> either. Should it be called or can this be removed?

Good question :), I will get back to you on this one later.

---
Cheers,
	Rui


  reply	other threads:[~2019-02-20 11:26 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-06 15:13 [PATCH v14 00/13] media: staging/imx7: add i.MX7 media driver Rui Miguel Silva
2019-02-06 15:13 ` Rui Miguel Silva
2019-02-06 15:13 ` [PATCH v14 01/13] media: staging/imx: refactor imx media device probe Rui Miguel Silva
2019-02-06 15:13   ` Rui Miguel Silva
2019-02-06 15:36   ` Hans Verkuil
2019-02-06 15:36     ` Hans Verkuil
2019-02-06 16:11   ` [PATCH v14.1] " Rui Miguel Silva
2019-02-06 15:13 ` [PATCH v14 02/13] media: staging/imx: rearrange group id to take in account IPU Rui Miguel Silva
2019-02-06 15:13   ` Rui Miguel Silva
2019-02-06 15:13 ` [PATCH v14 03/13] media: dt-bindings: add bindings for i.MX7 media driver Rui Miguel Silva
2019-02-06 15:13   ` Rui Miguel Silva
2019-02-06 15:13 ` [PATCH v14 04/13] media: staging/imx7: add imx7 CSI subdev driver Rui Miguel Silva
2019-02-06 15:13   ` Rui Miguel Silva
2019-02-06 15:13 ` [PATCH v14 05/13] media: staging/imx7: add MIPI CSI-2 receiver subdev for i.MX7 Rui Miguel Silva
2019-02-06 15:13   ` Rui Miguel Silva
2019-02-06 22:53   ` [PATCH v14.1] " Rui Miguel Silva
2019-02-20  8:56   ` [PATCH v14 05/13] " Hans Verkuil
2019-02-20  8:56     ` Hans Verkuil
2019-02-20 11:26     ` Rui Miguel Silva [this message]
2019-02-20 11:26       ` Rui Miguel Silva
2019-02-06 15:13 ` [PATCH v14 06/13] ARM: dts: imx7s: add mipi phy power domain Rui Miguel Silva
2019-02-06 15:13   ` Rui Miguel Silva
2019-02-06 15:13 ` [PATCH v14 07/13] ARM: dts: imx7s: add multiplexer controls Rui Miguel Silva
2019-02-06 15:13   ` Rui Miguel Silva
2019-02-06 15:13 ` [PATCH v14 08/13] ARM: dts: imx7: Add video mux, csi and mipi_csi and connections Rui Miguel Silva
2019-02-06 15:13   ` Rui Miguel Silva
2019-03-10 21:41   ` Laurent Pinchart
2019-03-10 21:41     ` Laurent Pinchart
2019-03-12 14:05     ` Rui Miguel Silva
2019-03-12 14:05       ` Rui Miguel Silva
2019-03-12 14:10       ` Laurent Pinchart
2019-03-12 14:10         ` Laurent Pinchart
2019-03-12 15:35         ` Rui Miguel Silva
2019-03-12 15:35           ` Rui Miguel Silva
2019-02-06 15:13 ` [PATCH v14 09/13] ARM: dts: imx7s-warp: add ov2680 sensor node Rui Miguel Silva
2019-02-06 15:13   ` Rui Miguel Silva
2019-02-06 15:13 ` [PATCH v14 10/13] media: imx7.rst: add documentation for i.MX7 media driver Rui Miguel Silva
2019-02-06 15:13   ` Rui Miguel Silva
2019-02-06 15:13 ` [PATCH v14 11/13] media: staging/imx: add i.MX7 entries to TODO file Rui Miguel Silva
2019-02-06 15:13   ` Rui Miguel Silva
2019-02-06 15:13 ` [PATCH v14 12/13] media: video-mux: add bayer formats Rui Miguel Silva
2019-02-06 15:13   ` Rui Miguel Silva
2019-02-06 15:13 ` [PATCH v14 13/13] media: MAINTAINERS: add entry for Freescale i.MX7 media driver Rui Miguel Silva
2019-02-06 15:13   ` Rui Miguel Silva

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=m35zteu2dp.fsf@gmail.com \
    --to=rmfrfs@gmail.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=devicetree@vger.kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=hverkuil@xs4all.nl \
    --cc=linux-media@vger.kernel.org \
    --cc=p.zabel@pengutronix.de \
    --cc=sakari.ailus@linux.intel.com \
    --cc=slongerbeam@gmail.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.