From: Yao Zi <me@ziyao.cc>
To: Michael Opdenacker <michael.opdenacker@rootcommit.com>,
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
Subject: Re: [PATCH 1/2] riscv: dts: spacemit: Add i2c buses on OrangePi RV2
Date: Mon, 15 Dec 2025 12:58:10 +0000 [thread overview]
Message-ID: <aUAF4iNjuP5AWJaf@pie> (raw)
In-Reply-To: <20251215-k1-boards-add-mmc-v1-1-d68dc87d4aab@rootcommit.com>
On Mon, Dec 15, 2025 at 10:10:14AM +0000, Michael Opdenacker wrote:
> The OrangePi RV2 board exposes i2c2 and i2c8 buses
> from the Spacemit K1 SoC.
>
> This declares devices present on such buses, in particular
> the at24 eeprom to store MAC addresses and the regulators
> attached to the PMIC on i2c8.
This series is named as "Attempt to enable MMC on SpacemiT K1 boards",
what's the relationship between MMC and PMIC/I2C bus? You didn't make
use of any regulators in the second patch, either (which seems wrong to
me).
vmmc-supply specifies the card's power supply. And if you want to enable
SDR modes which mandate 1.8v IO level, vqmmc-supply is also necessary
for switching between 1.8v and 3.3v.
Regards,
Yao Zi
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2025-12-15 12:58 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-15 10:10 [PATCH 0/2] Attempt to enable MMC on SpacemiT K1 boards Michael Opdenacker
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 [this message]
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=aUAF4iNjuP5AWJaf@pie \
--to=me@ziyao.cc \
--cc=dan.carpenter@linaro.org \
--cc=dlan@gentoo.org \
--cc=linux-riscv@lists.infradead.org \
--cc=michael.opdenacker@rootcommit.com \
--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