From: E Shattow <e@freeshell.de>
To: Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Alexandre Ghiti <alex@ghiti.fr>
Cc: linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org,
devicetree@vger.kernel.org, E Shattow <e@freeshell.de>
Subject: [PATCH v1 0/2] riscv: dts: starfive: jh7110-common: drop no-mmc and power-on-delay-ms from mmc interfaces
Date: Wed, 3 Sep 2025 03:13:34 -0700 [thread overview]
Message-ID: <20250903101346.861076-1-e@freeshell.de> (raw)
Drop no-mmc and power-on-delay-ms properties.
The committer cannot be reached for comment and per discussion [1] and
testing there is not any observable problem that is being solved by
having these properties for the VisionFive 2 or similar variant boards
through the jh7110-common.dtsi include.
E Shattow (2):
riscv: dts: starfive: jh7110-common: drop no-mmc property from mmc1
riscv: dts: starfive: jh7110-common: drop mmc post-power-on-delay-ms
arch/riscv/boot/dts/starfive/jh7110-common.dtsi | 3 ---
1 file changed, 3 deletions(-)
base-commit: f66eb149b87677da3171a0ed51c77c3599ad55d6
--
2.50.0
next reply other threads:[~2025-09-03 10:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-03 10:13 E Shattow [this message]
2025-09-03 10:13 ` [PATCH v1 1/2] riscv: dts: starfive: jh7110-common: drop no-mmc property from mmc1 E Shattow
2025-09-03 10:13 ` [PATCH v1 2/2] riscv: dts: starfive: jh7110-common: drop mmc post-power-on-delay-ms E Shattow
2025-09-03 10:19 ` [PATCH v1 0/2] riscv: dts: starfive: jh7110-common: drop no-mmc and power-on-delay-ms from mmc interfaces E Shattow
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=20250903101346.861076-1-e@freeshell.de \
--to=e@freeshell.de \
--cc=alex@ghiti.fr \
--cc=aou@eecs.berkeley.edu \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.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).