From: sashiko-bot@kernel.org
To: "Haruka Kuze" <harukak@zohomail.eu>
Cc: virtualization@lists.linux.dev,
"Michael S. Tsirkin" <mst@redhat.com>,
"Eugenio Perez" <eperezma@redhat.com>
Subject: Re: [PATCH v3 2/2] rpmb: add a virtio RPMB device driver
Date: Fri, 30 Oct 2026 13:38:40 +0000 [thread overview]
Message-ID: <sashiko-outbox-191075@kernel.org> (raw)
In-Reply-To: <20261030133000.24147-3-harukak@zohomail.eu>
> From: Haruka Kuze <harukak@zohomail.eu>
>
> No driver exists for virtio-rpmb devices (virtio ID 28), so OP-TEE
> running in a guest can not use them.
>
> This registers the virtio-rpmb devices found with the RPMB sub-system.
> Each request is done in one transfer on request queue, and for key
> programming and data writing a result read frame is appended so that
> the device can return the result.
>
> These frames are copied since the caller's buffers are not always
> usable for DMA.
>
> These frames follow the emmc definition, so that the device is
> registered as RPMB_TYPE_EMMC. The device has no identifier of own, so
> that a fixed dev_id is used for the key derivation for the device.
>
> Based on the virtio-rpmb driver in Alex Bennée's RPMB series.
>
> Link: https://lore.kernel.org/all/20220405093759.1126835-4-alex.bennee@linaro.org/
> Signed-off-by: Haruka Kuze <harukak@zohomail.eu>
Sashiko has reviewed this patch and found no issues.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261030133000.24147-1-harukak@zohomail.eu?part=2
prev parent reply other threads:[~2026-10-30 13:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-30 13:29 [PATCH v3 0/2] rpmb: add virtio RPMB driver Haruka Kuze
2026-10-30 13:29 ` [PATCH v3 1/2] rpmb: stop the routing after unregister Haruka Kuze
2026-10-30 13:40 ` sashiko-bot
2026-10-30 13:30 ` [PATCH v3 2/2] rpmb: add a virtio RPMB device driver Haruka Kuze
2026-10-30 13:38 ` sashiko-bot [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=sashiko-outbox-191075@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=eperezma@redhat.com \
--cc=harukak@zohomail.eu \
--cc=mst@redhat.com \
--cc=sashiko-reviews@lists.linux.dev \
--cc=virtualization@lists.linux.dev \
/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