From: Ramiro Oliveira <Ramiro.Oliveira@synopsys.com>
To: Pavel Machek <pavel@ucw.cz>,
Ramiro Oliveira <Ramiro.Oliveira@synopsys.com>
Cc: <mchehab@kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-media@vger.kernel.org>, <robh+dt@kernel.org>,
<devicetree@vger.kernel.org>, <davem@davemloft.net>,
<gregkh@linuxfoundation.org>, <geert+renesas@glider.be>,
<akpm@linux-foundation.org>, <linux@roeck-us.net>,
<hverkuil@xs4all.nl>, <dheitmueller@kernellabs.com>,
<slongerbeam@gmail.com>, <lars@metafoo.de>,
<robert.jarzmik@free.fr>, <pali.rohar@gmail.com>,
<sakari.ailus@linux.intel.com>, <mark.rutland@arm.com>,
<CARLOS.PALMINHA@synopsys.com>
Subject: Re: [PATCH v4 2/2] Add support for OV5647 sensor
Date: Mon, 21 Nov 2016 15:00:40 +0000 [thread overview]
Message-ID: <9992afb4-d0a4-6101-6381-aaef0c09b9df@synopsys.com> (raw)
In-Reply-To: <20161115121032.GB7018@amd>
Hi Pavel!
On 11/15/2016 12:10 PM, Pavel Machek wrote:
> Hi!
>
>> Add support for OV5647 sensor.
>>
>
>> +static int ov5647_write(struct v4l2_subdev *sd, u16 reg, u8 val)
>> +{
>> + int ret;
>> + unsigned char data[3] = { reg >> 8, reg & 0xff, val};
>> + struct i2c_client *client = v4l2_get_subdevdata(sd);
>> +
>> + ret = i2c_master_send(client, data, 3);
>> + if (ret != 3) {
>> + dev_dbg(&client->dev, "%s: i2c write error, reg: %x\n",
>> + __func__, reg);
>> + return ret < 0 ? ret : -EIO;
>> + }
>> + return 0;
>> +}
>
> Sorry, this is wrong. It should something <0 any time error is detected.
>
>> +static int ov5647_write_array(struct v4l2_subdev *sd,
>> + struct regval_list *regs, int array_size)
>> +{
>> + int i = 0;
>> + int ret = 0;
>> +
>> + if (!regs)
>> + return -EINVAL;
>> +
>> + while (i < array_size) {
>> + ret = ov5647_write(sd, regs->addr, regs->data);
>> + if (ret < 0)
>> + return ret;
>> + i++;
>> + regs++;
>> + }
>> + return 0;
>> +}
>
> For example this expects <0 on error.
>
>> +static int set_sw_standby(struct v4l2_subdev *sd, bool standby)
>> +{
>> + int ret;
>> + unsigned char rdval;
>> +
>> + ret = ov5647_read(sd, 0x0100, &rdval);
>> + if (ret != 0)
>> + return ret;
>> +
>> + if (standby)
>> + ret = ov5647_write(sd, 0x0100, rdval&0xfe);
>> + else
>> + ret = ov5647_write(sd, 0x0100, rdval|0x01);
>> +
>> + return ret;
>
> if (standby)
> rdval &= 0xfe;
> else
> rdval |= 0x01;
>
> ret = ov5647_write(sd, 0x0100, rdval);
>
> ?
>
>
>> +/**
>> + * @short Store information about the video data format.
>> + */
>> +static struct sensor_format_struct {
>> + __u8 *desc;
>> + u32 mbus_code;
>
> u8 is suitable here.
>
>
>> + ov5647_read(sd, 0x0100, &resetval);
>> + if (!resetval&0x01) {
>
> add ()s here.
>
>> +static int sensor_power(struct v4l2_subdev *sd, int on)
>> +{
>> + int ret;
>> + struct ov5647 *ov5647 = to_state(sd);
>> + struct i2c_client *client = v4l2_get_subdevdata(sd);
>> +
>> + ret = 0;
>> + mutex_lock(&ov5647->lock);
>> +
>> + if (on) {
>> + dev_dbg(&client->dev, "OV5647 power on!\n");
>> +
>> + ret = ov5647_write_array(sd, sensor_oe_enable_regs,
>> + ARRAY_SIZE(sensor_oe_enable_regs));
>> +
>> + ret = __sensor_init(sd);
>> +
>> + if (ret < 0)
>> + dev_err(&client->dev,
>> + "Camera not available! Check Power!\n");
>> + } else {
>> + dev_dbg(&client->dev, "OV5647 power off!\n");
>> +
>> + dev_dbg(&client->dev, "disable oe\n");
>> + ret = ov5647_write_array(sd, sensor_oe_disable_regs,
>> + ARRAY_SIZE(sensor_oe_disable_regs));
>> +
>> + if (ret < 0)
>> + dev_dbg(&client->dev, "disable oe failed!\n");
>> +
>> + ret = set_sw_standby(sd, true);
>> +
>> + if (ret < 0)
>> + dev_dbg(&client->dev, "soft stby failed!\n");
>
> dev_err for errors? Little less "!"s in the output?
>
>> +static int sensor_get_register(struct v4l2_subdev *sd,
>> + struct v4l2_dbg_register *reg)
>> +{
>> + unsigned char val = 0;
>> + int ret;
>> +
>> + ret = ov5647_read(sd, reg->reg & 0xff, &val);
>> + reg->val = val;
>> + reg->size = 1;
>> + return ret;
>> +}
>
> Filling reg->* when read failed is strange.
>
>> +static int sensor_set_register(struct v4l2_subdev *sd,
>> + const struct v4l2_dbg_register *reg)
>> +{
>> + ov5647_write(sd, reg->reg & 0xff, reg->val & 0xff);
>> + return 0;
>> +}
>
> error handling?
>
> Best regards,
> Pavel
>
Thanks for the feedback, I've corrected all the issues you pointed out, except
the one regarding the error handling in the ov5647_write function.
Best Regards,
Ramiro
prev parent reply other threads:[~2016-11-21 15:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-14 13:46 [PATCH v4 0/2] Add support for Omnivision OV5647 Ramiro Oliveira
2016-11-14 13:46 ` [PATCH v4 1/2] Add OV5647 device tree documentation Ramiro Oliveira
2016-11-16 13:21 ` Rob Herring
2016-11-14 13:46 ` [PATCH v4 2/2] Add support for OV5647 sensor Ramiro Oliveira
2016-11-15 12:10 ` Pavel Machek
2016-11-15 13:50 ` Guenter Roeck
2016-11-15 14:52 ` Pavel Machek
2016-11-21 15:00 ` Ramiro Oliveira [this message]
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=9992afb4-d0a4-6101-6381-aaef0c09b9df@synopsys.com \
--to=ramiro.oliveira@synopsys.com \
--cc=CARLOS.PALMINHA@synopsys.com \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=dheitmueller@kernellabs.com \
--cc=geert+renesas@glider.be \
--cc=gregkh@linuxfoundation.org \
--cc=hverkuil@xs4all.nl \
--cc=lars@metafoo.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=mark.rutland@arm.com \
--cc=mchehab@kernel.org \
--cc=pali.rohar@gmail.com \
--cc=pavel@ucw.cz \
--cc=robert.jarzmik@free.fr \
--cc=robh+dt@kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®