← Prev in month ← Prev in thread

Clarifying the language of VIRTIO_RPMB_REQ_PROGRAM_KEY

From
Alex BennÃe <>
Date
2020-06-12T15:40:57+00:00
ID
Thread
Clarifying the language of VIRTIO_RPMB_REQ_PROGRAM_KEY
Hi,

In the virtio-rpmb part of the spec it says:

  The operation of a virtio RPMB device is driven by the requests placed on the virtqueue.
    The type of request can be program key (VIRTIO_RPMB_REQ_PROGRAM_KEY),
    get write counter (VIRTIO_RPMB_REQ_GET_WRITE_COUNTER),
    write (VIRTIO_RPMB_REQ_DATA_WRITE), and read (VIRTIO_RPMB_REQ_DATA_READ).
    A program key or write request can also combine with a
    result read (VIRTIO_RPMB_REQ_RESULT_READ) for a returned result.

but later on:

  VIRTIO_RPMB_REQ_RESULT_READ
     requests for a returned result. It is used following with VIRTIO_RPMB_REQ_PROGRAM_KEY or VIRTIO_RPMB_REQ_DATA_WRITE request types for a returned result in one or multiple RPMB frames. If itâs not requested, the device will not return result frame to the driver.

So which is it? I can't quite see how a VIRTIO_RPMB_REQ_RESULT_READ can
be combined with the other requests because they are not overlapping
bits so maybe the working should be:

  A program key or write request can be followed by a result read (VIRTIO_RPMB_REQ_RESULT_READ) for a returned result.

Is that is what is intended?

-- 
Alex BennÃe
← Prev in month ← Prev in thread