devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ramiro Oliveira <Ramiro.Oliveira@synopsys.com>
To: Vladimir Zapolskiy <vladimir_zapolskiy@mentor.com>,
	Ramiro Oliveira <Ramiro.Oliveira@synopsys.com>,
	linux-kernel@vger.kernel.org, linux-media@vger.kernel.org,
	devicetree@vger.kernel.org
Cc: CARLOS.PALMINHA@synopsys.com,
	"David S. Miller" <davem@davemloft.net>,
	"Geert Uytterhoeven" <geert+renesas@glider.be>,
	"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
	"Guenter Roeck" <linux@roeck-us.net>,
	"Hans Verkuil" <hans.verkuil@cisco.com>,
	"Ivaylo Dimitrov" <ivo.g.dimitrov.75@gmail.com>,
	"Mark Rutland" <mark.rutland@arm.com>,
	"Mauro Carvalho Chehab" <mchehab@kernel.org>,
	"Pali Rohár" <pali.rohar@gmail.com>,
	"Pavel Machek" <pavel@ucw.cz>,
	"Robert Jarzmik" <robert.jarzmik@free.fr>,
	"Rob Herring" <robh+dt@kernel.org>,
	"Sakari Ailus" <sakari.ailus@linux.intel.com>,
	"Steve Longerbeam" <slongerbeam@gmail.com>
Subject: Re: [PATCH v9 2/2] Add support for OV5647 sensor.
Date: Tue, 21 Feb 2017 16:42:13 +0000	[thread overview]
Message-ID: <c39814c2-20a0-db08-38c1-ce95ccc49738@synopsys.com> (raw)
In-Reply-To: <cea82e22-07eb-dd8a-c781-7384ac27823e@mentor.com>

Hi Vladimir,

Thank you for your feedback

