All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michal Simek <michal.simek@amd.com>
To: Charles Perry <charles.perry@microchip.com>, u-boot@lists.denx.de
Cc: Rahul Pathak <rahul@summations.net>,
	Anup Patel <anup@brainfault.org>, Paul Walmsley <pjw@kernel.org>,
	Palmer Dabbelt <palmer@dabbelt.com>,
	Albert Ou <aou@eecs.berkeley.edu>,
	Alexandre Ghiti <alex@ghiti.fr>,
	Romain Caritey <romain.caritey@microchip.com>,
	Mame Maria Mbaye <MameMaria.Mbaye@microchip.com>,
	Tom Rini <trini@konsulko.com>,
	Heinrich Schuchardt <heinrich.schuchardt@canonical.com>,
	Rick Chen <rick@andestech.com>,
	Leo Yu-Chi Liang <ycliang@andestech.com>,
	Souvik Chakravarty <Souvik.Chakravarty@arm.com>
Subject: Re: [PATCH v2 0/5] Add support for RPMI to U-Boot
Date: Thu, 9 Jul 2026 15:02:11 +0200	[thread overview]
Message-ID: <c2c87ebf-e26b-4987-bf78-cc2508ec7ca8@amd.com> (raw)
In-Reply-To: <20260708215200.1331416-1-charles.perry@microchip.com>



On 7/8/26 23:51, Charles Perry wrote:
> Hello,
> 
> This series adds support for RISC-V Platform Management Interface (RPMI) to
> U-Boot. RPMI is an OS-agnostic protocol for communication between an
> Application Processor (AP) and a Platform Microcontroller (PuC) [1]. The
> goals and purpose of RPMI are similar to ARM's SCMI.

 From the first look it looks like SCMI. Why do you introducing something what 
can be replaced by SCMI?
And SCMI has only specific ARM transport layer but the rest is arch independent.

In our case where we have Microblaze V in programmable logic I can't see any 
reason to use RPMI for talking to the same server if I need to do it from ARM 
side too via SCMI.

I pretty much think that there should be communication with ARM and instead of 
creating another firmware interface talk to each other and have only one which 
can be used across multiple architectures.

Thanks,
Michal

  parent reply	other threads:[~2026-07-09 13:02 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-08 21:51 [PATCH v2 0/5] Add support for RPMI to U-Boot Charles Perry
2026-07-08 21:51 ` [PATCH v2 1/5] firmware: add support for RPMI Charles Perry
2026-07-08 21:51 ` [PATCH v2 2/5] firmware: rpmi: add support for the SBI MPXY transport Charles Perry
2026-07-08 21:51 ` [PATCH v2 3/5] firmware: rpmi: add support for shared memory transport Charles Perry
2026-07-08 21:51 ` [PATCH v2 4/5] drivers: clk: add support for RPMI clocks Charles Perry
2026-07-08 21:51 ` [PATCH v2 5/5] firmware: rpmi: add a test and a sandbox driver Charles Perry
2026-07-09 13:02 ` Michal Simek [this message]
2026-07-09 14:53   ` [PATCH v2 0/5] Add support for RPMI to U-Boot Heinrich Schuchardt
2026-07-09 14:54   ` Charles Perry
2026-07-09 15:20     ` Michal Simek
2026-07-09 16:57       ` Conor Dooley
2026-07-10  3:14         ` Anup Patel
2026-07-10  3:08       ` Anup Patel
2026-07-10  6:36         ` Michal Simek

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=c2c87ebf-e26b-4987-bf78-cc2508ec7ca8@amd.com \
    --to=michal.simek@amd.com \
    --cc=MameMaria.Mbaye@microchip.com \
    --cc=Souvik.Chakravarty@arm.com \
    --cc=alex@ghiti.fr \
    --cc=anup@brainfault.org \
    --cc=aou@eecs.berkeley.edu \
    --cc=charles.perry@microchip.com \
    --cc=heinrich.schuchardt@canonical.com \
    --cc=palmer@dabbelt.com \
    --cc=pjw@kernel.org \
    --cc=rahul@summations.net \
    --cc=rick@andestech.com \
    --cc=romain.caritey@microchip.com \
    --cc=trini@konsulko.com \
    --cc=u-boot@lists.denx.de \
    --cc=ycliang@andestech.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.