From: E Shattow <e@freeshell.de>
To: Hal Feng <hal.feng@linux.starfivetech.com>,
Heinrich Schuchardt <heinrich.schuchardt@canonical.com>
Cc: linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-riscv@lists.infradead.org,
Emil Renner Berthing <kernel@esmil.dk>,
Conor Dooley <conor@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Hal Feng <hal.feng@starfivetech.com>
Subject: Re: [PATCH v2 5/5] riscv: dts: starfive: jh7110-common: bootph-pre-ram hinting needed by boot loader
Date: Thu, 6 Feb 2025 03:17:26 -0800 [thread overview]
Message-ID: <cba21857-7eb2-4f10-a1bd-6743ce63dfa6@freeshell.de> (raw)
In-Reply-To: <62D89163A60680E7+f0f5a4d4-42f1-454d-9dfe-cf53e2aca4ac@linux.starfivetech.com>
On 2/5/25 18:59, Hal Feng wrote:
> On 2/5/2025 6:01 PM, Heinrich Schuchardt wrote:
>> On 2/5/25 08:57, Hal Feng wrote:
>>> On 2/3/2025 9:37 AM, E Shattow wrote:
>>>> Add bootph-pre-ram hinting to jh7110-common.dtsi:
>>>> - i2c5_pins and i2c-pins subnode for connection to eeprom
>>>> - eeprom node
>>>> - qspi flash configuration subnode
>>>> - memory node
>>>> - uart0 for serial console
>>>>
>>>> With this the U-Boot SPL secondary program loader may drop such
>>>> overrides when using dt-rebasing with JH7110 OF_UPSTREAM board targets.
>>>>
>>>> Signed-off-by: E Shattow <e@freeshell.de>
>>>> ---
>>>> arch/riscv/boot/dts/starfive/jh7110-common.dtsi | 6 ++++++
>>>> 1 file changed, 6 insertions(+)
>>>>
>>>> diff --git a/arch/riscv/boot/dts/starfive/jh7110-common.dtsi b/arch/riscv/boot/dts/starfive/jh7110-common.dtsi
>>>> index 30c5f3487c8b..c9e7ae59ee7c 100644
>>>> --- a/arch/riscv/boot/dts/starfive/jh7110-common.dtsi
>>>> +++ b/arch/riscv/boot/dts/starfive/jh7110-common.dtsi
>>>> @@ -28,6 +28,7 @@ chosen {
>>>> memory@40000000 {
>>>> device_type = "memory";
>>>> reg = <0x0 0x40000000 0x1 0x0>;
>>>> + bootph-pre-ram;
>>>> };
>>>> gpio-restart {
>>>> @@ -247,6 +248,7 @@ emmc_vdd: aldo4 {
>>>> };
>>>> eeprom@50 {
>>>> + bootph-pre-ram;
>>>> compatible = "atmel,24c04";
>>>> reg = <0x50>;
>>>> pagesize = <16>;
>>>> @@ -323,6 +325,7 @@ &qspi {
>>>> nor_flash: flash@0 {
>>>> compatible = "jedec,spi-nor";
>>>> reg = <0>;
>>>> + bootph-pre-ram;
>>>> cdns,read-delay = <2>;
>>>> spi-max-frequency = <100000000>;
>>>> cdns,tshsl-ns = <1>;
>>>> @@ -405,6 +408,7 @@ GPOEN_SYS_I2C2_DATA,
>>>> };
>>>> i2c5_pins: i2c5-0 {
>>>> + bootph-pre-ram;
>>>> i2c-pins {
>>>> pinmux = <GPIOMUX(19, GPOUT_LOW,
>>>> GPOEN_SYS_I2C5_CLK,
>>>> @@ -413,6 +417,7 @@ GPI_SYS_I2C5_CLK)>,
>>>> GPOEN_SYS_I2C5_DATA,
>>>> GPI_SYS_I2C5_DATA)>;
>>>> bias-disable; /* external pull-up */
>>>> + bootph-pre-ram;
>>>> input-enable;
>>>> input-schmitt-enable;
>>>> };
>>>> @@ -641,6 +646,7 @@ GPOEN_DISABLE,
>>>> };
>>>> &uart0 {
>>>> + bootph-pre-ram;
>>>> clock-frequency = <24000000>;
>>>> pinctrl-names = "default";
>>>> pinctrl-0 = <&uart0_pins>;
>>>
>>> What about &mmc0, &mmc1, &qspi, &sysgpio, &mmc0_pins, &mmc1_pins, &i2c5?
>>> Why not add "bootph-pre-ram;" for them?
>>
>> Would they be needed before relocation of U-Boot to DRAM?
>
> Yeah, they are needed by SPL and they are set in
> U-Boot arch/riscv/dts/jh7110-common-u-boot.dtsi.
>
> Best regards,
> Hal
>
When I tested on Star64 there was none of those needed to boot. We can
add more bootph-pre-ram as needed but I want to know how to test
(because I did not see any need for these).
How do you test that these are needed?
-E
next prev parent reply other threads:[~2025-02-06 11:17 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-03 1:37 [PATCH v2 0/5] riscv: dts: starfive: jh7110-common: Sync downstream U-Boot changes E Shattow
2025-02-03 1:37 ` [PATCH v2 1/5] riscv: dts: starfive: jh7110-common: replace syscrg clock assignments E Shattow
2025-02-05 10:16 ` Emil Renner Berthing
2025-02-05 12:52 ` E Shattow
2025-02-07 8:31 ` Hal Feng
2025-02-09 23:33 ` E Shattow
2025-02-20 6:38 ` Hal Feng
2025-02-28 8:08 ` E Shattow
2025-02-07 12:21 ` Emil Renner Berthing
2025-02-03 1:37 ` [PATCH v2 2/5] riscv: dts: starfive: jh7110-common: qspi flash setting read-delay 2 cycles max 100MHz E Shattow
2025-02-05 10:18 ` Emil Renner Berthing
2025-02-05 13:21 ` E Shattow
2025-02-07 12:23 ` Emil Renner Berthing
2025-02-03 1:37 ` [PATCH v2 3/5] riscv: dts: starfive: jh7110-common: assign 24MHz clock-frequency to uart0 E Shattow
2025-02-05 7:23 ` Hal Feng
2025-02-05 10:29 ` Emil Renner Berthing
2025-04-23 20:18 ` E Shattow
2025-02-03 1:37 ` [PATCH v2 4/5] riscv: dts: starfive: jh7110-common: add eeprom node to i2c5 E Shattow
2025-02-05 10:33 ` Emil Renner Berthing
2025-02-03 1:37 ` [PATCH v2 5/5] riscv: dts: starfive: jh7110-common: bootph-pre-ram hinting needed by boot loader E Shattow
2025-02-05 7:57 ` Hal Feng
2025-02-05 10:01 ` Heinrich Schuchardt
2025-02-06 2:59 ` Hal Feng
2025-02-06 11:17 ` E Shattow [this message]
2025-02-07 3:01 ` Hal Feng
2025-02-28 7:53 ` E Shattow
2025-02-28 9:54 ` Maud Spierings
2025-04-24 5:15 ` E Shattow
2025-04-24 10:54 ` Heinrich Schuchardt
2025-04-24 23:37 ` E Shattow
2025-02-05 10:35 ` Emil Renner Berthing
2025-02-05 10:53 ` Conor Dooley
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=cba21857-7eb2-4f10-a1bd-6743ce63dfa6@freeshell.de \
--to=e@freeshell.de \
--cc=aou@eecs.berkeley.edu \
--cc=conor@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=hal.feng@linux.starfivetech.com \
--cc=hal.feng@starfivetech.com \
--cc=heinrich.schuchardt@canonical.com \
--cc=kernel@esmil.dk \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.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
Powered by JetHome