On 2/21/2017 3:54 PM, Vladimir Zapolskiy wrote:
> Hi Ramiro,
> 
> please find some review comments below.
> 
> On 02/17/2017 03:14 PM, Ramiro Oliveira wrote:
>> The OV5647 sensor from Omnivision supports up to 2592x1944 @ 15 fps, RAW 8
>> and RAW 10 output formats, and MIPI CSI-2 interface.
>>
>> The driver adds support for 640x480 RAW 8.
>>
>> Signed-off-by: Ramiro Oliveira <roliveir@synopsys.com>
>> ---
> 
> [snip]
> 
>> +
>> +struct ov5647 {
>> +	struct v4l2_subdev		sd;
>> +	struct media_pad		pad;
>> +	struct mutex			lock;
>> +	struct v4l2_mbus_framefmt	format;
>> +	unsigned int			width;
>> +	unsigned int			height;
>> +	int				power_count;
>> +	struct clk			*xclk;
>> +	/* External clock frequency currently supported is 30MHz */
>> +	u32				xclk_freq;
> 
> See a comment about 25MHz vs 30MHz below.
> 
> Also I assume you can remove 'xclk_freq' from the struct fields,
> it can be replaced by a local variable.
> 

I'll do that.

>> +};
> 
> [snip]
> 
>> +
>> +static int ov5647_read(struct v4l2_subdev *sd, u16 reg, u8 *val)
>> +{
>> +	int ret;
>> +	unsigned char data_w[2] = { reg >> 8, reg & 0xff };
>> +	struct i2c_client *client = v4l2_get_subdevdata(sd);
>> +
>> +	ret = i2c_master_send(client, data_w, 2);
>> +	if (ret < 0) {
>> +		dev_dbg(&client->dev, "%s: i2c read error, reg: %x\n",
> 
> s/i2c read error/i2c write error/
> 

I'm not sure I understand what you mean.

>> +			__func__, reg);
>> +		return ret;
>> +	}
>> +
>> +	ret = i2c_master_recv(client, val, 1);
>> +	if (ret < 0)
>> +		dev_dbg(&client->dev, "%s: i2c read error, reg: %x\n",
>> +				__func__, reg);
>> +
>> +	return ret;
>> +
> 
> Please remove the empty line above.
> 

Ok.

>> +}
>> +
>> +static int ov5647_write_array(struct v4l2_subdev *sd,
>> +				struct regval_list *regs, int array_size)
>> +{
>> +	int i = 0, ret;
> 
> Assignment of 'i' on declaration is not needed, please remove.
> 

Ok.

>> +
>> +	for (i = 0; i < array_size; i++) {
>> +		ret = ov5647_write(sd, regs[i].addr, regs[i].data);
>> +		if (ret < 0)
>> +			return ret;
>> +	}
>> +
>> +	return 0;
>> +}
>> +
>> +static int ov5647_set_virtual_channel(struct v4l2_subdev *sd, int channel)
>> +{
>> +	u8 channel_id;
>> +	int ret;
>> +
>> +	ret = ov5647_read(sd, 0x4814, &channel_id);
>> +	if (ret < 0)
>> +		return ret;
>> +
>> +	channel_id &= ~(3 << 6);
>> +	return ov5647_write(sd, 0x4814, channel_id | (channel << 6));
>> +}
>> +
>> +static int ov5647_stream_on(struct v4l2_subdev *sd)
>> +{
>> +	struct i2c_client *client = v4l2_get_subdevdata(sd);
>> +
>> +	ov5647_write(sd, 0x4202, 0x00);
> 
> Should you add a check of the returned value?
> 

I'll add it.

>> +
>> +	dev_dbg(&client->dev, "Stream on");
> 
> I would suggest to remove dev_dbg(), because ftrace will report to a user,
> when this function is called.
> 
> Also dev_dbg() in the middle of two I2C transfers in a row looks as being
> placed improperly.
> 

I'll remove it.

>> +
>> +	return ov5647_write(sd, 0x300D, 0x00);
>> +}
>> +
>> +static int ov5647_stream_off(struct v4l2_subdev *sd)
>> +{
>> +	struct i2c_client *client = v4l2_get_subdevdata(sd);
>> +
>> +	ov5647_write(sd, 0x4202, 0x0f);
> 
> Should you add a check of the returned value?
> 

I'll add it.

>> +
>> +	dev_dbg(&client->dev, "Stream off");
> 
> I would suggest to remove dev_dbg(), because ftrace will report to a user,
> when this function is called.
> 
> Also dev_dbg() in the middle of two I2C transfers in a row looks as being
> placed improperly.
> 

I'll remove it.

>> +
>> +	return ov5647_write(sd, 0x300D, 0x01);
>> +}
>> +
>> +static int set_sw_standby(struct v4l2_subdev *sd, bool standby)
>> +{
>> +	int ret;
>> +	u8 rdval;
>> +
>> +	ret = ov5647_read(sd, 0x0100, &rdval);
>> +	if (ret < 0)
>> +		return ret;
>> +
>> +	if (standby)
>> +		rdval &= ~0x01;
>> +	else
>> +		rdval |= 0x01;
>> +
>> +	return ov5647_write(sd, 0x0100, rdval);
>> +}
>> +
>> +static int __sensor_init(struct v4l2_subdev *sd)
>> +{
>> +	int ret;
>> +	u8 resetval;
>> +	u8 rdval;
> 
> It could be possible to put declarations of 'resetval' and 'rdval' on the same line.
> 

Sure.

>> +	struct i2c_client *client = v4l2_get_subdevdata(sd);
>> +
>> +	dev_dbg(&client->dev, "sensor init\n");
>> +
>> +	ret = ov5647_read(sd, 0x0100, &rdval);
>> +	if (ret < 0)
>> +		return ret;
>> +
>> +	ret = ov5647_write_array(sd, ov5647_640x480,
>> +					ARRAY_SIZE(ov5647_640x480));
>> +	if (ret < 0) {
>> +		dev_err(&client->dev, "write sensor default regs error\n");
>> +		return ret;
>> +	}
>> +
>> +	ret = ov5647_set_virtual_channel(sd, 0);
>> +	if (ret < 0)
>> +		return ret;
>> +
>> +	ret = ov5647_read(sd, 0x0100, &resetval);
>> +	if (ret < 0)
>> +		return ret;
>> +
>> +	if (!(resetval & 0x01)) {
>> +		dev_err(&client->dev, "Device was in SW standby");
>> +		ret = ov5647_write(sd, 0x0100, 0x01);
>> +		if (ret < 0)
>> +			return ret;
>> +	}
>> +
>> +	return ov5647_write(sd, 0x4800, 0x04);
>> +}
>> +
>> +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 && !ov5647->power_count)	{
>> +		dev_dbg(&client->dev, "OV5647 power on\n");
>> +
>> +		clk_set_rate(ov5647->xclk, ov5647->xclk_freq);
> 
> Now clk_set_rate() is redundant, please remove it.
> 
> If once it is needed again, please move it to the .probe function, so
> it is called only once in the runtime.
> 

Ok. I'll remove it for now.

>> +
>> +		ret = clk_prepare_enable(ov5647->xclk);
> 
> I wonder would it be possible to unload the driver or to unbind the device
> and leave the clock unintentionally enabled? If yes, then this is a bug.
> 

You're saying that if the driver was unloaded and the clock was left enabled
when the driver was loaded again this line would cause an error?

Should I disable the clock when the driver is removed?

>> +		if (ret < 0) {
>> +			dev_err(&client->dev, "clk prepare enable failed\n");
>> +			goto out;
>> +		}
>> +
>> +		ret = ov5647_write_array(sd, sensor_oe_enable_regs,
>> +				ARRAY_SIZE(sensor_oe_enable_regs));
>> +		if (ret < 0) {
>> +			clk_disable_unprepare(ov5647->xclk);
>> +			dev_err(&client->dev,
>> +				"write sensor_oe_enable_regs error\n");
>> +			goto out;
>> +		}
>> +
>> +		ret = __sensor_init(sd);
>> +		if (ret < 0) {
>> +			clk_disable_unprepare(ov5647->xclk);
>> +			dev_err(&client->dev,
>> +				"Camera not available, check Power\n");
>> +			goto out;
>> +		}
>> +	} else if (!on && ov5647->power_count == 1) {
>> +		dev_dbg(&client->dev, "OV5647 power off\n");
>> +
>> +		dev_dbg(&client->dev, "disable oe\n");
> 
> One of two dev_dbg()'s above is apparently redundant.
> 

I'll remove one.

>> +		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");
>> +
>> +		clk_disable_unprepare(ov5647->xclk);
>> +	}
>> +
>> +	/* Update the power count. */
>> +	ov5647->power_count += on ? 1 : -1;
>> +	WARN_ON(ov5647->power_count < 0);
>> +
>> +out:
>> +	mutex_unlock(&ov5647->lock);
>> +
>> +	return ret;
>> +}
>> +
> 
> [snip]
> 
>> +
>> +static int ov5647_probe(struct i2c_client *client,
>> +			const struct i2c_device_id *id)
>> +{
>> +	struct device *dev = &client->dev;
>> +	struct ov5647 *sensor;
>> +	int ret;
>> +	struct v4l2_subdev *sd;
>> +
>> +	sensor = devm_kzalloc(dev, sizeof(*sensor), GFP_KERNEL);
>> +	if (sensor == NULL)
> 
> if (!sensor) is a bit shorter.
> 

I'll change it.

>> +		return -ENOMEM;
>> +
>> +	/* get system clock (xclk) */
>> +	sensor->xclk = devm_clk_get(dev, "xclk");
>> +	if (IS_ERR(sensor->xclk)) {
>> +		dev_err(dev, "could not get xclk");
>> +		return PTR_ERR(sensor->xclk);
>> +	}
>> +
>> +	sensor->xclk_freq = clk_get_rate(sensor->xclk);
>> +	if (sensor->xclk_freq != 25000000) {
> 
> A comment in "struct ov5647" declaration says about 30MHz, which one is correct?
> 

25 MHz is the correct one.

>> +		dev_err(dev, "Unsupported clock frequency: %u\n",
>> +			sensor->xclk_freq);
>> +		return -EINVAL;
>> +	}
>> +
>> +	mutex_init(&sensor->lock);
>> +
>> +	sd = &sensor->sd;
>> +	v4l2_i2c_subdev_init(sd, client, &subdev_ops);
>> +	sensor->sd.flags |= V4L2_SUBDEV_FL_HAS_DEVNODE;
>> +
>> +	sensor->pad.flags = MEDIA_PAD_FL_SOURCE;
>> +	sd->entity.function = MEDIA_ENT_F_CAM_SENSOR;
>> +	ret = media_entity_pads_init(&sd->entity, 1, &sensor->pad);
>> +	if (ret < 0)
>> +		goto mutex_remove;
>> +
>> +	ret = ov5647_detect(sd);
>> +	if (ret < 0)
>> +		goto error;
>> +
>> +	ret = v4l2_async_register_subdev(sd);
>> +	if (ret < 0)
>> +		goto error;
>> +
>> +	dev_dbg(&client->dev, "OmniVision OV5647 camera driver probed\n");
>> +	return 0;
>> +error:
>> +	media_entity_cleanup(&sd->entity);
>> +mutex_remove:
>> +	mutex_destroy(&sensor->lock);
>> +	return ret;
>> +}
>> +
> 
> [snip]
> 
> The driver looks good in general IMO.
> 
> --
> With best wishes,
> Vladimir
> 

