From: "Alex Bennée" <alex.bennee@linaro.org>
To: Peter Hilber <peter.hilber@opensynergy.com>
Cc: virtio-comment@lists.oasis-open.org,
linux-arm-kernel@lists.infradead.org, Souvik.Chakravarty@arm.com,
Sudeep.Holla@arm.com, virtio-dev@lists.oasis-open.org
Subject: Re: [virtio-dev] [PATCH v3] Add virtio SCMI device specification
Date: Mon, 23 Mar 2020 17:35:57 +0000 [thread overview]
Message-ID: <87blonas8y.fsf@linaro.org> (raw)
In-Reply-To: <20200317192053.15665-1-peter.hilber@opensynergy.com>
Peter Hilber <peter.hilber@opensynergy.com> writes:
> This patch proposes a new virtio device for the Arm SCMI protocol.
>
> The device provides a simple transport for the Arm SCMI protocol[1]. The
> *S*ystem *C*ontrol and *M*anagement *I*nterface protocol allows speaking
> to system controllers that allow orchestrating things like power
> management, system state management and sensor access. The SCMI protocol
> is used on SoCs where multiple cores and co-processors need access to
> these resources.
>
<snip>
>
> OpenSynergy has a prototype implementation (without device specific
> features so far), and plans to upstream the Linux kernel driver.
Has a RFC of the kernel driver been posted yet? I'm curious on how it
Linux backend integrates with other devices.
>
> The PDF output is available at [2].
>
> [2]
> https://share.mailbox.org/ajax/share/056076e70571144f50c4ca7571144b319a1d7236dda1cd3b/1/8/MzQ/MzQvMQ
This PDF seems to include a fair number of extra devices - including an
RPMB device I'm quite interested in. Is this because you are building
from a tree with a bunch of rolled up updates?
In fact looking closer at the rendered version it seems to be missing
device id 32.
/me wonders off to look at the make tooling in the upstream repo to see
if things can be tweaked a bit.
--
Alex Bennée
---------------------------------------------------------------------
To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org
next prev parent reply other threads:[~2020-03-23 17:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200220193715.12097-1-peter.hilber@opensynergy.com>
2020-02-27 11:37 ` [virtio-comment] [PATCH v2] Add virtio SCMI device specification Peter Hilber
2020-03-17 19:20 ` [virtio-comment] [PATCH v3] " Peter Hilber
2020-03-23 17:35 ` Alex Bennée [this message]
2020-03-27 14:43 ` [virtio-comment] Re: [virtio-dev] " Alex Bennée
2020-03-27 17:19 ` Alex Bennée
2020-04-09 8:01 ` Peter Hilber
2020-04-24 8:51 ` [virtio-comment] [PATCH v4] " Peter Hilber
2020-05-13 10:48 ` [virtio-comment] " Peter Hilber
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=87blonas8y.fsf@linaro.org \
--to=alex.bennee@linaro.org \
--cc=Souvik.Chakravarty@arm.com \
--cc=Sudeep.Holla@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=peter.hilber@opensynergy.com \
--cc=virtio-comment@lists.oasis-open.org \
--cc=virtio-dev@lists.oasis-open.org \
/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