Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: David Heidelberg <david@ixit.cz>
To: "Ondřej Jirman" <megi@xff.cz>,
	"Sakari Ailus" <sakari.ailus@linux.intel.com>,
	"Mauro Carvalho Chehab" <mchehab@kernel.org>,
	"Rob Herring" <robh@kernel.org>,
	"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
	"Conor Dooley" <conor+dt@kernel.org>,
	"Heiko Stuebner" <heiko@sntech.de>,
	"Olivier Benjamin" <olivier.benjamin@bootlin.com>,
	"Manuel Traut" <manut@mecka.net>,
	"Alexander Warnecke" <awarnecke002@hotmail.com>,
	"Frank Li" <Frank.Li@nxp.com>,
	"Sascha Hauer" <s.hauer@pengutronix.de>,
	"Pengutronix Kernel Team" <kernel@pengutronix.de>,
	"Fabio Estevam" <festevam@gmail.com>,
	"Shawn Guo" <shawnguo@kernel.org>,
	"Krzysztof Kozlowski" <krzk@kernel.org>,
	linux-media@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-rockchip@lists.infradead.org, phone-devel@vger.kernel.org,
	imx@lists.linux.dev, stable@vger.kernel.org
Subject: Re: [PATCH 2/4] arm64: dts: rockchip: rk3399-pinephone-pro: DW9714 coil requires higher voltage
Date: Thu, 6 Aug 2026 13:49:07 +0200	[thread overview]
Message-ID: <dd2f19ac-a65e-4e53-aa2f-6f76c949366e@ixit.cz> (raw)
In-Reply-To: <galrq4ug3hhny2ivpylqwuztwv7vnqvm6sdhlu6pucxk6qy2mz@zxw4ckkxj2sh>

On 06/08/2026 13:19, Ondřej Jirman wrote:
> Hi,
> 
> On Tue, Aug 04, 2026 at 11:12:21AM +0200, David Heidelberg wrote:
>> On 04/08/2026 09:39, Ondřej Jirman wrote:
>>> Hi,
>>>
>>> On Sat, Aug 01, 2026 at 02:35:21AM +0200, David Heidelberg via B4 Relay wrote:
>>>> From: David Heidelberg <david@ixit.cz>
>>>>
>>>> By datasheet the VDD (in-kernel named vcc) range is between 2.3 to 4.3 V.
>>>> Usually it's around 2.8 V. Here it matches the avdd2v8_dvp.
>>>>
>>>> Fixes: 9336eb829a18 ("arm64: dts: rockchip: describe I2c Bus 1 and IMX258 world camera on PinePhone Pro")
>>>> Cc: stable@vger.kernel.org
>>>> Signed-off-by: David Heidelberg <david@ixit.cz>
>>>> ---
>>>>    arch/arm64/boot/dts/rockchip/rk3399-pinephone-pro.dts | 2 +-
>>>>    1 file changed, 1 insertion(+), 1 deletion(-)
>>>>
>>>> diff --git a/arch/arm64/boot/dts/rockchip/rk3399-pinephone-pro.dts b/arch/arm64/boot/dts/rockchip/rk3399-pinephone-pro.dts
>>>> index d46cdfe3f7849..bde35d9b2263e 100644
>>>> --- a/arch/arm64/boot/dts/rockchip/rk3399-pinephone-pro.dts
>>>> +++ b/arch/arm64/boot/dts/rockchip/rk3399-pinephone-pro.dts
>>>> @@ -473,17 +473,17 @@ wcam_out: endpoint {
>>>>    			};
>>>>    		};
>>>>    	};
>>>>    	wcam_lens: camera-lens@c {
>>>>    		compatible = "dongwoon,dw9714";
>>>>    		reg = <0x0c>;
>>>>    		/* Same I2c bus as both cameras, depends on vcca1v8_codec for power. */
>>>> -		vcc-supply = <&vcc1v8_dvp>;
>>>> +		vcc-supply = <&avdd2v8_dvp>;
>>>
>>> This does not match reality, schematic says it's VCC2V8_DVP:
>>>
>>> 	https://xff.cz/dl/tmp/6253a0465329df41.png
>>
>> Ahoj,
>>
>> thanks for spotting this, since I know you have the device, would be too
>> much to ask you to send standalone fix for PP Pro?
>>
>> I would drop the change from the series.
> 
> Ok. Just for the reference, vcc1v8_dvp here feeds an enable pin for VCC2V8_DVP
> LDO regulator (which is supplied from VCC3V3_SYS and not described in DT, yet).
> So in practice enabling vcc1v8_dvp enables both VCC2V8_DVP and AVDD2V8_DVP and
> while DT does not describe the HW in detail, it describes the only regulator
> that is actually controllable and enables all needed power rails for the camera
> modules all by itself in proper order/timing.
> 
> Not sure what's the DT maintainers idea here about whether DT has to describe
> every detail of power rails routing, or just what's pragmatic.

My perception is that DT syntax should describe everything, except passive 
components.

No additional GPIO is needed to enable VCC and AVDD?

Here, it seems to me that explanation like this in DT could cover it. But I'm no 
authority here :)

