public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: "Nirujogi, Pratap" <pnirujog@amd.com>
To: Krzysztof Kozlowski <krzk@kernel.org>,
	Pratap Nirujogi <pratap.nirujogi@amd.com>,
	mchehab@kernel.org, sakari.ailus@linux.intel.com,
	hverkuil@xs4all.nl, laurent.pinchart@ideasonboard.com,
	dave.stevenson@raspberrypi.com, dan.carpenter@linaro.org
Cc: linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
	benjamin.chan@amd.com, bin.du@amd.com, grosikop@amd.com,
	king.li@amd.com, dantony@amd.com,
	Venkata Narendra Kumar Gutta <vengutta@amd.com>
Subject: Re: [PATCH v2] media: i2c: Add OV05C10 camera sensor driver
Date: Mon, 31 Mar 2025 15:19:20 -0400	[thread overview]
Message-ID: <2cce157d-eaba-44c1-89d1-7e5088ee361f@amd.com> (raw)
In-Reply-To: <e94d3ba7-78ad-453a-86c0-a71662e02922@kernel.org>

Hi Krzysztof,

Thanks for the review.

Thanks,
Pratap

On 3/29/2025 12:30 AM, Krzysztof Kozlowski wrote:
> Caution: This message originated from an External Source. Use proper caution when opening attachments, clicking links, or responding.
> 
> 
> On 28/03/2025 22:42, Pratap Nirujogi wrote:
>> +static int ov05c10_probe(struct i2c_client *client)
>> +{
>> +     struct ov05c10 *ov05c10;
>> +     u32 refclk;
>> +     int ret;
>> +
>> +     ov05c10 = devm_kzalloc(&client->dev, sizeof(*ov05c10), GFP_KERNEL);
>> +     if (!ov05c10)
>> +             return -ENOMEM;
>> +
>> +     struct fwnode_handle *fwnode = dev_fwnode(&client->dev);
>> +
>> +     ret = fwnode_property_read_u32(fwnode, "refclk", &refclk);
> 
> Use existing properties, like clock-frequency. refclk means this is the
> clock, not it's frequency.
> 
sure, will replace "refclk" with "clock-frequency" variable in the next 
V3 patch.

>> +     if (ret)
>> +             return  dev_err_probe(&client->dev, -EINVAL,
>> +                                   "fail to get refclk\n");
>> +     if (refclk != OV05C10_REF_CLK)
>> +             return dev_err_probe(&client->dev, -EINVAL,
>> +                                  "failbad refclk %u, %lu expected\n",
>> +                                  refclk, OV05C10_REF_CLK);
>> +
>> +     ret = ov05c10_parse_endpoint(&client->dev, fwnode);
>> +     if (ret)
>> +             return dev_err_probe(&client->dev, -EINVAL,
>> +                                  "fail to parse endpoint\n");
>> +
>> +     ov05c10->enable_gpio = devm_gpiod_get(&client->dev, "sensor0_enable",
>> +                                           GPIOD_OUT_LOW);
> 
> Nothing improved and you did not bothered to wait for my feedback. You
> just sent v2.
> 
sorry, I should have waited for your feedback before submitting V2. I 
will use the suggested name "enable" in the next V3 submission.

> There is no second GPIO, otherwise would be present here.
> 
I rechecked both GPIOs. Only one is relevant for sensor driver and other 
one is for the ISP driver. Sorry for the confusion caused.

> NAK.
> 
> 
> 
> Best regards,
> Krzysztof


      reply	other threads:[~2025-03-31 19:19 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <MhUYQD7uWnfZQAPq7VslFWPHOmx2B2UfAIpbMhLq1-7GC_i5bI2hhns_-ov_AAVpEH_VmDDFYkS5aOKBwnY61g==@protonmail.internalid>
2025-03-28 21:42 ` [PATCH v2] media: i2c: Add OV05C10 camera sensor driver Pratap Nirujogi
2025-03-29  1:18   ` Bryan O'Donoghue
2025-03-31 19:17     ` Nirujogi, Pratap
2025-04-02  1:20       ` Laurent Pinchart
2025-04-02 22:04         ` Nirujogi, Pratap
2025-05-06  7:45         ` Sakari Ailus
2025-05-06 11:29           ` Hans de Goede
2025-05-07 20:25             ` Nirujogi, Pratap
2025-04-08 21:09       ` Nirujogi, Pratap
2025-03-29  4:30   ` Krzysztof Kozlowski
2025-03-31 19:19     ` Nirujogi, Pratap [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=2cce157d-eaba-44c1-89d1-7e5088ee361f@amd.com \
    --to=pnirujog@amd.com \
    --cc=benjamin.chan@amd.com \
    --cc=bin.du@amd.com \
    --cc=dan.carpenter@linaro.org \
    --cc=dantony@amd.com \
    --cc=dave.stevenson@raspberrypi.com \
    --cc=grosikop@amd.com \
    --cc=hverkuil@xs4all.nl \
    --cc=king.li@amd.com \
    --cc=krzk@kernel.org \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --cc=pratap.nirujogi@amd.com \
    --cc=sakari.ailus@linux.intel.com \
    --cc=vengutta@amd.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