linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Muhammed Efe Cetin <efectn@6tel.net>
To: megi@xff.cz
Cc: conor+dt@kernel.org, devicetree@vger.kernel.org, efectn@6tel.net,
	heiko@sntech.de, krzysztof.kozlowski+dt@linaro.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, linux-rockchip@lists.infradead.org,
	robh+dt@kernel.org, sebastian.reichel@collabora.com
Subject: Re: [PATCH 3/3] arm64: dts: rockchip: Add Orange Pi 5
Date: Thu, 17 Aug 2023 19:28:01 +0300	[thread overview]
Message-ID: <20230817162803.17990-1-efectn@6tel.net> (raw)
In-Reply-To: <qqx5tay4etbepyyy7hqdp2prtw4t3m57esulruevggw2yi4xqf@63a7v5vzodhs>

Hi, Ondřej

On 17.08.2023 18:32, Ondřej Jirman wrote:
> On Thu, Aug 17, 2023 at 05:30:04PM +0200, megi xff wrote:
>>
>> On Thu, Aug 17, 2023 at 05:57:55PM +0300, Muhammed Efe Cetin wrote:
>>>
>>> Hi, Ondřej
>>>
>>> On 17.08.2023 16:57, Ondřej Jirman wrote:
>>>> Hi Muhammed,
>>>>
>>>>>>> [...]
>>>>>>
>>>>>>> +	vcc_1v1_nldo_s3: vcc-1v1-nldo-s3-regulator {
>>>>>>> +		compatible = "regulator-fixed";
>>>>>>> +		regulator-name = "vcc_1v1_nldo_s3";
>>>>>>> +		regulator-always-on;
>>>>>>> +		regulator-boot-on;
>>>>>>> +		regulator-min-microvolt = <1100000>;
>>>>>>> +		regulator-max-microvolt = <1100000>;
>>>>>>> +		vin-supply = <&vcc5v0_sys>;
>>>>>>> +	};
>>>>>>
>>>>>> There's no such regulator on the board.
>>>>>
>>>>> It's connected to PMIC https://i.imgur.com/sVJdC5K.png
>>>>
>>>> It's not a separate fixed regulator. It's a PMIC output from buck6 https://megous.com/dl/tmp/8630fa17407c75b9.png
>>>>
>>>
>>> I think it should be fixed regulator. It's used as vcc13-supply and
>>> vcc14-supply regulator on PMIC and it's same as other rk3588 boards.
>>
>> Yes, BUCK6 output is input to some LDOs. If you make this a regulator-fixed,
>> BUCK6 will not get enabled when those LDOs are enabled, and the LDOs will not
>> work because they'll lack input power.
>>
>> Your regulator-fixed does nothing to enable BUCK6 which is where vcc_1v1_nldo_s3
>> power rail is connected.
>>
>> It only works for you now, because dcdc-reg6 is marked as regulator-always-on,
>> so it's already enabled when you need those dependent LDOs.
> 
> And if other boards have this same HW setup and user separate DT node with
> regulator-fixed for this, they're broken, too.

As i've seen on upstream and Rockchip SDK; boards have dual RK806, have vcc_1v1_nldo_s3 node inside of pmic (rk3588-evb1-v10) and boards have single RK806, have separated vcc_1v1_nldo_s3 node. I don't know why they preferred this way.

> 
> regards,
> 	o.
> 
>> regards,
>> 	o.
>>
>>>> So this is VDD2_DDR_S3. If you want to keep the alias, just add extra alias to
>>>> dcdc-reg6 like this:
>>>>
>>>> 		...
>>>> 	vcc_1v1_nldo_s3: vdd2_ddr_s3: dcdc-reg6 {
>>>> 		...
>>>>
>>>>>>

Regards,
Efe

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2023-08-17 16:28 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-15 12:58 [PATCH 0/3] Add Support for Orange Pi 5 Muhammed Efe Cetin
2023-08-15 12:58 ` [PATCH 1/3] dt-bindings: arm: rockchip: Add Orange Pi 5 board Muhammed Efe Cetin
2023-08-15 13:46   ` Krzysztof Kozlowski
2023-08-15 12:59 ` [PATCH 2/3] arm64: dts: rockchip: Add sfc node to rk3588s Muhammed Efe Cetin
2023-08-17 21:04   ` Jonas Karlman
2023-08-15 12:59 ` [PATCH 3/3] arm64: dts: rockchip: Add Orange Pi 5 Muhammed Efe Cetin
2023-08-15 13:45   ` Krzysztof Kozlowski
2023-08-17 17:23     ` Muhammed Efe Cetin
2023-08-15 16:39   ` Ondřej Jirman
2023-08-17 13:33     ` Muhammed Efe Cetin
2023-08-17 13:57       ` Ondřej Jirman
2023-08-17 14:57         ` Muhammed Efe Cetin
2023-08-17 15:30           ` Ondřej Jirman
2023-08-17 15:32             ` Ondřej Jirman
2023-08-17 16:28               ` Muhammed Efe Cetin [this message]
2023-08-17 21:05   ` Jonas Karlman

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=20230817162803.17990-1-efectn@6tel.net \
    --to=efectn@6tel.net \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=heiko@sntech.de \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=megi@xff.cz \
    --cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).