From: Sylwester Nawrocki <s.nawrocki@samsung.com>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: linux-media@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH] v4l: mt9v032: Add OF support
Date: Mon, 09 Mar 2015 11:35:52 +0100 [thread overview]
Message-ID: <54FD7788.2020709@samsung.com> (raw)
In-Reply-To: <1425822349-19218-1-git-send-email-laurent.pinchart@ideasonboard.com>
Hi Laurent,
On 08/03/15 14:45, Laurent Pinchart wrote:
> +++ b/Documentation/devicetree/bindings/media/i2c/mt9v032.txt
> @@ -0,0 +1,41 @@
> +* Aptina 1/3-Inch WVGA CMOS Digital Image Sensor
> +
> +The Aptina MT9V032 is a 1/3-inch CMOS active pixel digital image sensor with
> +an active array size of 752H x 480V. It is programmable through a simple
> +two-wire serial interface.
> +
> +Required Properties:
> +
> +- compatible: value should be either one among the following
> + (a) "aptina,mt9v032" for MT9V032 color sensor
> + (b) "aptina,mt9v032m" for MT9V032 monochrome sensor
> + (c) "aptina,mt9v034" for MT9V034 color sensor
> + (d) "aptina,mt9v034m" for MT9V034 monochrome sensor
It can't be determined at runtime whether the sensor is just monochromatic ?
Al in all the color filter array is a physical property of the sensor, still
the driver seems to be ignoring the "m" suffix. Hence I suspect the register
interfaces for both color and monochromatic versions are compatible.
I'm wondering whether using a boolean property to indicate the color filter
array type would do as well.
> +static struct mt9v032_platform_data *
> +mt9v032_get_pdata(struct i2c_client *client)
> +{
> + struct mt9v032_platform_data *pdata;
> + struct v4l2_of_endpoint endpoint;
> + struct device_node *np;
> + struct property *prop;
> +
> + if (!IS_ENABLED(CONFIG_OF) || !client->dev.of_node)
> + return client->dev.platform_data;
> +
> + np = v4l2_of_get_next_endpoint(client->dev.of_node, NULL);
> + if (!np)
> + return NULL;
> +
> + if (v4l2_of_parse_endpoint(np, &endpoint) < 0)
> + goto done;
> +
> + pdata = devm_kzalloc(&client->dev, sizeof(*pdata), GFP_KERNEL);
> + if (!pdata)
> + goto done;
> +
> + prop = of_find_property(np, "link-freqs", NULL);
I suspect you meant "link-frequencies" here ?
> + if (prop) {
> + size_t size = prop->length / 8;
> + u64 *link_freqs;
> +
> + link_freqs = devm_kzalloc(&client->dev,
> + size * sizeof(*link_freqs),
> + GFP_KERNEL);
> + if (!link_freqs)
> + goto done;
> +
> + if (of_property_read_u64_array(np, "link-frequencies",
> + link_freqs, size) < 0)
> + goto done;
> +
> + pdata->link_freqs = link_freqs;
> + pdata->link_def_freq = link_freqs[0];
> + }
> +
> + pdata->clk_pol = !!(endpoint.bus.parallel.flags &
> + V4L2_MBUS_PCLK_SAMPLE_RISING);
> +
> +done:
> + of_node_put(np);
> + return pdata;
> +}
> @@ -1034,9 +1086,21 @@ static const struct i2c_device_id mt9v032_id[] = {
> };
> MODULE_DEVICE_TABLE(i2c, mt9v032_id);
>
> +#if IS_ENABLED(CONFIG_OF)
> +static const struct of_device_id mt9v032_of_match[] = {
> + { .compatible = "mt9v032" },
> + { .compatible = "mt9v032m" },
> + { .compatible = "mt9v034" },
> + { .compatible = "mt9v034m" },
> + { /* Sentinel */ }
> +};
> +MODULE_DEVICE_TABLE(of, mt9v032_of_match);
> +#endif
--
Thanks,
Sylwester
next prev parent reply other threads:[~2015-03-09 10:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-08 13:45 [PATCH] v4l: mt9v032: Add OF support Laurent Pinchart
2015-03-09 9:45 ` Carlos Sanmartín Bustos
[not found] ` <CAPW4HR1WJPWg64GwitxCPK2jop0CntS1UtsOu_0VjCz0BEke6A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-03-09 11:19 ` Laurent Pinchart
2015-03-09 16:03 ` Carlos Sanmartín Bustos
2015-03-09 10:35 ` Sylwester Nawrocki [this message]
2015-03-09 10:57 ` Sakari Ailus
2015-03-09 11:57 ` Sylwester Nawrocki
[not found] ` <54FD7788.2020709-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2015-03-09 11:29 ` Laurent Pinchart
2015-03-09 12:22 ` Sylwester Nawrocki
[not found] ` <54FD9074.8050600-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2015-03-12 23:41 ` 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=54FD7788.2020709@samsung.com \
--to=s.nawrocki@samsung.com \
--cc=devicetree@vger.kernel.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
/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).