- Openamp-system-reference - lists.openampproject.org

2022-03-16 OpenAMP System Reference call notes and action items

by Nathalie Chan King Choy

Hi all, The notes are now posted at https://github.com/OpenAMP/openamp-system-reference/wiki/OpenAMP-System-Ref… Best regards, Nathalie

2 years, 2 months

1
0
0 0

Calling for agenda: 2022-03-16 OpenAMP System Reference call

by Nathalie Chan King Choy

Hi all, Reminder that North America had our Daylight Savings time change this past weekend, but Europe's comes later in the month, so the meeting time will probably be skewed by an hour for @Arnaud POULIQUEN<mailto:arnaud.pouliquen@st.com> & @Milea, Danut Gabriel (Danut)<mailto:Danut.Milea@windriver.com>. Please let us know if you have additional topics for the agenda. This is what I collected so far: * Individual updates. From last meeting: What to work on before next call? * Tanmay: In sync w/ Mathieu on what needs to happen next. Will post v4 for upstreaming Xilinx remoteproc driver in next 2 weeks. * Arnaud: Try to upstream work to close to mainline repositories (Zephyr & Linux) * Bill: Add staging kernel into builds. Try Xilinx KV260. * Tammy: Have to finish current project before can address the changes in the outstanding tickets (so not in the next 2 weeks) Thanks & regards, Nathalie

2 years, 2 months

1
0
0 0

2022-03-02 OpenAMP System Reference notes and action items

by Nathalie Chan King Choy

Hi all, Notes from today's call are posted at: https://github.com/OpenAMP/openamp-system-reference/wiki/OpenAMP-System-Ref… Action items * (IN PROGRESS) Tomas give Bruce a heads up during 1:1 * (IN PROGRESS) Bill will start an email thread with Bruce to get his access re-activated in the Linaro system * Bill: Send out the Google Drive links for commenters & editors for the virtio-related proposal * Nathalie: Start email thread w/ Arnaud & NXP folks Best regards, Nathalie

2 years, 2 months

1
0
0 0

HPP homepage

by Bill Mills

Hello, The HPP homepage should be publicly visible to all. https://linaro.atlassian.net/wiki/spaces/HPP/overview As the page says: HPP is a Linaro project but it is also closely associated with the OpenAMP community project Thanks, Bill -- Bill Mills Principal Technical Consultant, Linaro +1-240-643-0836 TZ: US Eastern Work Schedule: Tues/Wed/Thur

2 years, 2 months

1
0
0 0

Calling for agenda: 2022-03-02 OpenAMP System Reference call

by Nathalie Chan King Choy

Hi all, Please let us know if you have additional topics. Here is what I collected so far for the agenda: * Nathalie: Update on Xilinx plan for ELC NA CFP * Dan: Any update on Zephyr Developer Summit CFP? (March 4 deadline) * Anything this group needs to discuss wrt Virtio discussion? * Individual updates. Objectives from previous call: * Tanmay: Post RPU binaries for Bill to try. * Bill: Reproduce Dan's work Thanks & regards, Nathalie

2 years, 2 months

1
0
0 0

Calling for agenda: 2022-02-16 OpenAMP System Reference call

by Nathalie Chan King Choy

Hi all, Please let us know if you have additional topics. Here is what I collected so far for the agenda: * Keeping Discord going * Bill's suggestions to re-organize wiki & publishing output of the sprint * Submit to ELC NA<https://events.linuxfoundation.org/open-source-summit-north-america/> CFP? Deadline is March 14. Event is June 21-24 Austin, TX and Virtual. * Submit to Zephyr Developer Summit CFP<https://linuxfoundation.smapply.io/prog/zephyr_developer_summit_2022/>? Deadline is March 4. Event is June 8-9 Mountain View, CA * Individual updates. Objectives from previous call: * Tanmay: Post RPU binaries for Bill to try. * Bill: Reproduce Tanmay's work. If time, reproduce Dan's. * Dan: Virtio discussion prep. * Tammy: Can support, not enough time this week for independent tasks. Thanks & regards, Nathalie

2 years, 3 months

1
0
0 0

Calling for agenda: 2022-02-09 OpenAMP System Reference

by Nathalie Chan King Choy

Hi all, The main agenda topic for the call will be a wrap-up of the previous week's virtual sprint. Any other topics to discuss? Thanks & regards, Nathalie

2 years, 3 months

1
0
0 0

[PATCH v3 0/6] Add Xilinx RPU subsystem support

by Tanmay Shah

