From: Yixun Lan <dlan@gentoo.org>
To: Anand Moon <linux.amoon@gmail.com>
Cc: Alex Elder <elder@riscstar.com>,
"open list:RISC-V MISC SOC SUPPORT"
<linux-riscv@lists.infradead.org>,
spacemit@lists.linux.dev
Subject: Re: spacemit: P1 PMIC support on Banana pi F3 testing
Date: Sat, 26 Jul 2025 08:27:43 +0800 [thread overview]
Message-ID: <20250726002743-GYA752238@gentoo> (raw)
In-Reply-To: <CANAwSgT-z-sQoJtT+DVNywObEwnmMSgK4uPXxhk=Bxx8TK483Q@mail.gmail.com>
Hi Anand,
On 15:26 Thu 24 Jul , Anand Moon wrote:
> Hi Alex,
>
> Thank you for your work on the P1 PMIC patch for Spacemit K1 SoC - Banana Pi F3.
>
> I've been testing your patch series for the Banana Pi F3 [0] to enable SD card
> and eMMC functionality,
>
> [0] https://patchew.org/linux/20250710175107.1280221-1-elder@riscstar.com/
>
> While debugging, I cross-referenced the patch with the BPI-F3-V3 board
> schematic [1]
> and noticed several discrepancies in the power configuration:
>
> [1] https://drive.google.com/file/d/19iLJ5xnCB_oK8VeQjkPGjzAn39WYyylv/view
>
> Incorrect Voltage Ranges: The minimum and maximum voltage values for
> multiple regulators
> (including BUCKs, ALDOs, and DLDOs) In the patch, do not match the
> specifications in
> the schematic's power tree.
>
> Missing/Incorrect Labels: Many regulators are missing accurate labels and names,
> which makes mapping them to the hardware difficult.
>
> Device Tree Mapping: To configure the power sources correctly, the k1
> user names from
> the schematic needs to be properly mapped to its corresponding device
> tree nodes.
>
> I’ve put together a set of local changes to better align the regulator
> definitions with the board schematic.
> These adjustments help improve the hardware mapping to the PMIC
> regulators, though some details
> may still need refinement. If you find the changes helpful, please
> consider incorporating them into
> the next revision of the patch.
>
> I’d be grateful if you could Cc me on any future communication
> regarding testing.
> as I didn’t receive this patch series in my inbox.
>
> Thanks
> -Anand
>
> Here is the boot log [2] https://pastebin.com/cXybbVar
>
> It's not working on my end., Neither the eMMC nor the SD card is
> getting detected.
the mainline driver in tree has no SD card support, but eMMC
so, you could only test eMMC for now.
--
Yixun Lan (dlan)
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
prev parent reply other threads:[~2025-07-26 0:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-24 9:56 spacemit: P1 PMIC support on Banana pi F3 testing Anand Moon
2025-07-25 1:56 ` Alex Elder
2025-07-25 9:49 ` Anand Moon
2025-07-25 15:03 ` Anand Moon
2025-07-26 0:27 ` Yixun Lan [this message]
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=20250726002743-GYA752238@gentoo \
--to=dlan@gentoo.org \
--cc=elder@riscstar.com \
--cc=linux-riscv@lists.infradead.org \
--cc=linux.amoon@gmail.com \
--cc=spacemit@lists.linux.dev \
/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