[virtio-comment] Re: [virtio-dev] [PATCH v3] Add virtio SCMI device specification

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: [virtio-comment] Re: [virtio-dev] [PATCH v3] Add virtio SCMI device specification
Date: Fri, 27 Mar 2020 14:43:37 +0000	[thread overview]
Message-ID: <87h7y9n9ie.fsf@linaro.org> (raw)
In-Reply-To: <87blonas8y.fsf@linaro.org>

Alex Bennée <alex.bennee@linaro.org> writes:

> 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?

I obviously failed to appropriately grep the existing spec closely
enough :-/

> /me wonders off to look at the make tooling in the upstream repo to see
> if things can be tweaked a bit.

I went ahead and suggested some tweaks anyway.

-- 
Alex Bennée

This publicly archived list offers a means to provide input to the
OASIS Virtual I/O Device (VIRTIO) TC.

In order to verify user consent to the Feedback License terms and
to minimize spam in the list archive, subscription is required
before posting.

Subscribe: virtio-comment-subscribe@lists.oasis-open.org
Unsubscribe: virtio-comment-unsubscribe@lists.oasis-open.org
List help: virtio-comment-help@lists.oasis-open.org
List archive: https://lists.oasis-open.org/archives/virtio-comment/
Feedback License: https://www.oasis-open.org/who/ipr/feedback_license.pdf
List Guidelines: https://www.oasis-open.org/policies-guidelines/mailing-lists
Committee: https://www.oasis-open.org/committees/virtio/
Join OASIS: https://www.oasis-open.org/join/