Following up on my action to send out a block diagram to show
interconnects and bus firewalls.
Let's refer to the Technical Reference Manual of the Xilinx Versal
board:
https://www.xilinx.com/support/documentation/architecture-manuals/am011-ver…
If you look for "Figure 3" at page 44 you can see a diagram
representing the interconnects. It also marks the XMPU and XPPU. XMPU
and XPPU are the two "bus firewalls" that we have. For more information
on the XMPU, see page 280.
I hope this helps. Rob, if you have any specific questions I'll try to
address them.
On Tue, 17 Nov 2020, Nathalie Chan King Choy via System-dt wrote:
> Hi all,
>
>
>
> Action items to complete prior to the call:
>
> · Stefano & Loic: send the block diagrams of ST & Xilinx systems to the System DT mailing list
>
> · Stefano: Kick off discussion on aligning the remote processor bindings
>
>
>
> Agenda:
>
> * Stefano, Loic, Rob: Continue discussion on bus firewalls in the context of system block diagrams
> * Stefano: Remote processor bindings
>
>
>
> Call scheduled based on overlapping availability of the speakers. Will record for those who can’t make it.
>
>
>
> Thanks & regards,
>
> Nathalie
>
>
>
>
>
> Meeting number (access code): 145 274 0153
>
>
>
> Meeting password: cgABNSQ$322
>
>
>
>
>
>
>
> Thursday, December 3, 2020
>
> 9:00 am | (UTC-08:00) Pacific Time (US & Canada) | 1 hr
>
>
>
>
>
>
>
> Join meeting
>
>
>
> United States Toll Free
>
> 1-844-621-3956
>
> Canada Toll Free
>
> 1-844-426-4405
>
> France Toll Free
>
> 0800-912-485
>
> United Kingdom Toll Free
>
> 08000315372
>
> Sweden Toll Free
>
> 020-033-6721
>
> India Toll Free
>
> 000-800-040-1016
>
> Global call-in numbers | Toll-free calling restrictions
>
>
>
>
>
Hi all,
Action items to complete prior to the call:
* Stefano & Loic: send the block diagrams of ST & Xilinx systems to the System DT mailing list
* Stefano: Kick off discussion on aligning the remote processor bindings
Agenda:
* Stefano, Loic, Rob: Continue discussion on bus firewalls in the context of system block diagrams
* Stefano: Remote processor bindings
Call scheduled based on overlapping availability of the speakers. Will record for those who can't make it.
Thanks & regards,
Nathalie
Meeting number (access code): 145 274 0153
Meeting password: cgABNSQ$322
Thursday, December 3, 2020
9:00 am | (UTC-08:00) Pacific Time (US & Canada) | 1 hr
Join meeting<https://xilinx.webex.com/xilinx/j.php?MTID=maf89c5997c1cca28b2d74b49f1e8c6da>
United States Toll Free
1-844-621-3956
Canada Toll Free
1-844-426-4405
France Toll Free
0800-912-485
United Kingdom Toll Free
08000315372
Sweden Toll Free
020-033-6721
India Toll Free
000-800-040-1016
Global call-in numbers<https://xilinx.webex.com/xilinx/globalcallin.php?MTID=mf8c3e8024514989f05f6…> | Toll-free calling restrictions<https://www.webex.com/pdf/tollfree_restrictions.pdf>
Hi all,
The notes from today's call can be found on the OpenAMP Wiki at:
https://github.com/OpenAMP/open-amp/wiki/System-DT-Meeting-Notes-2020#20201…
The link to the Webex recording is in the notes. I am not sure how long before the recordings expire or I will hit my storage limit, so if you need to catch up by watching the recording, please download it in the next couple weeks.
The action items are:
* Stefano & Loic: send the block diagrams of ST & Xilinx systems
* Stefano: Kick off discussion on aligning the remote processor bindings
* Stefano to send out slides & examples (DONE)
If you spoke during the call, please check for any errors or important omissions. Feel free to edit the notes in the wiki directly with any corrections.
Thanks & regards,
Nathalie C. Chan King Choy
Program Manager focused on Open Source and Community
Hi all,
I am attaching the slides that I showed during the last System Device
Tree call about the Firewall and Interconnects bindings. I am also
attaching the RemoteProc slides and examples I started to discuss at the
end of the meeting. We'll continue the RemoteProc discussion next time.
Cheers,
Stefano
Hi all,
Just a reminder that the System DT call begins in just under 1 hour (9am Pacific Time, 4pm UTC). Joining details below, if you don't have the calendar invitation.
-Nathalie
Hi all,
Agenda:
* Loic & Stefano have aligned on their thinking with regards to this action item, so we will discuss:
Xilinx and ST to discuss interconnect binding, considering that it could be expanded beyond QoS, and review Rob's earlier feedback to Benjamin on pin control.
* I believe the openamp-rp working group is looking to get Rob's inputs on the remote processor bindings discussion.
Notes from the previous calls can be found at: https://github.com/OpenAMP/open-amp/wiki/System-DT-Meeting-Notes-2020
Best regards,
Nathalie
Meeting number (access code): 145 595 0396
Meeting password: PMhPW739CH@
Thursday, October 22, 2020
9:00 am | (UTC-07:00) Pacific Time (US & Canada) | 1 hr
Join meeting<https://xilinx.webex.com/xilinx/j.php?MTID=mc71c052daa30068e09f852fbb378eda5>
Join by phone
Canada toll free 1-844-426-4405
France toll free 0800-912-485
India toll free 000-800-040-1016
Sweden toll free 020-033-6721
UK toll free 08000315372
United States Toll Free 1-844-621-3956
Global call-in numbers<https://xilinx.webex.com/xilinx/globalcallin.php?MTID=m370fae0984a8792a3592…> | Toll-free calling restrictions<https://www.webex.com/pdf/tollfree_restrictions.pdf>
Hi all,
Agenda:
* Loic & Stefano have aligned on their thinking with regards to this action item, so we will discuss:
Xilinx and ST to discuss interconnect binding, considering that it could be expanded beyond QoS, and review Rob's earlier feedback to Benjamin on pin control.
* I believe the openamp-rp working group is looking to get Rob's inputs on the remote processor bindings discussion.
Notes from the previous calls can be found at: https://github.com/OpenAMP/open-amp/wiki/System-DT-Meeting-Notes-2020
Best regards,
Nathalie
Meeting number (access code): 145 595 0396
Meeting password: PMhPW739CH@
Thursday, October 22, 2020
9:00 am | (UTC-07:00) Pacific Time (US & Canada) | 1 hr
Join meeting<https://xilinx.webex.com/xilinx/j.php?MTID=mc71c052daa30068e09f852fbb378eda5>
Join by phone
Canada toll free 1-844-426-4405
France toll free 0800-912-485
India toll free 000-800-040-1016
Sweden toll free 020-033-6721
UK toll free 08000315372
United States Toll Free 1-844-621-3956
Global call-in numbers<https://xilinx.webex.com/xilinx/globalcallin.php?MTID=m370fae0984a8792a3592…> | Toll-free calling restrictions<https://www.webex.com/pdf/tollfree_restrictions.pdf>
On Tue, 1 Sep 2020, François Ozog via System-dt wrote:
> On Tue, 1 Sep 2020 at 14:49, Tomas Evensen <tomase(a)xilinx.com> wrote:
> Here are some brief notes from the meeting.
>
> If nothing else as a showcase on how much we miss Nathalie when she is on vacation 😉
>
> Krzysztof Kepa – GE
> Mathieu Poirier – Linaro
> Etsam Anjum – Mentor
> Anrnoud Pouliquen – ST
> Loic Pallardy - ST
> Suman Anna - TI
> Dan Milea – Wind River
> Mark Dapoz – Wind River
> Tomas Evensen – Xilinx
> Stefano Stabellini – Xilinx
> Bruce Ashfield – Xilinx
> Ed Mooring – Xilinx
> Ben Levinsky - Xilinx
>
> Stefano went through slides.
> Overall idea:
>
> 1. Specify remoteproc channels with minimal information in System-DT in a way that is as common as possible for all vendors.
> In particular, we are avoiding to have to specify the same memory regions in more than one place. A resource group is specially
> marked to contain most information.
> 2. Use Lopper to create the vendor specific remoteproc specification
> Generating reserved-memory, etc. information that has duplicate information.
> For the time being, no plans to unify the vendor specific information that goes into the traditional device tree for Linux
> 3. Later (or in parallel), but without making it a gating item, start discussions on what we can do to unify the vendor
> specific information in the traditional DT
>
> Discussion about how TI and ST might generate their specific information from this specification.
>
> Stefano to send out examples and slides.
> Ben: Xilinx backend to Lopper is upstreamed and available as an example. Might change as upstreaming continues.
>
> Question:
> * How do we configure VirtIO?
>
> Could you describe more the VirtIO question so that relationship with Linaro project Stratos is assessed?
I think this point refers to various vdev<x> buffers described under
/reserved-memory which are linked from RemoteProc. From the Xilinx
bindings:
reserved-memory {
#address-cells = <1>;
#size-cells = <1>;
ranges;
rpu0vdev0vring0: rpu0vdev0vring0@3ed40000 {
compatible = "xilinx,openamp-ipc-1.0";
no-map;
reg = <0x3ed40000 0x4000>;
};
rpu0vdev0vring1: rpu0vdev0vring1@3ed44000 {
compatible = "xilinx,openamp-ipc-1.0";
no-map;
reg = <0x3ed44000 0x4000>;
};
rpu0vdev0buffer: rpu0vdev0buffer@3ed48000 {
compatible = "xilinx,openamp-ipc-1.0";
no-map;
reg = <0x3ed48000 0x100000>;
};
rproc_0_reserved: rproc@3ed000000 {
compatible = "xilinx,openamp-ipc-1.0";
no-map;
reg = <0x3ed00000 0x40000>;
};
};
Here are some brief notes from the meeting.
If nothing else as a showcase on how much we miss Nathalie when she is on vacation 😉
Krzysztof Kepa – GE
Mathieu Poirier – Linaro
Etsam Anjum – Mentor
Anrnoud Pouliquen – ST
Loic Pallardy - ST
Suman Anna - TI
Dan Milea – Wind River
Mark Dapoz – Wind River
Tomas Evensen – Xilinx
Stefano Stabellini – Xilinx
Bruce Ashfield – Xilinx
Ed Mooring – Xilinx
Ben Levinsky - Xilinx
Stefano went through slides.
Overall idea:
1. Specify remoteproc channels with minimal information in System-DT in a way that is as common as possible for all vendors.
In particular, we are avoiding to have to specify the same memory regions in more than one place. A resource group is specially marked to contain most information.
2. Use Lopper to create the vendor specific remoteproc specification
Generating reserved-memory, etc. information that has duplicate information.
For the time being, no plans to unify the vendor specific information that goes into the traditional device tree for Linux
3. Later (or in parallel), but without making it a gating item, start discussions on what we can do to unify the vendor specific information in the traditional DT
Discussion about how TI and ST might generate their specific information from this specification.
Stefano to send out examples and slides.
Ben: Xilinx backend to Lopper is upstreamed and available as an example. Might change as upstreaming continues.
Question:
* How do we configure VirtIO?
From: nathalie(a)xilinx.com
When: 8:00 AM - 9:00 AM August 31, 2020
Subject: [System-dt] System DT call: OpenAMP bindings
Location: webex
CAUTION: This message has originated from an External Source. Please use proper judgment and caution when opening attachments, clicking links, or responding to this email.
Hi all,
The OpenAMP-remoteproc working group is looking forward to discuss OpenAMP bindings with the System DT working group & all others interested in System DT.
Best regards,
Nathalie C. Chan King Choy
Program Manager focused on Open Source & Community
Meeting number (access code): 145 853 2028
Meeting password: NgTwf4r8R$3
Monday, August 31, 2020
8:00 am | (UTC-07:00) Pacific Time (US & Canada) | 1 hr
Join meeting<https://xilinx.webex.com/xilinx/j.php?MTID=mcd4ad9bca009dfef38671c26d5a1d301>
Canada toll free 1-844-426-4405
France toll free 0800-912-485
India toll free 000-800-040-1016
Sweden toll free 020-033-6721
UK toll free 08000315372
United States Toll Free 1-844-621-3956
Global call-in numbers<https://xilinx.webex.com/xilinx/globalcallin.php?MTID=m370fae0984a8792a3592…> | Toll-free calling restrictions<https://www.webex.com/pdf/tollfree_restrictions.pdf>
This email and any attachments are intended for the sole use of the named recipient(s) and contain(s) confidential information that may be proprietary, privileged or copyrighted under applicable law. If you are not the intended recipient, do not read, copy, or forward this email message or any attachments. Delete this email message and any attachments immediately.
On Mon, 31 Aug 2020, Bjorn Andersson via System-dt wrote:
> On Mon 31 Aug 16:04 UTC 2020, Tomas Evensen via System-dt wrote:
>
> > Here are some brief notes from the meeting.
> >
> > If nothing else as a showcase on how much we miss Nathalie when she is on vacation ????
> >
> > Krzysztof Kepa – GE
> > Mathieu Poirier – Linaro
> > Etsam Anjum – Mentor
> > Anrnoud Pouliquen – ST
> > Loic Pallardy - ST
> > Suman Anna - TI
> > Dan Milea – Wind River
> > Mark Dapoz – Wind River
> > Tomas Evensen – Xilinx
> > Stefano Stabellini – Xilinx
> > Bruce Ashfield – Xilinx
> > Ed Mooring – Xilinx
> > Ben Levinsky - Xilinx
> >
> > Stefano went through slides.
> > Overall idea:
> >
> > 1. Specify remoteproc channels with minimal information in System-DT in a way that is as common as possible for all vendors.
> > In particular, we are avoiding to have to specify the same memory regions in more than one place. A resource group is specially marked to contain most information.
> > 2. Use Lopper to create the vendor specific remoteproc specification
> > Generating reserved-memory, etc. information that has duplicate information.
> > For the time being, no plans to unify the vendor specific information that goes into the traditional device tree for Linux
> > 3. Later (or in parallel), but without making it a gating item, start discussions on what we can do to unify the vendor specific information in the traditional DT
>
> Can anyone point me to some examples of vendor specific information
> referred to here?
Some of the other attendees might have better examples than this. The
ones I was mentioning this morning are the "mboxes" and "mbox-names"
properties you can see in the "output.txt" example. Also the memory
regions listed under the "memory-region" property and under
"reserved-memory".
On Mon, 31 Aug 2020, Tomas Evensen via System-dt wrote:
> Stefano to send out examples and slides
I am attaching the slides and examples, where:
- input.txt is the system device tree snippet, input to lopper
- output.txt is the traditional device tree snipper, output from lopper