From: Bing Bu Cao <bingbu.cao@linux.intel.com>
To: Tomasz Figa <tfiga@chromium.org>, Cao Bing Bu <bingbu.cao@intel.com>
Cc: Linux Media Mailing List <linux-media@vger.kernel.org>,
Sakari Ailus <sakari.ailus@linux.intel.com>,
"Mani, Rajmohan" <rajmohan.mani@intel.com>,
"Qiu, Tian Shu" <tian.shu.qiu@intel.com>,
"Zheng, Jian Xu" <jian.xu.zheng@intel.com>
Subject: Re: [PATCH v5] media: add imx319 camera sensor driver
Date: Fri, 21 Sep 2018 10:31:54 +0800 [thread overview]
Message-ID: <c2998a8f-90bf-e5c8-e45d-e52d2bebcca0@linux.intel.com> (raw)
In-Reply-To: <CAAFQd5Dp8kp6fi8bXr6jODO0Cr4Kqu5L0eSXudsrOkHK6cKdjg@mail.gmail.com>
On 09/18/2018 05:49 PM, Tomasz Figa wrote:
> Hi Bingbu,
>
> On Mon, Sep 17, 2018 at 2:53 PM <bingbu.cao@intel.com> wrote:
>> From: Bingbu Cao <bingbu.cao@intel.com>
>>
>> Add a v4l2 sub-device driver for the Sony imx319 image sensor.
>> This is a camera sensor using the i2c bus for control and the
>> csi-2 bus for data.
> Please see my comments inline. Also, I'd appreciate being CCed on
> related work in the future.
Ack.
Sorry, will add you into the cc-list.
>
> [snip]
>> +
>> +static const char * const imx319_test_pattern_menu[] = {
>> + "Disabled",
>> + "100% color bars",
>> + "Solid color",
>> + "Fade to gray color bars",
>> + "PN9"
>> +};
>> +
>> +static const int imx319_test_pattern_val[] = {
>> + IMX319_TEST_PATTERN_DISABLED,
>> + IMX319_TEST_PATTERN_COLOR_BARS,
>> + IMX319_TEST_PATTERN_SOLID_COLOR,
>> + IMX319_TEST_PATTERN_GRAY_COLOR_BARS,
>> + IMX319_TEST_PATTERN_PN9,
>> +};
> This array is not needed. All the entries are equal to corresponding
> indices, i.e. the array is equivalent to { 0, 1, 2, 3, 4 }. We can use
> ctrl->val directly.
Ack.
> [snip]
>
>> +/* Write a list of registers */
>> +static int imx319_write_regs(struct imx319 *imx319,
>> + const struct imx319_reg *regs, u32 len)
>> +{
>> + struct i2c_client *client = v4l2_get_subdevdata(&imx319->sd);
>> + int ret;
>> + u32 i;
>> +
>> + for (i = 0; i < len; i++) {
>> + ret = imx319_write_reg(imx319, regs[i].address, 1, regs[i].val);
>> + if (ret) {
>> + dev_err_ratelimited(&client->dev,
>> +
> Hmm, the message is clipped here. Let me see if it's something with my
> email client...
The code here:
1827 for (i = 0; i < len; i++) {
1828 ret = imx319_write_reg(imx319, regs[i].address, 1, regs[i].val);
1829 if (ret) {
1830 dev_err_ratelimited(&client->dev,
1831 "write reg 0x%4.4x return err %d",
1832 regs[i].address, ret);
1833 return ret;
1834 }
1835 } Same as the code shown on your client?
>
> Best regards,
> Tomasz
>
next prev parent reply other threads:[~2018-09-21 8:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-17 5:57 [PATCH v5] media: add imx319 camera sensor driver bingbu.cao
2018-09-17 10:52 ` kbuild test robot
2018-09-17 11:34 ` Sakari Ailus
2018-09-21 2:07 ` Bing Bu Cao
2018-09-21 7:20 ` Bing Bu Cao
2018-09-21 7:41 ` Sakari Ailus
2018-09-21 8:47 ` Bing Bu Cao
2018-09-18 9:49 ` Tomasz Figa
2018-09-21 2:31 ` Bing Bu Cao [this message]
2018-09-21 7:53 ` Tomasz Figa
2018-09-19 4:11 ` Tomasz Figa
2018-09-21 2:39 ` Bing Bu Cao
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=c2998a8f-90bf-e5c8-e45d-e52d2bebcca0@linux.intel.com \
--to=bingbu.cao@linux.intel.com \
--cc=bingbu.cao@intel.com \
--cc=jian.xu.zheng@intel.com \
--cc=linux-media@vger.kernel.org \
--cc=rajmohan.mani@intel.com \
--cc=sakari.ailus@linux.intel.com \
--cc=tfiga@chromium.org \
--cc=tian.shu.qiu@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.