mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: E Shattow <e@freeshell.de>
To: Owen O'Hehir <oo.hehir@gmail.com>,
	Conor Dooley <conor@kernel.org>,
	Emil Renner Berthing <kernel@esmil.dk>
Cc: Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Paul Walmsley <pjw@kernel.org>,
	Palmer Dabbelt <palmer@dabbelt.com>,
	Albert Ou <aou@eecs.berkeley.edu>,
	Alexandre Ghiti <alex@ghiti.fr>,
	linux-riscv@lists.infradead.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] riscv: dts: starfive: jh7110-common: keep the status power LED on
Date: Fri, 6 Nov 2026 10:51:00 -0800	[thread overview]
Message-ID: <179fe9e8-322b-4745-8734-d5de5f1e8487@freeshell.de> (raw)
In-Reply-To: <20261106184055.3891621-1-oo.hehir@gmail.com>

Hi Owen,

On 11/6/26 10:40, Owen O'Hehir wrote:
> The firmware turns the status power LED on, but the node has no
> default-state, so the LED switches off when leds-gpio probes and the
> board looks powered down.
> 
> Default the LED to on.
> 
> Tested on a VisionFive 2 v1.3B.
> 
> Fixes: 1ec99dfe9eb0 ("riscv: dts: starfive: jh7110-common: add status power led node")
> Signed-off-by: Owen O'Hehir <oo.hehir@gmail.com>
> ---
>  arch/riscv/boot/dts/starfive/jh7110-common.dtsi | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/arch/riscv/boot/dts/starfive/jh7110-common.dtsi b/arch/riscv/boot/dts/starfive/jh7110-common.dtsi
> index 64de468f2..7ec94e968 100644
> --- a/arch/riscv/boot/dts/starfive/jh7110-common.dtsi
> +++ b/arch/riscv/boot/dts/starfive/jh7110-common.dtsi
> @@ -44,6 +44,7 @@ leds {
>  
>  		led_status_power: led-0 {
>  			gpios = <&aongpio 3 GPIO_ACTIVE_HIGH>;
> +			default-state = "on";
>  		};
>  	};
>  
> 
> base-commit: ddfe51b0a0f5dc9e415cc2c8ad8db17532dd426b

I think this change may disagree with fastboot select function on
VisionFive2 Lite, where (if I understand this correctly) it is read as
an input; see that schematic listed as the "VisionFive 2 Lit Schematic":

https://www.starfivetech.com/en/index.php?s=docs&c=search&keyword=schematic

You may reference also the ghidra archive
https://web.archive.org/web/20260718140236/https://freeshell.de/e/riscv64/hrv-jhre-JH-7110%20BootROM%20analysis_2026_02_22.gar
for decompilation of JH-7110 BootROM loader, and there (to the best of
my understanding) it is not interacting with that register so it must be
purely the SoC reset state.

-E

  reply	other threads:[~2026-11-06 18:51 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-06 18:40 Owen O'Hehir
2026-11-06 18:51 ` E Shattow [this message]
2026-11-06 19:59   ` Owen O'Hehir
2026-11-06 20:30     ` E Shattow
2026-11-06 21:12       ` Owen O'Hehir
2026-11-06 21:13       ` Owen O'Hehir
2026-11-06 18:54 ` Conor Dooley
2026-11-06 19:06   ` E Shattow
2026-11-06 21:15     ` 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=179fe9e8-322b-4745-8734-d5de5f1e8487@freeshell.de \
    --to=e@freeshell.de \
    --cc=alex@ghiti.fr \
    --cc=aou@eecs.berkeley.edu \
    --cc=conor@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=kernel@esmil.dk \
    --cc=krzk+dt@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=oo.hehir@gmail.com \
    --cc=palmer@dabbelt.com \
    --cc=pjw@kernel.org \
    --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

all inboxes | Powered by JetHome®