[PATCH v2 2/2] drivers: gpio: add virtio-gpio guest driver
alex.bennee at linaro.org
Tue Apr 13 12:07:58 BST 2021
"Enrico Weigelt, metux IT consult" <info at metux.net> writes:
> On 04.12.20 04:35, Jason Wang wrote:
>> Is the plan to keep this doc synced with the one in the virtio
> Yes, of course. I'm still in progress of doing the beaurocratic stuff w/
> virtio-tc folks (ID registration, ...) - yet have to see whether they
> wanna add it to their spec documents ...
> BTW: if you feel, sometings not good w/ the current spec, please raise
> your voice now.
>> I think it's better to use u8 ot uint8_t here.Git grep told me the
>> former is more popular under Documentation/.
> thx, I'll fix that
>>> +- for version field currently only value 1 supported.
>>> +- the line names block holds a stream of zero-terminated strings,
>>> + holding the individual line names.
>> I'm not sure but does this mean we don't have a fixed length of config
>> space? Need to check whether it can bring any trouble to
> Yes, it depends on how many gpio lines are present and how much space
> their names take up.
> A fixed size would either put unpleasent limits on the max number of
> lines or waste a lot space when only few lines present.
> Not that virtio-gpio is also meant for small embedded workloads running
> under some hypervisor.
>>> +- unspecified fields are reserved for future use and should be zero.
>>> +Virtqueues and messages:
>>> +- Queue #0: transmission from host to guest
>>> +- Queue #1: transmission from guest to host
>> Virtio became more a popular in the area without virtualization. So I
>> think it's better to use "device/driver" instead of "host/guest" here.
> Good point. But I'd prefer "cpu" instead of "driver" in that case.
I think you are going to tie yourself up in knots if you don't move this
to the OASIS spec. The reason being the VirtIO spec has definitions for
what a "Device" and a "Driver" is that are clear and unambiguous. The
upstream spec should be considered the canonical source of truth for any
implementation (Linux or otherwise).
By all means have the distilled documentation for the driver in the
kernel source tree but trying to upstream an implementation before
starting the definition in the standard is a little back to front IMHO*.
* that's not to say these things can't be done in parallel as the spec
is reviewed and worked on and the kinks worked out but you want the
final order of upstreaming to start with the spec.
More information about the linux-riscv