From: Charles Perry <charles.perry@microchip.com>
To: Linus Walleij <linusw@kernel.org>
Cc: Charles Perry <charles.perry@microchip.com>,
<linus.walleij@linaro.org>, <linux-gpio@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <joshua.yeong@starfivetech.com>,
<anup@brainfault.org>, <rahul.pathak@oss.qualcomm.com>,
<leyfoon.tan@starfivetech.com>
Subject: Re: [RFC] RPMI pin control specification
Date: Thu, 19 Nov 2026 12:04:41 -0500 [thread overview]
Message-ID: <av8sKVcE17v56Vew@MON-LT-C78453.mchp-main.com> (raw)
In-Reply-To: <CAD++jLn2dBDakGxRzCby5bUJpianq65=WdmHKrpeF9ZqwH0Zgg@mail.gmail.com>
Hello Linus,
On Wed, Nov 18, 2026 at 10:36:43PM +0100, Linus Walleij wrote:
> Hi Charles,
>
> sorry for replying so late, kernel development is intense these days.
No problem, thank you for replying.
>
> On Tue, Oct 27, 2026 at 10:43 PM Charles Perry
> <charles.perry@microchip.com> wrote:
>
> > There is currently a spec under review for adding a pin control service to
> > Risc-V Platform Management Interface (RPMI). RPMI is a messaging interface
> > between an application processor and a platform controller for riscv.
>
> I actually have only one question:
>
> Is this spec so similar to another four-letter firmware interface that
> drivers/pinctrl/pinctrl-scmi.c can be used without changes or perhaps
> by a simple addition of a compatible string?
No, that is not the case currently. There are semantic differences in the
protocol, the message format changes, the enums are not the same, the
underlying transport is not the same, etc.
On the topic of SCMI, are you aware of anything that could have been
improved or should have been done differently in the pin control protocol?
>
> Because what I'm not interested in are two necessarily different drivers
> with the same content.
>
> Other than that I understand these specifications are similar for some
> reasons that I maybe don't want to concern myself with, so I'm fine
> either way.
>
> Yours,
> Linus Walleij
--
Thanks,
Charles
prev parent reply other threads:[~2026-11-19 17:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-27 21:42 Charles Perry
2026-11-18 21:36 ` Linus Walleij
2026-11-19 17:04 ` Charles Perry [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=av8sKVcE17v56Vew@MON-LT-C78453.mchp-main.com \
--to=charles.perry@microchip.com \
--cc=anup@brainfault.org \
--cc=joshua.yeong@starfivetech.com \
--cc=leyfoon.tan@starfivetech.com \
--cc=linus.walleij@linaro.org \
--cc=linusw@kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rahul.pathak@oss.qualcomm.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
all inboxes | Powered by JetHome®