This patch series adds bindings document for RPU subsystem found on Xilinx ZynqMP platforms. It also adds device nodes and driver to enable RPU subsytem in split mode and lockstep mode. Xilinx ZynqMP platform contains Remote Processing Unit(RPU). RPU subsystem contains two arm cortex r5f cores. RPU subsystem can be configured in split mode, locsktep mode and single-cpu mode. RPU subsystem also contains 4 Tightly Coupled Memory(TCM) banks. In lockstep mode, all 4 banks are combined and total of 256KB memory is made available to r5 core0. In split mode, both cores can access two TCM banks i.e. 128 KB. RPU can also fetch data and execute instructions from DDR memory along with TCM memory. --- Changes in v3: - Fix checkpatch script indentation warning - Remove unused variable from xilinx remoteproc driver - use C style comments, i.e /*...*/ - Remove redundant debug information which can be derived using /proc/device-tree - Fix multilined comment format - s/"final fot TCM"/"final for TCM" - Function devm_kzalloc() does not return an code on error, just NULL. Remove redundant error check for this function throughout the driver. - Fix RPU mode configuration and add documentation accordingly - Get rid of the indentations to match function documentation style with rest of the driver - Fix memory leak by only using r5_rproc->priv and not replace it with new instance - Use 'i' for the outer loop and 'j' for the inner one as per convention - Remove redundant error and NULL checks throughout the driver - Use devm_kcalloc() when more than one element is required - Add memory-regions carveouts during driver probe instead of parse_fw call This removes redundant copy of reserved_mem object in r5_core structure. - Fix memory leak by using of_node_put() - Fix indentation of tcm_mem_map function args - Remove redundant init of variables - Initialize tcm bank size variable for lockstep mode - Replace u32 with phys_addr_t for variable stroing memory bank address - Add documentation of TCM behavior in lockstep mode - Use dev_get_drvdata instead of platform driver API - Remove info level messages - Fix checkpatch.pl warnings - Add documentation for the Xilinx r5f platform to understand driver design Changes in v2: - Remove proprietary copyright footer from cover letter Ben Levinsky (3): firmware: xilinx: Add ZynqMP firmware ioctl enums for RPU configuration. firmware: xilinx: Add shutdown/wakeup APIs firmware: xilinx: Add RPU configuration APIs Tanmay Shah (3): dt-bindings: remoteproc: Add Xilinx RPU subsystem bindings arm64: dts: xilinx: zynqmp: Add RPU subsystem device node drivers: remoteproc: Add Xilinx r5 remoteproc driver .../bindings/remoteproc/xlnx,r5f-rproc.yaml | 139 +++ arch/arm64/boot/dts/xilinx/zynqmp.dtsi | 17 + drivers/firmware/xilinx/zynqmp.c | 96 ++ drivers/remoteproc/Kconfig | 12 + drivers/remoteproc/Makefile | 1 + drivers/remoteproc/xlnx_r5_remoteproc.c | 975 ++++++++++++++++++ include/dt-bindings/power/xlnx-zynqmp-power.h | 6 + include/linux/firmware/xlnx-zynqmp.h | 60 ++ 8 files changed, 1306 insertions(+) create mode 100644 Documentation/devicetree/bindings/remoteproc/xlnx,r5f-rproc.yaml create mode 100644 drivers/remoteproc/xlnx_r5_remoteproc.c base-commit: c1fe10d238c0256a77dbc4bf6493b9782b2a218d -- 2.25.1

2 years, 3 months

1
6
0 0

Posted OpenAMP System Reference presentation from HPP call to website

by Nathalie Chan King Choy

Hi, I finally got around to one of my old action items. The PDF version of the presentation that Tomas & Bill gave to the HPP working group about OpenAMP System Reference is now posted to https://www.openampproject.org/docs/presentations/OpenAMPSystemReferencePro… Updates compared to what was actually presented to HPP: * Added mention of RTOS * Updated Wind River logo Best regards, Nathalie

2 years, 3 months

1
0
0 0

Organizing virtual sprint tasks

by Nathalie Chan King Choy

Hi all, Since Linaro Jira is not accessible to everyone in the System Reference project, do we want to use GitHub Projects in the OpenAMP System Refence repo to organize the tasks for next week's sprint? https://github.com/OpenAMP/openamp-system-reference/projects Columns could be: Backlog, To do today, In progress, Done? Or, do you prefer to keep the GitHub repo & issue queue limited to what is being published and not the draft work, similar to how we're having content in Google Drive until it's ready for publication outside this working group? If so, we could avoid making people sign up for new tools by staying basic & just have a Google spreadsheet to track the tasks. Other ideas are welcome. Thanks & regards, Nathalie

2 years, 3 months

1
0
0 0

2024

2023

2022

2021

Openamp-system-reference