From: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
To: frank-w@public-files.de, Frank Wunderlich <linux@fw-web.de>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Matthias Brugger <matthias.bgg@gmail.com>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org
Subject: Re: [PATCH v2 03/18] arm64: dts: mediatek: mt7988: add fixed regulators for 1v8 and 3v3
Date: Tue, 3 Dec 2024 15:20:15 +0100 [thread overview]
Message-ID: <4da0ab36-34c2-413a-90b3-bcdbdd4a6ac0@collabora.com> (raw)
In-Reply-To: <371B3F0C-D468-45C8-B1F6-F4619B7C72DD@public-files.de>
Il 03/12/24 11:51, Frank Wunderlich ha scritto:
> Am 3. Dezember 2024 10:40:54 MEZ schrieb AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>:
>> Il 02/12/24 13:25, Frank Wunderlich ha scritto:
>>> From: Frank Wunderlich <frank-w@public-files.de>
>>>
>>> Add regulator nodes used for mmc to Bananapi R4 board.
>>>
>>> Signed-off-by: Frank Wunderlich <frank-w@public-files.de>
>>
>> If you're adding the eMMC regulators, I assume that there's an eMMC, or that even
>> if there's no device in some version of the board, these two regulators are always
>> assigned to the eMMC device - right?
>
> Like BPi-R3 there is one mmc controller mapped to either sd or emmc. I can move the regulators to the dtbo,but then they are defined twice (at least 3v3).
>
>> You should, at this point, do exactly that: you can leave the mmc0 disabled and
>> only enable it in a DTBO.
>
> I enable it only in dtbo...
>
>> &mmc0 {
>> /* eMMC gets enabled by DTBO if present */
>> vmmc-supply = <®_3p3v>;
>> vqmmc-supply = <®_1p8v>;
>> };
>
> Problem is here that sdcard uses only the 3v3 twice
>
> https://github.com/frank-w/BPI-Router-Linux/blob/6.12-main/arch/arm64/boot/dts/mediatek/mt7988a-bananapi-bpi-r4-sd.dtso
>
> And emmc needs both
>
> https://github.com/frank-w/BPI-Router-Linux/blob/6.12-main/arch/arm64/boot/dts/mediatek/mt7988a-bananapi-bpi-r4-emmc.dtso
>
> Only defining the vmmc-supply in dts and set only the other in dtso is possible but but imho not nice.
>
If you added that in the commit description in the first place, I wouldn't
have sent you that suggestion ;-)
So, please add the reason that you just explained to me in the description
of this commit and just leave the code as-is.
Cheers!
>> Cheers,
>> Angelo
>>
>>> ---
>>> v2:
>>> - move mmc regulators to board dts of bpi-r4
>>> ---
>>> .../dts/mediatek/mt7988a-bananapi-bpi-r4.dts | 18 ++++++++++++++++++
>>> 1 file changed, 18 insertions(+)
>>>
>>> diff --git a/arch/arm64/boot/dts/mediatek/mt7988a-bananapi-bpi-r4.dts b/arch/arm64/boot/dts/mediatek/mt7988a-bananapi-bpi-r4.dts
>>> index d914eae2b524..df53512c6890 100644
>>> --- a/arch/arm64/boot/dts/mediatek/mt7988a-bananapi-bpi-r4.dts
>>> +++ b/arch/arm64/boot/dts/mediatek/mt7988a-bananapi-bpi-r4.dts
>>> @@ -8,6 +8,24 @@ / {
>>> compatible = "bananapi,bpi-r4", "mediatek,mt7988a";
>>> model = "Banana Pi BPI-R4";
>>> chassis-type = "embedded";
>>> +
>>> + reg_1p8v: regulator-1p8v {
>>> + compatible = "regulator-fixed";
>>> + regulator-name = "fixed-1.8V";
>>> + regulator-min-microvolt = <1800000>;
>>> + regulator-max-microvolt = <1800000>;
>>> + regulator-boot-on;
>>> + regulator-always-on;
>>> + };
>>> +
>>> + reg_3p3v: regulator-3p3v {
>>> + compatible = "regulator-fixed";
>>> + regulator-name = "fixed-3.3V";
>>> + regulator-min-microvolt = <3300000>;
>>> + regulator-max-microvolt = <3300000>;
>>> + regulator-boot-on;
>>> + regulator-always-on;
>>> + };
>>> };
>>> &pio {
>>
>>
>
>
> regards Frank
next prev parent reply other threads:[~2024-12-03 14:20 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-02 12:25 [PATCH v2 00/18] continue mt7988 devicetree work Frank Wunderlich
2024-12-02 12:25 ` [PATCH v2 01/18] arm64: dts: mediatek: mt7988: enable watchdog on bpi-r4 Frank Wunderlich
2024-12-03 9:40 ` AngeloGioacchino Del Regno
2024-12-02 12:25 ` [PATCH v2 02/18] arm64: dts: mediatek: mt7988: add mmc support Frank Wunderlich
2024-12-03 9:40 ` AngeloGioacchino Del Regno
2024-12-02 12:25 ` [PATCH v2 03/18] arm64: dts: mediatek: mt7988: add fixed regulators for 1v8 and 3v3 Frank Wunderlich
2024-12-03 9:40 ` AngeloGioacchino Del Regno
2024-12-03 10:51 ` Frank Wunderlich
2024-12-03 14:20 ` AngeloGioacchino Del Regno [this message]
2024-12-03 15:08 ` Frank Wunderlich (linux)
2024-12-02 12:25 ` [PATCH v2 04/18] arm64: dts: mediatek: mt7988: add lvts node Frank Wunderlich
2024-12-03 9:40 ` AngeloGioacchino Del Regno
2024-12-02 12:25 ` [PATCH v2 05/18] arm64: dts: mediatek: mt7988: add thermal-zone Frank Wunderlich
2024-12-03 9:40 ` AngeloGioacchino Del Regno
2024-12-02 12:25 ` [PATCH v2 06/18] arm64: dts: mediatek: mt7988: add thermal trips to bpi-r4 Frank Wunderlich
2024-12-03 9:40 ` AngeloGioacchino Del Regno
2024-12-02 12:25 ` [PATCH v2 07/18] arm64: dts: mediatek: mt7988: add reserved memory Frank Wunderlich
2024-12-03 9:40 ` AngeloGioacchino Del Regno
2024-12-02 12:25 ` [PATCH v2 08/18] arm64: dts: mediatek: mt7988: add mcu-sys node for cpu Frank Wunderlich
2024-12-03 9:40 ` AngeloGioacchino Del Regno
2024-12-02 12:25 ` [PATCH v2 09/18] arm64: dts: mediatek: mt7988: add operating-points Frank Wunderlich
2024-12-03 9:40 ` AngeloGioacchino Del Regno
2024-12-02 12:25 ` [PATCH v2 10/18] arm64: dts: mediatek: mt7988: enable serial0 on bpi-r4 Frank Wunderlich
2024-12-03 9:40 ` AngeloGioacchino Del Regno
2024-12-03 11:27 ` Frank Wunderlich
2024-12-03 14:23 ` AngeloGioacchino Del Regno
2024-12-02 12:25 ` [PATCH v2 11/18] arm64: dts: mediatek: mt7988: add chosen node " Frank Wunderlich
2024-12-02 13:46 ` Krzysztof Kozlowski
2024-12-02 14:29 ` Frank Wunderlich
2024-12-02 15:58 ` Krzysztof Kozlowski
2024-12-02 17:54 ` Aw: " Frank Wunderlich
2024-12-03 9:40 ` AngeloGioacchino Del Regno
2024-12-02 12:25 ` [PATCH v2 12/18] arm64: dts: mediatek: mt7988: add missing clock-div property for i2c Frank Wunderlich
2024-12-03 9:40 ` AngeloGioacchino Del Regno
2024-12-02 12:25 ` [PATCH v2 13/18] arm64: dts: mediatek: mt7988: add i2c to bpi-r4 board Frank Wunderlich
2024-12-03 9:40 ` AngeloGioacchino Del Regno
2024-12-03 10:58 ` Frank Wunderlich
2024-12-03 14:22 ` AngeloGioacchino Del Regno
2024-12-03 15:28 ` Frank Wunderlich (linux)
2024-12-02 12:25 ` [PATCH v2 14/18] arm64: dts: mediatek: mt7988: add pmic on bpi-r4 Frank Wunderlich
2024-12-03 9:40 ` AngeloGioacchino Del Regno
2024-12-03 14:04 ` Frank Wunderlich
2024-12-02 12:25 ` [PATCH v2 15/18] arm64: dts: mediatek: mt7988: add proc-supply for cpus " Frank Wunderlich
2024-12-03 9:40 ` AngeloGioacchino Del Regno
2024-12-02 12:25 ` [PATCH v2 16/18] arm64: dts: mediatek: mt7988: add i2c-mux " Frank Wunderlich
2024-12-03 9:40 ` AngeloGioacchino Del Regno
2024-12-02 12:25 ` [PATCH v2 17/18] arm64: dts: mediatek: mt7988: enable ssusb1 " Frank Wunderlich
2024-12-03 9:40 ` AngeloGioacchino Del Regno
2024-12-04 11:29 ` Frank Wunderlich (linux)
2024-12-02 12:25 ` [PATCH v2 18/18] arm64: dts: mediatek: mt7988: enable pwm " Frank Wunderlich
2024-12-03 9:40 ` AngeloGioacchino Del Regno
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=4da0ab36-34c2-413a-90b3-bcdbdd4a6ac0@collabora.com \
--to=angelogioacchino.delregno@collabora.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=frank-w@public-files.de \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux@fw-web.de \
--cc=matthias.bgg@gmail.com \
--cc=robh@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