Re: [PATCH v2 1/2] MT9P031: Add support for Aptina mt9p031 sensor.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi, Laurent, Guennadi,
thank you for your review. I've already fixed most of the issues.

On 23 May 2011 11:03, Laurent Pinchart
<laurent.pinchart@xxxxxxxxxxxxxxxx> wrote:
> Hi Guennadi and Javier,
>
> On Saturday 21 May 2011 17:29:18 Guennadi Liakhovetski wrote:
>> On Fri, 20 May 2011, Javier Martin wrote:
>
> [snip]
>
>> > diff --git a/drivers/media/video/mt9p031.c
>> > b/drivers/media/video/mt9p031.c new file mode 100644
>> > index 0000000..e406b64
>> > --- /dev/null
>> > +++ b/drivers/media/video/mt9p031.c
>
> [snip]
>> > +}
>> > +
>> > +static int mt9p031_power_on(struct mt9p031 *mt9p031)
>> > +{
>> > +   int ret;
>> > +
>> > +   /* turn on VDD_IO */
>> > +   ret = regulator_enable(mt9p031->reg_2v8);
>> > +   if (ret) {
>> > +           pr_err("Failed to enable 2.8v regulator: %d\n", ret);
>>
>> dev_err()
>>
>> > +           return ret;
>> > +   }
>> > +   if (mt9p031->pdata->set_xclk)
>> > +           mt9p031->pdata->set_xclk(&mt9p031->subdev, 54000000);
>
> Can you make 54000000 a #define at the beginning of the file ?
>
> You should soft-reset the chip here by calling mt9p031_reset().
>

If I do this, I would be force to cache some registers and restart
them. I've tried to do this but I don't know what is failing that
there are some artifacts consisting on horizontal black lines in the
image.
Please, let me push this to mainline without this feature as a first
step, since I'll have to spend some assigned to another project.

[snip]
>> > + */
>> > +static int mt9p031_video_probe(struct i2c_client *client)
>> > +{
>> > +   s32 data;
>> > +   int ret;
>> > +
>> > +   /* Read out the chip version register */
>> > +   data = reg_read(client, MT9P031_CHIP_VERSION);
>> > +   if (data != MT9P031_CHIP_VERSION_VALUE) {
>> > +           dev_err(&client->dev,
>> > +                   "No MT9P031 chip detected, register read %x\n", data);
>> > +           return -ENODEV;
>> > +   }
>> > +
>> > +   dev_info(&client->dev, "Detected a MT9P031 chip ID %x\n", data);
>> > +
>> > +   ret = mt9p031_reset(client);
>> > +   if (ret < 0)
>> > +           dev_err(&client->dev, "Failed to initialise the camera\n");
>
> If you move the soft-reset operation to mt9p031_power_on(), you don't need to
> call it here.
>

The reason for this is the same as before. I haven't still been able
to success on restarting registers and getting everything to work
fine.
It would be great if you allowed me to push this as it is as an
intermediate step.

[snip]
>
>> > +   mt9p031->rect.width     = MT9P031_MAX_WIDTH;
>> > +   mt9p031->rect.height    = MT9P031_MAX_HEIGHT;
>> > +
>> > +   mt9p031->format.code = V4L2_MBUS_FMT_SGRBG12_1X12;
>> > +
>> > +   mt9p031->format.width = MT9P031_MAX_WIDTH;
>> > +   mt9p031->format.height = MT9P031_MAX_HEIGHT;
>> > +   mt9p031->format.field = V4L2_FIELD_NONE;
>> > +   mt9p031->format.colorspace = V4L2_COLORSPACE_SRGB;
>> > +
>> > +   mt9p031->xskip = 1;
>> > +   mt9p031->yskip = 1;
>> > +
>> > +   mt9p031->reg_1v8 = regulator_get(NULL, "cam_1v8");
>> > +   if (IS_ERR(mt9p031->reg_1v8)) {
>> > +           ret = PTR_ERR(mt9p031->reg_1v8);
>> > +           pr_err("Failed 1.8v regulator: %d\n", ret);
>>
>> dev_err()
>>
>> > +           goto e1v8;
>> > +   }
>
> The driver can be used with boards where either or both of the 1.8V and 2.8V
> supplies are always on, thus not connected to any regulator. I'm not sure how
> that's usually handled, if board code should define an "always-on" power
> supply, or if the driver shouldn't fail when no regulator is present. In any
> case, this must be handled.
>

I think board code should define an "always-on" power supply.

>> > +
>> > +   mt9p031->reg_2v8 = regulator_get(NULL, "cam_2v8");
>> > +   if (IS_ERR(mt9p031->reg_2v8)) {
>> > +           ret = PTR_ERR(mt9p031->reg_2v8);
>> > +           pr_err("Failed 2.8v regulator: %d\n", ret);
>>
>> ditto
>>
>> > +           goto e2v8;
>> > +   }
>> > +   /* turn on core */
>> > +   ret = regulator_enable(mt9p031->reg_1v8);
>> > +   if (ret) {
>> > +           pr_err("Failed to enable 1.8v regulator: %d\n", ret);
>>
>> ditto
>>
>> > +           goto e1v8en;
>> > +   }
>> > +   return 0;
>
> Why do you leave core power on at the end of probe() ? You should only turn it
> on when needed.
>

Just as I said, because restarting registers does not work yet.





-- 
Javier Martin
Vista Silicon S.L.
CDTUC - FASE C - Oficina S-345
Avda de los Castros s/n
39005- Santander. Cantabria. Spain
+34 942 25 32 60
www.vista-silicon.com
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Input]     [Video for Linux]     [Gstreamer Embedded]     [Mplayer Users]     [Linux USB Devel]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Yosemite Backpacking]
  Powered by Linux