From: "Diederik de Haas" <didi.debian@cknow.org>
To: "Sebastian Reichel" <sebastian.reichel@collabora.com>
Cc: "Nicolas Frattaroli" <nicolas.frattaroli@collabora.com>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Heiko Stuebner" <heiko@sntech.de>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>,
<linux-rockchip@lists.infradead.org>, <kernel@collabora.com>,
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 1/3] arm64: dts: rockchip: adjust dcin regulator on ROCK 4D
Date: Tue, 01 Jul 2025 10:19:33 +0200 [thread overview]
Message-ID: <DB0KL629S4E4.3ENNM27XN3IYM@cknow.org> (raw)
In-Reply-To: <5acizoywvjolaffojiawqlzixiclrqzohuhq55lbsjm6yhhlwi@w2amqugl3ee2>
[-- Attachment #1: Type: text/plain, Size: 1239 bytes --]
Hi,
On Tue Jul 1, 2025 at 1:10 AM CEST, Sebastian Reichel wrote:
> On Mon, Jun 30, 2025 at 08:12:27PM +0200, Diederik de Haas wrote:
>> On Mon Jun 30, 2025 at 5:36 PM CEST, Nicolas Frattaroli wrote:
>> > The ROCK 4D's actual DC input is 5V, and the schematic names it as being
>> > 5V as well.
>> >
>> > Rename the regulator, and change the voltage it claims to be at.
>>
>> Shouldn't it have a fixes tag then? Providing 12V where 5V is expected
>> sounds problematic ;-)
>
> This is basically "just" documentation, as the DT just describes
> a fixed regulator (i.e. nothing software controllable). This just
> changes a number in sysfs :)
>
> Note, that the 5V DCIN is a USB-C port, which does not do any PD
> negotiation, but has the 5K1 resistors on the CC lines to "request"
> 5V. If for whatever reason a higher voltage is applied (which does
> not happen as long as the power is provided by anything remotely
> following the USB specifications) there also is an over-voltage
> protection chip. So it's not problematic :)
I was worried about and wondered why I/we did NOT receive reports about
boards being fried. Good to know, thanks!
> OTOH adding a Fixes tag does not hurt ;)
Cheers,
Diederik
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2025-07-01 8:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-30 15:36 [PATCH 0/3] ROCK 4D DT additions: regulators, usb, rfkill Nicolas Frattaroli
2025-06-30 15:36 ` [PATCH 1/3] arm64: dts: rockchip: adjust dcin regulator on ROCK 4D Nicolas Frattaroli
2025-06-30 18:12 ` Diederik de Haas
2025-06-30 23:10 ` Sebastian Reichel
2025-07-01 8:19 ` Diederik de Haas [this message]
2025-07-01 8:55 ` Nicolas Frattaroli
2025-07-01 9:07 ` Diederik de Haas
2025-06-30 15:36 ` [PATCH 2/3] arm64: dts: rockchip: complete USB nodes " Nicolas Frattaroli
2025-06-30 15:36 ` [PATCH 3/3] arm64: dts: rockchip: theoretically enable Wi-Fi " Nicolas Frattaroli
2025-07-10 9:27 ` [PATCH 0/3] ROCK 4D DT additions: regulators, usb, rfkill Heiko Stuebner
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=DB0KL629S4E4.3ENNM27XN3IYM@cknow.org \
--to=didi.debian@cknow.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=kernel@collabora.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=nicolas.frattaroli@collabora.com \
--cc=robh@kernel.org \
--cc=sebastian.reichel@collabora.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