From: Yao Zi <me@ziyao.cc>
To: Yixun Lan <dlan@gentoo.org>, Iker Pedrosa <ikerpedrosam@gmail.com>
Cc: Michael Opdenacker <michael.opdenacker@rootcommit.com>,
Johannes Erdfelt <johannes@erdfelt.com>,
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: Sat, 20 Dec 2025 02:22:30 +0000 [thread overview]
Message-ID: <aUYIZkLmbxNXw3fF@pie> (raw)
In-Reply-To: <20251219112924-GYB1955339@gentoo.org>
On Fri, Dec 19, 2025 at 07:29:24PM +0800, Yixun Lan wrote:
> Hi Iker,
>
> thanks for pushing this, I have few comments
>
> On 10:49 Thu 18 Dec , Iker Pedrosa wrote:
> > Hi Michael, Yao, Javier, Johannes,
> >
> > Thanks everyone for the great discussion and the guidance.
...
> > 2. Extend the pinctrl driver: support is needed for switching the SD
> > voltage pins from 3.3V to 1.8V.
> we probably could leave pinctrl for now or take a look at it later when
> really necessary, the default pin settings should work for most cases,
> besides, vendor is also starting to drop two pinctrl state implementation
> (the normal vs fast ..)
>
> for 3.3v to 1.8v switch, there is one MMC1_IO_REG to control it, and
> we do need to implement a _voltage_switch() function
> and it's in another aib io space..
Note the MMC1_IO_REG (0xd401_e81c) stays right in the Pad Configuration
region (0xd401_e000, length 0xc00) as stated in the address mapping of
TRM.
So it's not another io space, it's right the pin controller. This makes
me believe it's an undocumented pinctrl register, in which case it's
pretty natural to implement the switch logic through pinctrl interface.
Seems I forgot to mention one thing: there are mysterious "asfar" and
"assar" registers in APBC region which are written 0xbaba and 0xeb10
during voltage switch process.
I've looked through the TRM and found they aren't documented, either.
But handling of them should be easy, since the whole APBC region is
registered as a syscon, though it will still be helpful to know their
effects...
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-20 2:23 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
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 [this message]
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=aUYIZkLmbxNXw3fF@pie \
--to=me@ziyao.cc \
--cc=dan.carpenter@linaro.org \
--cc=dlan@gentoo.org \
--cc=ikerpedrosam@gmail.com \
--cc=johannes@erdfelt.com \
--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