From: Michael Opdenacker <michael.opdenacker@rootcommit.com>
To: Yixun Lan <dlan@gentoo.org>
Cc: Dan Carpenter <dan.carpenter@linaro.org>,
Binbin Zhou <zhoubinbin@loongson.cn>,
linux-riscv@lists.infradead.org, spacemit@lists.linux.dev,
Michael Opdenacker <michael.opdenacker@rootcommit.com>
Subject: [PATCH 0/2] Attempt to enable MMC on SpacemiT K1 boards
Date: Mon, 15 Dec 2025 10:10:13 +0000 (UTC) [thread overview]
Message-ID: <20251215-k1-boards-add-mmc-v1-0-d68dc87d4aab@rootcommit.com> (raw)
The following commits are trying to enable MMC support on the OrangePi RV2
and BananaPi F3 boards.
This is partially supported. On both boards, partitions are
recognized and a filesystem can be read until a certain point.
However, after attempting to read a partition via dd to /dev/null,
this error is shown:
[ 503.868650] Disabling IRQ #21
IRQ #21 was indeed the IRQ for mmc (from /proc/interrupts):
CPU0 CPU1 CPU2 CPU3 CPU4 CPU5 CPU6 CPU7
21: 390 0 0 0 0 0 0 0 SiFive PLIC 99 Edge mmc1
This "Disabling IRQ" message comes from kernel/irq/spurious.c,
meaning that the IRQ was spurious, i.e. not handled by the driver.
This is confirmed by the number of interrupts:
CPU0 CPU1 CPU2 CPU3 CPU4 CPU5 CPU6 CPU7
21: 100391 0 0 0 0 0 0 0 SiFive PLIC 99 Edge mmc1
What could be wrong? Are the pin configurations correct?
My understanding of MMC/SD and of the K1 SoC is very limited.
Signed-off-by: Michael Opdenacker <michael.opdenacker@rootcommit.com>
---
Michael Opdenacker (2):
riscv: dts: spacemit: Add i2c buses on OrangePi RV2
riscv: dts: spacemit: Add MMC support on BPI-F3 and OrangePi RV2
arch/riscv/boot/dts/spacemit/k1-bananapi-f3.dts | 12 ++
arch/riscv/boot/dts/spacemit/k1-orangepi-rv2.dts | 176 +++++++++++++++++++++++
arch/riscv/boot/dts/spacemit/k1-pinctrl.dtsi | 13 ++
arch/riscv/boot/dts/spacemit/k1.dtsi | 10 ++
4 files changed, 211 insertions(+)
---
base-commit: 8f0b4cce4481fb22653697cced8d0d04027cb1e8
change-id: 20251215-k1-boards-add-mmc-843c7d9e5822
Best regards,
--
Michael Opdenacker <michael.opdenacker@rootcommit.com>
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next reply other threads:[~2025-12-15 10:10 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-15 10:10 Michael Opdenacker [this message]
2025-12-15 10:10 ` [PATCH 2/2] riscv: dts: spacemit: Add MMC support on BPI-F3 and OrangePi RV2 Michael Opdenacker
2025-12-15 12:46 ` Yao Zi
2025-12-15 13:58 ` Michael Opdenacker
2025-12-24 15:00 ` Chukun Pan
2025-12-29 10:14 ` Javier Martinez Canillas
2025-12-15 10:10 ` [PATCH 1/2] riscv: dts: spacemit: Add i2c buses on " Michael Opdenacker
2025-12-15 12:58 ` Yao Zi
2025-12-15 15:00 ` Michael Opdenacker
2025-12-16 5:37 ` Yao Zi
2025-12-16 21:05 ` Michael Opdenacker
2025-12-17 15:26 ` Iker Pedrosa
2025-12-17 16:27 ` Michael Opdenacker
2025-12-17 22:10 ` Johannes Erdfelt
2025-12-18 5:19 ` Michael Opdenacker
2025-12-18 5:25 ` Michael Opdenacker
2025-12-18 9:49 ` Iker Pedrosa
2025-12-19 11:29 ` Yixun Lan
2025-12-20 2:22 ` Yao Zi
2025-12-17 20:25 ` Javier Martinez Canillas
2025-12-16 8:58 ` Javier Martinez Canillas
2025-12-24 14:00 ` Chukun Pan
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=20251215-k1-boards-add-mmc-v1-0-d68dc87d4aab@rootcommit.com \
--to=michael.opdenacker@rootcommit.com \
--cc=dan.carpenter@linaro.org \
--cc=dlan@gentoo.org \
--cc=linux-riscv@lists.infradead.org \
--cc=spacemit@lists.linux.dev \
--cc=zhoubinbin@loongson.cn \
/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