From: "Troy Mitchell" <troy.mitchell@linux.spacemit.com>
To: "Bo Gan" <ganboing@gmail.com>,
"Troy Mitchell" <troy.mitchell@linux.spacemit.com>,
<opensbi@lists.infradead.org>
Cc: "Xianbin Zhu" <xianbin.zhu@linux.spacemit.com>,
"Anup Patel" <anup@brainfault.org>
Subject: Re: [PATCH v2 0/5] platform: generic: spacemit: add K3 platform support
Date: Fri, 21 Aug 2026 09:18:44 +0800 [thread overview]
Message-ID: <DKU85LD7UDZB.1IQH1DZ35KKQO@linux.spacemit.com> (raw)
In-Reply-To: <df177995-1c44-420d-8138-2bbc7a4861bd@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1305 bytes --]
On Thu Aug 20, 2026 at 5:26 PM +08, Bo Gan wrote:
> Hi Troy, Xianbin,
>
> I got my com260 delivered just days ago, and I'm able to review and test
> this series. I just sent out some review feedbacks. One more high-level
> question is regarding rpmi. I see the vendor opensbi utilize the services
> provided by esos running on the small cores. What's the plan here?
The RPMI interface between OpenSBI and ESOS is mainly used for
suspend/resume, power-button handling, and enabling or disabling
regulators. In our upstream Linux implementation, regulator control
is already handled by Linux. We also plan to move power-button and
suspend/resume handling into Linux, although we do not yet have a
concrete implementation plan.
>
> Is it
> (this patch series) suppose to work with the esos currently shipped?
This series is clearly compatible with the current version of ESOS,
since it only removes the RPMI-related code.
>
> Also you mentioned "K3 SDK" many times, but I couldn't find any pointers.
> What is that exactly?
I apologize for forgetting to include the link. However, it is readily
available from the official source [1].
Link: https://www.spacemit.com/community/document/info?lang=en&nodepath=software/SDK/buildroot/k3_buildroot/source.md [1]
--
Troy Mitchell
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 248 bytes --]
[-- Attachment #2: Type: text/plain, Size: 105 bytes --]
--
opensbi mailing list
opensbi@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/opensbi
prev parent reply other threads:[~2026-08-21 1:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-18 1:14 [PATCH v2 0/5] platform: generic: spacemit: add K3 platform support Troy Mitchell
2026-08-18 1:14 ` [PATCH v2 1/5] lib: sbi: select expected trap handler per hart Troy Mitchell
2026-08-20 8:40 ` Bo Gan
2026-08-18 1:14 ` [PATCH v2 2/5] platform: generic: spacemit: k1: rename cache flush operation Troy Mitchell
2026-08-18 1:14 ` [PATCH v2 3/5] platform: generic: spacemit: k1: move hart init to nascent hook Troy Mitchell
2026-08-20 8:42 ` Bo Gan
2026-08-18 1:14 ` [PATCH v2 4/5] platform: generic: spacemit: k1: refactor platform support Troy Mitchell
2026-08-18 1:14 ` [PATCH v2 5/5] platform: generic: spacemit: k3: add " Troy Mitchell
2026-08-20 9:18 ` Bo Gan
2026-08-20 14:25 ` Samuel Holland
2026-08-21 1:55 ` Troy Mitchell
2026-08-20 9:26 ` [PATCH v2 0/5] platform: generic: spacemit: add K3 " Bo Gan
2026-08-21 1:18 ` Troy Mitchell [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=DKU85LD7UDZB.1IQH1DZ35KKQO@linux.spacemit.com \
--to=troy.mitchell@linux.spacemit.com \
--cc=anup@brainfault.org \
--cc=ganboing@gmail.com \
--cc=opensbi@lists.infradead.org \
--cc=xianbin.zhu@linux.spacemit.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