From: Hugues FRUCHET <hugues.fruchet@st.com>
To: Steve Longerbeam <steve_longerbeam@mentor.com>,
Steve Longerbeam <slongerbeam@gmail.com>,
Sakari Ailus <sakari.ailus@iki.fi>,
Hans Verkuil <hverkuil@xs4all.nl>,
Mauro Carvalho Chehab <mchehab@kernel.org>
Cc: "linux-media@vger.kernel.org" <linux-media@vger.kernel.org>,
"Benjamin Gaignard" <benjamin.gaignard@linaro.org>
Subject: Re: [PATCH v2 2/4] media: ov5640: check chip id
Date: Wed, 6 Dec 2017 09:47:18 +0000 [thread overview]
Message-ID: <84e77f25-da1a-44df-e624-54f7a981d2e3@st.com> (raw)
In-Reply-To: <fcf7a6e3-e4b7-bf45-feca-8b9fa5b08716@mentor.com>
Hi Steve,
thanks for review, comments below.
On 12/03/2017 10:34 PM, Steve Longerbeam wrote:
>
>
> On 11/29/2017 09:11 AM, Hugues Fruchet wrote:
>> Verify that chip identifier is correct before starting streaming
>>
>> Signed-off-by: Hugues Fruchet <hugues.fruchet@st.com>
>> ---
>> drivers/media/i2c/ov5640.c | 30 +++++++++++++++++++++++++++++-
>> 1 file changed, 29 insertions(+), 1 deletion(-)
>>
>> diff --git a/drivers/media/i2c/ov5640.c b/drivers/media/i2c/ov5640.c
>> index 61071f5..a576d11 100644
>> --- a/drivers/media/i2c/ov5640.c
>> +++ b/drivers/media/i2c/ov5640.c
>> @@ -34,7 +34,8 @@
>> #define OV5640_DEFAULT_SLAVE_ID 0x3c
>> -#define OV5640_REG_CHIP_ID 0x300a
>> +#define OV5640_REG_CHIP_ID_HIGH 0x300a
>> +#define OV5640_REG_CHIP_ID_LOW 0x300b
>
> There is no need to separate low and high byte addresses.
> See below.
>
>> #define OV5640_REG_PAD_OUTPUT00 0x3019
>> #define OV5640_REG_SC_PLL_CTRL0 0x3034
>> #define OV5640_REG_SC_PLL_CTRL1 0x3035
>> @@ -926,6 +927,29 @@ static int ov5640_load_regs(struct ov5640_dev
>> *sensor,
>> return ret;
>> }
>> +static int ov5640_check_chip_id(struct ov5640_dev *sensor)
>> +{
>> + struct i2c_client *client = sensor->i2c_client;
>> + int ret;
>> + u8 chip_id_h, chip_id_l;
>> +
>> + ret = ov5640_read_reg(sensor, OV5640_REG_CHIP_ID_HIGH, &chip_id_h);
>> + if (ret)
>> + return ret;
>> +
>> + ret = ov5640_read_reg(sensor, OV5640_REG_CHIP_ID_LOW, &chip_id_l);
>> + if (ret)
>> + return ret;
>> +
>> + if (!(chip_id_h == 0x56 && chip_id_l == 0x40)) {
>> + dev_err(&client->dev, "%s: wrong chip identifier, expected
>> 0x5640, got 0x%x%x\n",
>> + __func__, chip_id_h, chip_id_l);
>> + return -EINVAL;
>> + }
>> +
>
> This should all be be replaced by:
>
> u16 chip_id;
>
> ret = ov5640_read_reg16(sensor, OV5640_REG_CHIP_ID, &chip_id);
>
> etc.
>
Done, thanks.
>> + return 0;
>> +}
>> +
>> /* read exposure, in number of line periods */
>> static int ov5640_get_exposure(struct ov5640_dev *sensor)
>> {
>> @@ -1562,6 +1586,10 @@ static int ov5640_set_power(struct ov5640_dev
>> *sensor, bool on)
>> ov5640_reset(sensor);
>> ov5640_power(sensor, true);
>> + ret = ov5640_check_chip_id(sensor);
>> + if (ret)
>> + goto power_off;
>> +
>> ret = ov5640_init_slave_id(sensor);
>> if (ret)
>> goto power_off;
>
Best regards,
Hugues.
next prev parent reply other threads:[~2017-12-06 9:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-29 17:11 [PATCH v2 0/4] Add OV5640 parallel interface and RGB565/YUYV support Hugues Fruchet
2017-11-29 17:11 ` [PATCH v2 1/4] media: ov5640: switch to gpiod_set_value_cansleep() Hugues Fruchet
2017-11-29 17:11 ` [PATCH v2 2/4] media: ov5640: check chip id Hugues Fruchet
2017-11-30 19:07 ` Fabio Estevam
2017-12-06 10:02 ` Hugues FRUCHET
2017-12-03 21:34 ` Steve Longerbeam
2017-12-06 9:47 ` Hugues FRUCHET [this message]
2017-11-29 17:11 ` [PATCH v2 3/4] media: ov5640: add support of DVP parallel interface Hugues Fruchet
2017-11-30 19:09 ` Fabio Estevam
2017-12-06 10:04 ` Hugues FRUCHET
2017-12-03 21:58 ` Steve Longerbeam
2017-12-06 10:01 ` Hugues FRUCHET
2017-11-29 17:11 ` [PATCH v2 4/4] media: ov5640: add support of RGB565 and YUYV formats Hugues Fruchet
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=84e77f25-da1a-44df-e624-54f7a981d2e3@st.com \
--to=hugues.fruchet@st.com \
--cc=benjamin.gaignard@linaro.org \
--cc=hverkuil@xs4all.nl \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=sakari.ailus@iki.fi \
--cc=slongerbeam@gmail.com \
--cc=steve_longerbeam@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