Hello,
This series proposes basic DT bindings for FFA devices, and sets up the of_node
and dma_configure() callback for the devices.
Viresh Kumar (3):
dt-bindings: firmware: Add bindings for ARM FFA
firmware: arm_ffa: Setup of_node for ffa devices
firmware: arm_ffa: Provide .dma_configure()
.../devicetree/bindings/firmware/arm,ffa.yaml | 75 +++++++++++++++++++
drivers/firmware/arm_ffa/bus.c | 39 ++++++++++
2 files changed, 114 insertions(+)
create mode 100644 Documentation/devicetree/bindings/firmware/arm,ffa.yaml
--
2.31.1.272.g89b43f80a514
Hello,
I would like send this upstream next week, any feedback would be welcome before
that.
Thanks.
Viresh Kumar (2):
dt-bindings: firmware: Add bindings for ARM FFA
firmware: arm_ffa: Setup of_node for ffa devices
.../devicetree/bindings/firmware/arm,ffa.yaml | 75 +++++++++++++++++++
drivers/firmware/arm_ffa/bus.c | 30 ++++++++
2 files changed, 105 insertions(+)
create mode 100644 Documentation/devicetree/bindings/firmware/arm,ffa.yaml
--
2.31.1.272.g89b43f80a514
Hi Guys,
Happy new Year everyone.
I am travelling this week so i will not participate to the meeting but i pushed some changes to the specification in Alex Github mirror.
Those are introducing the error message in virtio-msg and some attempt to define the first bus messages.
The push contains some TODOs for which i would need some answers or ideas so feel free to look and tell me.
Also i wrote down a pending request to get an INT back when a notification is sent in case it cannot be sent and we will need to discuss it as adding an answer to EVENT messages would make those message synchronous which might not be the right idea. In the Bus to Transport interface definition of the google document, I did include an int return code when a message is sent by the transport and this could be used to signal back an error easily where posting a generated message back could introduce more complexity. This is just some thinking on my side and happy to discuss this in 2 weeks or by mail before that.
Regards
Bertrand
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
Hi everyone,
I hope all interested parties are part of the previously created list.
Based on the discussions we had previously, where I was struggling to find a
setup where I can test virtio-msg with FFA (or something more realistic than
hacked-up MMIO), I decided to go ahead and make use of Bertrand's Xen patches
with Linux based host and guest VMs.
I now have a working setup with Bertrand's Xen patches, where we can do FFA I
was able to reuse my earlier setup (where we tested I2C with MMIO traps) based
virtio communication guest and host kernels. I have created another page [1]
(similar to previous one) for curious ones to replicate it.
This would work just fine for Vsock as well, which I tested earlier with the
backend from vhost-device crate.
--
viresh
[1] https://linaro.atlassian.net/wiki/spaces/HVAC/pages/29657792513/2024-11+ker…
Hi All,
I've forked the VirtIO specification into a Linaro repo for us to work
on it:
https://github.com/Linaro/virtio-msg-spec
I've set the default branch to "virtio-msg-alpha" with the intention of
re-basing and squashing commits before we post to the list.
Once PRs are merged it triggers a rebuild of the draft spec which you
can find in:
https://github.com/Linaro/virtio-msg-spec/releases
Hopefully the working-draft just gets overwritten each time.
--
Alex Bennée
Virtualisation Tech Lead @ Linaro
All,
Today's meeting was canceled. I did it in an outlook friendly manner, but
I have been told some calendars still show the meeting.
Next meeting will be in two weeks.
Thanks,
Bill
Hi Everyone,
Enclosed you will find a first draft of a design document for the virtio message transport and the bus concept.
I took the content from the Google doc and turn it into a markdown and i remove the parts not really needed and reoganized a bit.
I also modified the tables to make them easier to read in text format and split the messages format table in several chapters per message.
This document is not intended to be in a form compatible with the virtio specification.
This is a first draft and any comment is welcome.
Cheers
Bertrand
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
