From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Prabhakar Lad <prabhakar.csengg@gmail.com>
Cc: Sascha Hauer <s.hauer@pengutronix.de>,
LMML <linux-media@vger.kernel.org>,
Mauro Carvalho Chehab <mchehab@redhat.com>,
DLOS <davinci-linux-open-source@linux.davincidsp.com>,
Hans Verkuil <hans.verkuil@cisco.com>,
Guennadi Liakhovetski <g.liakhovetski@gmx.de>,
LKML <linux-kernel@vger.kernel.org>,
Sakari Ailus <sakari.ailus@iki.fi>,
Sylwester Nawrocki <s.nawrocki@samsung.com>,
Grant Likely <grant.likely@secretlab.ca>,
Rob Herring <rob.herring@calxeda.com>,
Rob Landley <rob@landley.net>,
devicetree-discuss@lists.ozlabs.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH RFC v2] media: i2c: mt9p031: add OF support
Date: Thu, 02 May 2013 13:02:24 +0200 [thread overview]
Message-ID: <1561679.1AUpDgdnFy@avalon> (raw)
In-Reply-To: <CA+V-a8tbbgbyNF37_u-cbWQCDphhb0q+wQSGnBdYVS90o+HSXw@mail.gmail.com>
Hi Prabhakar,
Thank you for the patch.
On Thursday 02 May 2013 12:34:25 Prabhakar Lad wrote:
> On Thu, May 2, 2013 at 12:25 PM, Sascha Hauer wrote:
> > On Thu, May 02, 2013 at 11:52:34AM +0530, Prabhakar Lad wrote:
> >> From: Lad, Prabhakar <prabhakar.csengg@gmail.com>
> >>
> >> add OF support for the mt9p031 sensor driver.
> >> Alongside this patch sorts the header inclusion alphabetically.
>
> [Snip]
>
> >> +#if defined(CONFIG_OF)
> >> +static struct mt9p031_platform_data *
> >> + mt9p031_get_pdata(struct i2c_client *client)
Please align this line on the left.
> >> +{
> >> + if (client->dev.of_node) {
> >
> > By inverting the logic here and returning immediately you can safe an
> > indention level for the bulk of this function.
>
> OK
>
> >> + struct device_node *np;
> >> + struct mt9p031_platform_data *pdata;
> >> +
> >> + np = v4l2_of_get_next_endpoint(client->dev.of_node, NULL);
> >> + if (!np)
> >> + return NULL;
> >> +
> >> + pdata = devm_kzalloc(&client->dev,
> >> + sizeof(struct mt9p031_platform_data),
> >> + GFP_KERNEL);
> >> + if (!pdata) {
> >> + dev_err(&client->dev,
> >> + "mt9p031 failed allocate memeory\n");
> >> + return NULL;
> >
> > s/memeory/memory/
> >
> > Better drop this message completely. If you are really out of memory
> > you'll notice it quite fast anyway.
>
> alright I'll drop the message.
>
> >> + }
> >> + pdata->reset = of_get_named_gpio(client->dev.of_node,
> >> + "gpio-reset", 0);
> >> + if (!gpio_is_valid(pdata->reset))
> >> + pdata->reset = -1;
I've just sent a patch that converts the manual -1 checks in the driver to
gpio_is_valid(). You can thus drop these two lines.
> >> + if (of_property_read_u32(np, "input-clock-frequency",
> >> + &pdata->ext_freq))
> >> + return NULL;
> >> +
> >> + if (of_property_read_u32(np, "pixel-clock-frequency",
> >> + &pdata->target_freq))
> >> + return NULL;
> >
> > returning NULL here means that when these properties are missing the
> > driver bails out with the message "No platform data\n" which is not
> > very helpful for users. How about just ignoring this here and return
> > pdata? The driver will probably print a more useful message later when
> > it notices that the clock params are invalid.
>
> Yes would be good idea of not returning NULL.
>
> >> +
> >> + return pdata;
> >> + }
> >> +
> >> + return client->dev.platform_data;
> >> +}
> >> +#else
> >> +static struct mt9p031_platform_data *
> >> + mt9p031_get_pdata(struct i2c_client *client)
> >> +{
> >> + return client->dev.platform_data;
> >> +}
> >> +#endif
> >> +
> >>
> >> static int mt9p031_probe(struct i2c_client *client,
> >> const struct i2c_device_id *did)
> >> {
> >> - struct mt9p031_platform_data *pdata = client->dev.platform_data;
> >> + struct mt9p031_platform_data *pdata = mt9p031_get_pdata(client);
> >>
> >> struct i2c_adapter *adapter = to_i2c_adapter(client->dev.parent);
> >> struct mt9p031 *mt9p031;
> >> unsigned int i;
> >> @@ -1070,8 +1120,16 @@ static const struct i2c_device_id mt9p031_id[] = {
> >>
> >> };
> >> MODULE_DEVICE_TABLE(i2c, mt9p031_id);
> >>
> >> +static const struct of_device_id mt9p031_of_match[] = {
> >> + { .compatible = "aptina,mt9p031", },
> >> + { .compatible = "aptina,mt9p031m", },
> >> + {},
> >> +};
> >
> > I would have expected something like:
> >
> > static const struct of_device_id mt9p031_of_match[] = {
> > {
> > .compatible = "aptina,mt9p031-sensor",
> > .data = (void *)MT9P031_MODEL_COLOR,
> > }, {
> > .compatible = "aptina,mt9p031m-sensor",
> > .data = (void *)MT9P031_MODEL_MONOCHROME,
> > }, {
> > /* sentinel */
> > },
> > };
> >
> > of_id = of_match_device(mt9p031_of_match, &client->dev);
> > if (of_id)
> > mt9p031->model = (enum mt9p031_model)of_id->data;
> >
> > To handle monochrome sensors.
>
> OK will do the same.
And please guard the table with #ifdef CONFIG_OF.
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2013-05-02 11:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-02 6:22 [PATCH RFC v2] media: i2c: mt9p031: add OF support Prabhakar Lad
2013-05-02 6:55 ` Sascha Hauer
2013-05-02 7:04 ` Prabhakar Lad
2013-05-02 11:02 ` Laurent Pinchart [this message]
2013-05-02 13:18 ` Prabhakar Lad
2013-05-02 13:24 ` Laurent Pinchart
2013-05-02 13:42 ` Arnd Bergmann
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=1561679.1AUpDgdnFy@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=davinci-linux-open-source@linux.davincidsp.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=g.liakhovetski@gmx.de \
--cc=grant.likely@secretlab.ca \
--cc=hans.verkuil@cisco.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@redhat.com \
--cc=prabhakar.csengg@gmail.com \
--cc=rob.herring@calxeda.com \
--cc=rob@landley.net \
--cc=s.hauer@pengutronix.de \
--cc=s.nawrocki@samsung.com \
--cc=sakari.ailus@iki.fi \
/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).