Hi all,
On Monday, Christopher and Daniel will talk about their Device Tree
bindings for HyperLaunch, which has very close similarities to System
Device Tree domains.
We'll also discuss the topic of hierarchical domains and Bruce will
present the latest Lopper updates.
On Thu, 6 May 2021, Nathalie Chan King Choy via System-dt wrote:
> Hi all,
>
>
>
> Calling for agenda items for next week’s System Device Tree call.
>
>
>
> Best regards,
>
> Nathalie
>
>
>
> -----Original Appointment-----
> From: Nathalie Chan King Choy
> Sent: Monday, April 26, 2021 1:52 PM
> To: Nathalie Chan King Choy; 'system-dt(a)lists.openampproject.org'
> Cc: boot-architecture(a)lists.linaro.org; Tony McDowell; Joakim Bech; Tomas Evensen; Loic PALLARDY; Sudeep Holla; Kepa, Krzysztof (GE
> Research, US); Bruce Ashfield; marti.bolivar(a)nordicsemi.no; etoillon(a)kalrayinc.com; Raghuraman, Arvind; Stefano Stabellini; Ed T. Mooring
> Subject: System Device Tree call - May 2021
> When: Monday, May 10, 2021 9:00 AM-10:00 AM (UTC-08:00) Pacific Time (US & Canada).
> Where: webex
>
>
>
> Hi all,
>
>
>
> Notes & link to the recording from the last System DT call can be found at
> https://github.com/OpenAMP/open-amp/wiki/System-Device-Tree-Meeting-Notes-2…
>
>
>
> If you missed the LVC21 Device Tree State of the Union: https://connect.linaro.org/resources/lvc21/lvc21-108/
>
> Or the LVC21 Device Tree BOF: https://connect.linaro.org/resources/lvc21/lvc21-112
>
>
>
> Action items from last call:
>
> * Loic: Check HW lock bindings
> * Stefano: Will try to combine the 2 properties into 1 & come up with some examples.
>
>
>
> Call scheduled based on overlapping availability of the speakers. Will record for those who can’t make it.
>
>
>
> Thanks & regards,
>
> Nathalie
>
>
>
Hi all,
Calling for agenda items for next week's System Device Tree call.
Best regards,
Nathalie
-----Original Appointment-----
From: Nathalie Chan King Choy
Sent: Monday, April 26, 2021 1:52 PM
To: Nathalie Chan King Choy; 'system-dt(a)lists.openampproject.org'
Cc: boot-architecture(a)lists.linaro.org; Tony McDowell; Joakim Bech; Tomas Evensen; Loic PALLARDY; Sudeep Holla; Kepa, Krzysztof (GE Research, US); Bruce Ashfield; marti.bolivar(a)nordicsemi.no; etoillon(a)kalrayinc.com; Raghuraman, Arvind; Stefano Stabellini; Ed T. Mooring
Subject: System Device Tree call - May 2021
When: Monday, May 10, 2021 9:00 AM-10:00 AM (UTC-08:00) Pacific Time (US & Canada).
Where: webex
Hi all,
Notes & link to the recording from the last System DT call can be found at https://github.com/OpenAMP/open-amp/wiki/System-Device-Tree-Meeting-Notes-2…
If you missed the LVC21 Device Tree State of the Union: https://connect.linaro.org/resources/lvc21/lvc21-108/
Or the LVC21 Device Tree BOF: https://connect.linaro.org/resources/lvc21/lvc21-112
Action items from last call:
* Loic: Check HW lock bindings
* Stefano: Will try to combine the 2 properties into 1 & come up with some examples.
Call scheduled based on overlapping availability of the speakers. Will record for those who can't make it.
Thanks & regards,
Nathalie
Hi all,
The notes from today's System DT call are posted at https://github.com/OpenAMP/open-amp/wiki/System-Device-Tree-Meeting-Notes-2…, along with the recording link. If you spot any errors or important omissions, please make the fix directly in the wiki page (you just have to be logged in to GitHub).
Action items:
* Loic: Check HW lock bindings
* Stefano: Will try to combine the 2 properties into 1 & come up with some examples.
Thanks & have a great weekend,
Nathalie
Hi all,
Thank you for joining the meeting today. I am attaching here the two
sets of slides I showed in html format.
Cheers,
Stefano
On Wed, 27 Jan 2021, Stefano Stabellini via System-dt wrote:
> Hi Nathalie,
>
> Thank you for the reminder.
>
> I would like to continue the discussion on the bus firewall bindings. I
> sent an email to the list with the summary of the past discussions.
>
> I would also like to cover again the remoteproc bindings and they get
> generated from system device tree.
>
> If we have time, we can discuss how system device tree aligns with
> ffa partitions definitions.
>
> Cheers,
>
> Stefano
>
>
> On Thu, 21 Jan 2021, Nathalie Chan King Choy via System-dt wrote:
> > Hi all,
> >
> >
> >
> > Calling for agenda items for the Jan 29 System DT call. Please send me your topics.
> >
> >
> >
> > Thanks & regards,
> >
> > Nathalie
> >
> >
> >
> > -----Original Appointment-----
> > From: Nathalie Chan King Choy
> > To: Nathalie Chan King Choy; 'system-dt(a)lists.openampproject.org'
> > Subject: System DT call - January 2021
> > When: Friday, January 29, 2021 8:00 AM-9:00 AM (UTC-08:00) Pacific Time (US & Canada).
> > Where: Webex
> >
> >
> >
> > Hi all,
> >
> >
> >
> > Happy New Year!
> >
> >
> >
> > Notes & recording link from the previous System DT call can be found at
> > https://github.com/OpenAMP/open-amp/wiki/System-DT-Meeting-Notes-2020#20201…
> >
> >
> >
> > Action items to complete prior to the call:
> >
> > * Stefano: Write-up and continue discussion on list
> >
> >
> >
> > Call scheduled based on overlapping availability of the speakers. Will record for those who can’t make it.
> >
> >
> >
> > Thanks & regards,
> >
> > Nathalie
> >
> >
> >
> >
> >
> > Friday, January 29, 2021
> >
> > 8:00 am | (UTC-08:00) Pacific Time (US & Canada) | 1 hr
> >
> >
> >
> >
> >
> >
> >
> > Join meeting
> >
> >
> >
> >
> >
> > More ways to join:
> >
> > Join from the meeting link
> >
> > https://xilinx.webex.com/xilinx/j.php?MTID=m2910f54b9c95e96cc2baf2bd999949d4
> >
> >
> >
> >
> >
> >
> >
> > Join by meeting number
> >
> > Meeting number (access code): 145 107 1153
> >
> > Meeting password: pUVgDpD@832
> >
> >
> >
> >
> >
> >
> >
> > Join by phone
> >
> > 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
> >
> >
> >
> >
> >
> --
> System-dt mailing list
> System-dt(a)lists.openampproject.org
> https://lists.openampproject.org/mailman/listinfo/system-dt
>
Hi Nathalie,
Thank you for the reminder.
I would like to continue the discussion on the bus firewall bindings. I
sent an email to the list with the summary of the past discussions.
I would also like to cover again the remoteproc bindings and they get
generated from system device tree.
If we have time, we can discuss how system device tree aligns with
ffa partitions definitions.
Cheers,
Stefano
On Thu, 21 Jan 2021, Nathalie Chan King Choy via System-dt wrote:
> Hi all,
>
>
>
> Calling for agenda items for the Jan 29 System DT call. Please send me your topics.
>
>
>
> Thanks & regards,
>
> Nathalie
>
>
>
> -----Original Appointment-----
> From: Nathalie Chan King Choy
> To: Nathalie Chan King Choy; 'system-dt(a)lists.openampproject.org'
> Subject: System DT call - January 2021
> When: Friday, January 29, 2021 8:00 AM-9:00 AM (UTC-08:00) Pacific Time (US & Canada).
> Where: Webex
>
>
>
> Hi all,
>
>
>
> Happy New Year!
>
>
>
> Notes & recording link from the previous System DT call can be found at
> https://github.com/OpenAMP/open-amp/wiki/System-DT-Meeting-Notes-2020#20201…
>
>
>
> Action items to complete prior to the call:
>
> * Stefano: Write-up and continue discussion on list
>
>
>
> Call scheduled based on overlapping availability of the speakers. Will record for those who can’t make it.
>
>
>
> Thanks & regards,
>
> Nathalie
>
>
>
>
>
> Friday, January 29, 2021
>
> 8:00 am | (UTC-08:00) Pacific Time (US & Canada) | 1 hr
>
>
>
>
>
>
>
> Join meeting
>
>
>
>
>
> More ways to join:
>
> Join from the meeting link
>
> https://xilinx.webex.com/xilinx/j.php?MTID=m2910f54b9c95e96cc2baf2bd999949d4
>
>
>
>
>
>
>
> Join by meeting number
>
> Meeting number (access code): 145 107 1153
>
> Meeting password: pUVgDpD@832
>
>
>
>
>
>
>
> Join by phone
>
> 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,
Calling for agenda items for the Jan 29 System DT call. Please send me your topics.
Thanks & regards,
Nathalie
-----Original Appointment-----
From: Nathalie Chan King Choy
To: Nathalie Chan King Choy; 'system-dt(a)lists.openampproject.org'
Subject: System DT call - January 2021
When: Friday, January 29, 2021 8:00 AM-9:00 AM (UTC-08:00) Pacific Time (US & Canada).
Where: Webex
Hi all,
Happy New Year!
Notes & recording link from the previous System DT call can be found at https://github.com/OpenAMP/open-amp/wiki/System-DT-Meeting-Notes-2020#20201…
Action items to complete prior to the call:
* Stefano: Write-up and continue discussion on list
Call scheduled based on overlapping availability of the speakers. Will record for those who can't make it.
Thanks & regards,
Nathalie
Friday, January 29, 2021
8:00 am | (UTC-08:00) Pacific Time (US & Canada) | 1 hr
Join meeting<https://xilinx.webex.com/xilinx/j.php?MTID=m2910f54b9c95e96cc2baf2bd999949d4>
More ways to join:
Join from the meeting link
https://xilinx.webex.com/xilinx/j.php?MTID=m2910f54b9c95e96cc2baf2bd999949d4
Join by meeting number
Meeting number (access code): 145 107 1153
Meeting password: pUVgDpD@832
Join by phone
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=m2e0126266a5b83559b25…> | Toll-free calling restrictions<https://www.webex.com/pdf/tollfree_restrictions.pdf>
Hi all,
I am bringing the System Device Tree discussion to the mailing list so
that we can dig deeper into the details. Let's start by providing the
background and reference material from previous discussions. Below is a
transcript of the slides and diagram I showed during the calls.
The notes and recording from the last meeting are here:
https://github.com/OpenAMP/open-amp/wiki/System-DT-Meeting-Notes-2020#20201…
The paragraphs below up until "Interconnect Bindings" describe the
bus-firewall proposal.
Last time the general agreement was that interconnects and bus-firewalls
are different enough that reusing the interconnects bindings for
bus-firewalls doesn't seem to be the best way forward.
The possibility of reusing IOMMU bindings for bus-firewalls was
discussed toward the end of the meeting. However, IOMMU bindings
currently do not have a way to to describe the slave side, which is
covered by the "firewall" property in the bus-firewall proposal.
(bus-master-is is similar to the iommu property.)
Cheers,
Stefano
# Background
See "Figure 4: at
https://www.xilinx.com/support/documentation/architecture-manuals/am011-ver…
for a diagram representing bus-firewalls, see XMPU and XPPU and how they
differ from interconnects.
See the existing interconnect binding at
Documentation/devicetree/bindings/interconnect/interconnect.txt
# Bus-Firewalls in Device Tree: Goals
- describe firewall controllers
- describe which device is protected by which controller
- describe a new ID space to configure the firewalls
- describe domains-based firewall configurations in system device tree
# Firewall Controllers
Nodes describing the programmable controllers. There can be multiple
controllers in a system. We thought of using a #firewall-cells property
for firewall-specific extra information. It could be zero.
Each device protected by a firewall has a firewall property to link to
the controller that protects accesses *to the device MMIO regions*.
Example:
ctrl0: firewall@5c007000 {
compatible = "st,stm32-etzpc";
reg = <0x5c007000 0x400>;
#firewall-cells = <2>;
status = "okay";
};
/* ctrl0 protects accesses to foo */
foo: foo@0 {
firewall-names = "default", "setting1";
firewall = <&ctrl0 1 2>;
};
# Bus Master IDs
Bus mastering devices are identified by firewalls using IDs. Their
transactions are marked with a device ID. These IDs are used to
configure bus-firewalls.
Let's call these IDs "Bus Master IDs" and advertise them on device
tree using a new property: bus-master-id. They could be different per
firewall controller.
Example:
foo: foo@0 {
bus-master-id = <&ctrl0 0x12>;
# System Device Tree Hardware Description Example
amba_xppu: indirect-bus@1 {
compatible = "indirect-bus";
#address-cells = <0x2>;
#size-cells = <0x2>;
lpd_xppu: xppu@ff990000 {
compatible = "xlnx,xppu"
#firewall-cells = <0x0>;
reg = <0x0 0xff990000 0x0 0x1000>;
};
pmc_xppu: xppu@f1310000 {
compatible = "xlnx,xppu"
#firewall-cells = <0x0>;
reg = <0x0 0xf1310000 0x0 0x1000>;
};
};
cpus_r5: cpus-cluster@0 {
#address-cells = <0x1>;
#size-cells = <0x0>;
#cpus-mask-cells = <0x1>;
compatible = "cpus,cluster";
bus-master-id = <&lpd_xppu 0x0 &pmc_xppu 0x0 &lpd_xppu 0x1 &pmc_xppu 0x1>;
};
amba {
ethernet0: ethernet@ff0c0000 {
bus-master-id = <&lpd_xppu 0x234 &pmc_xppu 0x234>;
firewall = <&lpd_xppu>;
};
can0: can@ff060000 {
firewall = <&lpd_xppu>;
};
mmc0: sdhci@f1050000 {
bus-master-id = <&lpd_xppu 0x243 &pmc_xppu 0x243>;
firewall = <&pmc_xppu>;
};
serial0: serial@ff000000 {
firewall = <&lpd_xppu>;
};
};
# Interconnect Bindings
>From Documentation/devicetree/bindings/interconnect/interconnect.txt:
snoc: interconnect@580000 {
compatible = "qcom,msm8916-snoc";
#interconnect-cells = <1>;
reg = <0x580000 0x14000>;
clock-names = "bus_clk", "bus_a_clk";
clocks = <&rpmcc RPM_SMD_SNOC_CLK>,
<&rpmcc RPM_SMD_SNOC_A_CLK>;
};
sdhci@7864000 {
...
interconnects = <&pnoc MASTER_SDCC_1 &bimc SLAVE_EBI_CH0>;
interconnect-names = "sdhc-mem";
};
# Interconnect Bindings vs Firewall Bindings
- Similar concepts
- Firewall controller and Interconnect controller are separate hardware blocks
- how to distinguish between the two controllers?
- QoS and firewalls are configured independently
- Using Interconnect Bindings for Firewalls
- the firewall property is *missing*
- there is no distinction between a device as bus master or as slave
- we need a way to describe firewall interactions as master and as slave
Bus firewalls description example using the interconnect bindings:
amba_xppu: indirect-bus@1 {
compatible = "indirect-bus";
#address-cells = <0x2>;
#size-cells = <0x2>;
lpd_xppu: xppu@ff990000 {
compatible = "xlnx,xppu"
#interconnect-cells = <0x0>;
reg = <0x0 0xff990000 0x0 0x1000>;
};
pmc_xppu: xppu@f1310000 {
compatible = "xlnx,xppu"
#interconnect-cells = <0x0>;
reg = <0x0 0xf1310000 0x0 0x1000>;
};
};
amba {
ethernet0: ethernet@ff0c0000 {
interconnects = <&lpd_xppu 0x234 &pmc_xppu 0x234>;
firewall = <&lpd_xppu>; // XXX
};
can0: can@ff060000 {
firewall = <&lpd_xppu>; // XXX
};
mmc0: sdhci@f1050000 {
interconnects = <&lpd_xppu 0x243 &pmc_xppu 0x243>;
firewall = <&pmc_xppu>; // XXX
};
serial0: serial@ff000000 {
firewall = <&lpd_xppu>; // XXX
};
};
# Interconnect Bindings for Bus Firewalls
- Reuse the same controller for both QoS and Firewall configurations
- Add two new consumer properties
- interconnects-master (and #interconnect-master-cells)
- interconnects-slave (and #interconnect-slave-cells)
- Specify both master and slave firewall interactions
- Keep the QoS data and Firewall data separately
Example:
amba_xppu: indirect-bus@1 {
compatible = "indirect-bus";
#address-cells = <0x2>;
#size-cells = <0x2>;
lpd_xppu: xppu@ff990000 {
compatible = "xlnx,xppu"
#interconnect-cells = <0x1>;
#interconnect-master-cells = <0x1>;
#interconnect-slave-cells = <0x0>;
reg = <0x0 0xff990000 0x0 0x1000>;
};
pmc_xppu: xppu@f1310000 {
compatible = "xlnx,xppu"
#interconnect-cells = <0x1>;
#interconnect-master-cells = <0x1>;
#interconnect-slave-cells = <0x0>;
reg = <0x0 0xf1310000 0x0 0x1000>;
};
};
amba {
ethernet0: ethernet@ff0c0000 {
interconnects = <&lpd_xppu QOS &pmc_xppu QOS>;
interconnects-master = <&lpd_xppu 0x234 &pmc_xppu 0x234>;
interconnects-slave = <&lpd_xppu>;
};
can0: can@ff060000 {
interconnects-slave = <&lpd_xppu>;
};
mmc0: sdhci@f1050000 {
interconnects-master = <&lpd_xppu 0x243 &pmc_xppu 0x243>;
interconnects-slave = <&pmc_xppu>;
};
serial0: serial@ff000000 {
interconnects-slave = <&lpd_xppu>;
};
};
# Interconnect Bindings for Bus Firewalls: Alternative
- Reuse the same controller for both QoS and Firewall configurations
- Specify both master and slave firewall interactions
- Distinguish between master/slave using interconnect-names
- Mix QoS data and Firewall data
Example:
amba_xppu: indirect-bus@1 {
compatible = "indirect-bus";
#address-cells = <0x2>;
#size-cells = <0x2>;
lpd_xppu: xppu@ff990000 {
compatible = "xlnx,xppu"
#interconnect-cells = <0x1>;
reg = <0x0 0xff990000 0x0 0x1000>;
};
pmc_xppu: xppu@f1310000 {
compatible = "xlnx,xppu"
#interconnect-cells = <0x1>;
reg = <0x0 0xf1310000 0x0 0x1000>;
};
};
amba {
ethernet0: ethernet@ff0c0000 {
interconnects = <&lpd_xppu 0x234 &pmc_xppu 0x234 &lpd_xppu 0x0 &qos_controller QOS>;
interconnects-names = "master", "master", "slave", "qos";
};
can0: can@ff060000 {
interconnects = <&lpd_xppu>;
interconnects-names = "slave";
};
mmc0: sdhci@f1050000 {
interconnects = <&lpd_xppu 0x243 &pmc_xppu 0x243 &pmc_xppu 0x0>;
interconnect-names = "master", "master", "slave";
};
serial0: serial@ff000000 {
interconnects = <&lpd_xppu>;
interconnects-names = "slave";
};
};
Hi all,
The notes from the Dec 3rd 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: Write-up and continue discussion on list
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