From: Krzysztof Kozlowski <krzk@kernel.org>
To: Hardevsinh Palaniya <hardevsinh.palaniya@siliconsignals.io>,
"sakari.ailus@linux.intel.com" <sakari.ailus@linux.intel.com>,
"andriy.shevchenko@linux.intel.com"
<andriy.shevchenko@linux.intel.com>,
"krzk+dt@kernel.org" <krzk+dt@kernel.org>
Cc: "Himanshu Bhavani" <himanshu.bhavani@siliconsignals.io>,
"Mauro Carvalho Chehab" <mchehab@kernel.org>,
"Rob Herring" <robh@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Hans Verkuil" <hverkuil@xs4all.nl>,
"André Apitzsch" <git@apitzsch.eu>,
"Hans de Goede" <hansg@kernel.org>,
"Ricardo Ribalda" <ribalda@chromium.org>,
"Heimir Thor Sverrisson" <heimir.sverrisson@gmail.com>,
"Matthias Fend" <matthias.fend@emfend.at>,
"Benjamin Mugnier" <benjamin.mugnier@foss.st.com>,
"Jingjing Xiong" <jingjing.xiong@intel.com>,
"Sylvain Petinot" <sylvain.petinot@foss.st.com>,
"Dongcheng Yan" <dongcheng.yan@intel.com>,
"Arnd Bergmann" <arnd@arndb.de>,
"Bryan O'Donoghue" <bryan.odonoghue@linaro.org>,
"linux-media@vger.kernel.org" <linux-media@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 2/2] media: i2c: add ov2735 image sensor driver
Date: Tue, 8 Jul 2025 15:26:13 +0200 [thread overview]
Message-ID: <550105c6-1520-4f2b-ae4f-0f135a8f3b5f@kernel.org> (raw)
In-Reply-To: <PN3P287MB35199F4D8EA9F384660A337DFF4EA@PN3P287MB3519.INDP287.PROD.OUTLOOK.COM>
On 08/07/2025 13:28, Hardevsinh Palaniya wrote:
>> On 08/07/2025 12:25, Hardevsinh Palaniya wrote:
>>> +
>>> +static const struct v4l2_subdev_ops ov2735_subdev_ops = {
>>> + .video = &ov2735_video_ops,
>>> + .pad = &ov2735_pad_ops,
>>> +};
>>> +
>>> +static const struct v4l2_subdev_internal_ops ov2735_internal_ops = {
>>> + .init_state = ov2735_init_state,
>>> +};
>>> +
>>> +static int ov2735_power_on(struct device *dev)
>>> +{
>>> + struct v4l2_subdev *sd = dev_get_drvdata(dev);
>>> + struct ov2735 *ov2735 = to_ov2735(sd);
>>> + unsigned long delay_us;
>>> + int ret;
>>> +
>>> + gpiod_set_value_cansleep(ov2735->pwdn_gpio, 0);
>>
>> So you power up here...
>>
>>> + fsleep(3000);
>>> +
>>> + ret = regulator_bulk_enable(ARRAY_SIZE(ov2735_supply_name),
>>> + ov2735->supplies);
>>> + if (ret) {
>>> + dev_err(ov2735->dev, "failed to enable regulators\n");
>>> + return ret;
>>> + }
>>> +
>>> + gpiod_set_value_cansleep(ov2735->pwdn_gpio, 1);
>>
>> And here you power down your device. This makes no sense... unless this
>> is not a power down GPIO.
>
> In Datasheet
> Power-up sequence:
>
> |--------------------------------------
> avdd ----|
> <-t1->
> |--------------------------------
> dovdd ---------|
> <-T2->
> |--------------------------
> dvdd ------------------|
> <-T3->
> |---------------------|
> pwdn -----| |-------------------
So that is not really a typical power down pin and this should be
explained clearly in property description. It rather feels like power-on
pin, which you need to pull for some time to boot the process and later
the supplies are keeping it on.
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-07-08 13:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-08 10:25 [PATCH v2 0/2] media: i2c: Add ov2735 camera sensor driver Hardevsinh Palaniya
2025-07-08 10:25 ` [PATCH v2 1/2] dt-bindings: media: i2c: Add ov2735 sensor Hardevsinh Palaniya
2025-07-08 10:41 ` Krzysztof Kozlowski
2025-07-10 7:18 ` Hardevsinh Palaniya
2025-07-08 10:25 ` [PATCH v2 2/2] media: i2c: add ov2735 image sensor driver Hardevsinh Palaniya
2025-07-08 10:42 ` Krzysztof Kozlowski
2025-07-08 11:28 ` Hardevsinh Palaniya
2025-07-08 13:26 ` Krzysztof Kozlowski [this message]
2025-07-08 11:40 ` Kieran Bingham
2025-07-08 13:25 ` Dave Stevenson
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=550105c6-1520-4f2b-ae4f-0f135a8f3b5f@kernel.org \
--to=krzk@kernel.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=arnd@arndb.de \
--cc=benjamin.mugnier@foss.st.com \
--cc=bryan.odonoghue@linaro.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dongcheng.yan@intel.com \
--cc=git@apitzsch.eu \
--cc=hansg@kernel.org \
--cc=hardevsinh.palaniya@siliconsignals.io \
--cc=heimir.sverrisson@gmail.com \
--cc=himanshu.bhavani@siliconsignals.io \
--cc=hverkuil@xs4all.nl \
--cc=jingjing.xiong@intel.com \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=matthias.fend@emfend.at \
--cc=mchehab@kernel.org \
--cc=ribalda@chromium.org \
--cc=robh@kernel.org \
--cc=sakari.ailus@linux.intel.com \
--cc=sylvain.petinot@foss.st.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