-- 
Best Regards

Ramiro Oliveira
Ramiro.Oliveira@synopsys.com

  reply	other threads:[~2017-02-21 16:42 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-17 13:14 [PATCH v9 0/2] Add support for Omnivision OV5647 Ramiro Oliveira
2017-02-17 13:14 ` [PATCH v9 1/2] Add OV5647 device tree documentation Ramiro Oliveira
     [not found]   ` <5a93352142495528dd56d5e281a8ed8ad6404a05.1487334912.git.roliveir-HKixBCOQz3hWk0Htik3J/w@public.gmane.org>
2017-02-21 11:57     ` Sakari Ailus
2017-02-21 14:30       ` Ramiro Oliveira
     [not found]         ` <3d0b775a-e1de-d957-de72-7751e2c59aea-HKixBCOQz3hWk0Htik3J/w@public.gmane.org>
2017-02-21 14:40           ` Sakari Ailus
2017-02-21 15:58     ` Vladimir Zapolskiy
     [not found]       ` <dd33c7bc-e6f7-c234-c3c6-6cc4c7353c68-nmGgyN9QBj3QT0dZR+AlfA@public.gmane.org>
2017-02-21 20:13         ` Ramiro Oliveira
2017-02-21 20:48           ` Vladimir Zapolskiy
     [not found]             ` <cc6c914e-c3e7-7703-0405-104e701610cf-nmGgyN9QBj3QT0dZR+AlfA@public.gmane.org>
2017-02-21 21:48               ` Sakari Ailus
     [not found]                 ` <20170221214813.GN16975-S+BSfZ9RZZmRSg0ZkenSGLdO1Tsj/99ntUK59QYPAWc@public.gmane.org>
2017-02-21 22:37                   ` Vladimir Zapolskiy
     [not found]                     ` <1b7e2802-dda1-0372-8738-17655dd8ca69-nmGgyN9QBj3QT0dZR+AlfA@public.gmane.org>
2017-02-22 10:57                       ` Ramiro Oliveira
     [not found]                         ` <0c251686-6f95-2f54-3d9c-9a97fa8dd947-HKixBCOQz3hWk0Htik3J/w@public.gmane.org>
2017-02-22 11:39                           ` Vladimir Zapolskiy
     [not found]                             ` <eef5a0b8-c757-0af7-b856-8c29cf92134c-nmGgyN9QBj3QT0dZR+AlfA@public.gmane.org>
2017-02-22 14:39                               ` Ramiro Oliveira
2017-02-25 14:50                       ` Sakari Ailus
     [not found]                         ` <20170225145053.puqkcrntnhmcvla4-5TBSa+ebGXJ82hYKe6nXyg@public.gmane.org>
2017-02-25 14:55                           ` Sakari Ailus
2017-02-17 13:14 ` [PATCH v9 2/2] Add support for OV5647 sensor Ramiro Oliveira
     [not found]   ` <412e51e695630281d2084a77c0329fd273ea00d7.1487334912.git.roliveir-HKixBCOQz3hWk0Htik3J/w@public.gmane.org>
2017-02-21 12:09     ` Sakari Ailus
     [not found]       ` <20170221120914.GG16975-S+BSfZ9RZZmRSg0ZkenSGLdO1Tsj/99ntUK59QYPAWc@public.gmane.org>
2017-02-21 14:49         ` Ramiro Oliveira
2017-02-21 14:58           ` Sakari Ailus
2017-02-21 15:54     ` Vladimir Zapolskiy
2017-02-21 16:42       ` Ramiro Oliveira [this message]
     [not found]         ` <c39814c2-20a0-db08-38c1-ce95ccc49738-HKixBCOQz3hWk0Htik3J/w@public.gmane.org>
2017-02-21 20:36           ` Vladimir Zapolskiy
     [not found]             ` <21847f33-901c-7d26-15d8-6b92f10c8b15-nmGgyN9QBj3QT0dZR+AlfA@public.gmane.org>
2017-02-22 10:51               ` Ramiro Oliveira
     [not found]                 ` <94622194-78dc-ad6f-3f6e-4d7df0ac5383-HKixBCOQz3hWk0Htik3J/w@public.gmane.org>
2017-02-22 11:43                   ` Vladimir Zapolskiy

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=c39814c2-20a0-db08-38c1-ce95ccc49738@synopsys.com \
    --to=ramiro.oliveira@synopsys.com \
    --cc=CARLOS.PALMINHA@synopsys.com \
    --cc=davem@davemloft.net \
    --cc=devicetree@vger.kernel.org \
    --cc=geert+renesas@glider.be \
    --cc=gregkh@linuxfoundation.org \
    --cc=hans.verkuil@cisco.com \
    --cc=ivo.g.dimitrov.75@gmail.com \
    --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 \
    --cc=vladimir_zapolskiy@mentor.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;
as well as URLs for NNTP newsgroup(s).