David

> 
> Best regards,
> 	o.j.
> 
>> David
>>
>> P.S. I noticed I didn't mark this series RFC. Too late.
>>
>>>
>>> regards,
>>> 	o.
>>>
>>>>    	};
>>>>    	ucam: camera@36 {
>>>>    		compatible = "ovti,ov8858";
>>>>    		reg = <0x36>;
>>>>    		clocks = <&cru SCLK_CIF_OUT>; /* MIPI_MCLK1, derived from CIF_CLK0 */
>>>>    		clock-names = "xvclk";
>>>>    		dovdd-supply = <&vcc1v8_dvp>;
>>>>
>>>> -- 
>>>> 2.53.0
>>>>
>>>>
>>
>> -- 
>> David Heidelberg
>>

-- 
David Heidelberg



  reply	other threads:[~2026-08-06 11:49 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-01  0:35 [PATCH 0/4] Dongwoon DW9714 - correct vcc/vdd supply voltage David Heidelberg via B4 Relay
2026-08-01  0:35 ` [PATCH 1/4] media: dt-bindings: dongwoon,dw9714: Example shouldn't imply 1.8 V David Heidelberg via B4 Relay
2026-08-01  0:35 ` [PATCH 2/4] arm64: dts: rockchip: rk3399-pinephone-pro: DW9714 coil requires higher voltage David Heidelberg via B4 Relay
2026-08-04  7:39   ` Ondřej Jirman
2026-08-04  9:12     ` David Heidelberg
2026-08-06 11:19       ` Ondřej Jirman
2026-08-06 11:49         ` David Heidelberg [this message]
2026-08-06 14:18           ` Ondřej Jirman
2026-08-01  0:35 ` [PATCH 3/4] arm64: dts: rockchip: rk3566-pinetab2: " David Heidelberg via B4 Relay
2026-08-01  0:35 ` [PATCH 4/4] arm64: dts: imx8mq-librem5: Dongwoon " David Heidelberg via B4 Relay
2026-08-03 18:12   ` Sebastian Krzyszkowiak
2026-08-03 19:35     ` David Heidelberg

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=dd2f19ac-a65e-4e53-aa2f-6f76c949366e@ixit.cz \
    --to=david@ixit.cz \
    --cc=Frank.Li@nxp.com \
    --cc=awarnecke002@hotmail.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=festevam@gmail.com \
    --cc=heiko@sntech.de \
    --cc=imx@lists.linux.dev \
    --cc=kernel@pengutronix.de \
    --cc=krzk+dt@kernel.org \
    --cc=krzk@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=manut@mecka.net \
    --cc=mchehab@kernel.org \
    --cc=megi@xff.cz \
    --cc=olivier.benjamin@bootlin.com \
    --cc=phone-devel@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=s.hauer@pengutronix.de \
    --cc=sakari.ailus@linux.intel.com \
    --cc=shawnguo@kernel.org \
    --cc=stable@vger.kernel.org \
    /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