Branch: refs/heads/master
Home: https://github.com/OpenAMP/meta-openamp
Commit: 49ddd1933e362c299310bab2571cb8a2a40fcfb2
https://github.com/OpenAMP/meta-openamp/commit/49ddd1933e362c299310bab2571c…
Author: Mark Hatle <mark.hatle(a)kernel.crashing.org>
Date: 2022-11-08 (Tue, 08 Nov 2022)
Changed paths:
A recipes-openamp/libmetal/libmetal-xlnx_v2022.2.bb
M vendor/xilinx/recipes-openamp/libmetal/libmetal_%.bbappend
Log Message:
-----------
libmetal-xlnx: Merge in Xilinx 2022.2 release
Signed-off-by: Mark Hatle <mark.hatle(a)kernel.crashing.org>
(cherry picked from commit 8678b5740c8e46010742888787806757b179ba81)
Signed-off-by: Mark Hatle <mark.hatle(a)kernel.crashing.org>
Commit: 9f33f80721147ca15ac49d1e08fbba9859088d43
https://github.com/OpenAMP/meta-openamp/commit/9f33f80721147ca15ac49d1e08fb…
Author: Mark Hatle <mark.hatle(a)kernel.crashing.org>
Date: 2022-11-08 (Tue, 08 Nov 2022)
Changed paths:
A recipes-openamp/open-amp/open-amp-xlnx_v2022.2.bb
M vendor/xilinx/recipes-openamp/open-amp/open-amp_%.bbappend
Log Message:
-----------
open-amp-xlnx: Merge in Xilinx 2022.2 release
Signed-off-by: Mark Hatle <mark.hatle(a)kernel.crashing.org>
(cherry picked from commit 889ec35932e2b009cb6b9ca87a33ce87a87291af)
Signed-off-by: Mark Hatle <mark.hatle(a)kernel.crashing.org>
Commit: 90519a331b5169a55fa332dc4b67855e9f5ef409
https://github.com/OpenAMP/meta-openamp/commit/90519a331b5169a55fa332dc4b67…
Author: Mark Hatle <mark.hatle(a)kernel.crashing.org>
Date: 2022-11-08 (Tue, 08 Nov 2022)
Changed paths:
M conf/layer.conf
Log Message:
-----------
meta-openamp: declare the layer also compatible with langdale
Signed-off-by: Mark Hatle <mark.hatle(a)kernel.crashing.org>
(cherry picked from commit 7d3227ad0320e1a6d389f913fd0e4f552db43a5d)
Signed-off-by: Mark Hatle <mark.hatle(a)kernel.crashing.org>
Commit: 11dc317f784aa84110cdb515ae20b2d7208ce461
https://github.com/OpenAMP/meta-openamp/commit/11dc317f784aa84110cdb515ae20…
Author: Mark Hatle <mark.hatle(a)amd.com>
Date: 2022-11-08 (Tue, 08 Nov 2022)
Changed paths:
M vendor/xilinx/recipes-kernel/linux/linux-%.bbappend
R vendor/xilinx/recipes-kernel/linux/openamp-kmeta/cfg/remoteproc-zynqmp.cfg
R vendor/xilinx/recipes-kernel/linux/openamp-kmeta/cfg/remoteproc-zynqmp.scc
R vendor/xilinx/recipes-kernel/linux/openamp-kmeta/cfg/sparsevmemmap.cfg
R vendor/xilinx/recipes-kernel/linux/openamp-kmeta/cfg/sparsevmemmap.scc
A vendor/xilinx/recipes-kernel/linux/openamp-xilinx-kmeta/cfg/remoteproc-zynqmp.cfg
A vendor/xilinx/recipes-kernel/linux/openamp-xilinx-kmeta/cfg/remoteproc-zynqmp.scc
A vendor/xilinx/recipes-kernel/linux/openamp-xilinx-kmeta/cfg/sparsevmemmap.cfg
A vendor/xilinx/recipes-kernel/linux/openamp-xilinx-kmeta/cfg/sparsevmemmap.scc
Log Message:
-----------
vendor linux-%.bbappend: Move kmeta to vendor specific name
Re-using the base openamp-kmeta name meant that only this one was available
and not both the base and vendor version. Rename to vendor specific to
allow both paths to be available for parsing.
Signed-off-by: Mark Hatle <mark.hatle(a)amd.com>
(cherry picked from commit ac878a11dd9c15e09b32c5e504fa92e984f7ee58)
Signed-off-by: Mark Hatle <mark.hatle(a)kernel.crashing.org>
Commit: 1e06a82f039cb162930e984b00a38bec8dcdc7dd
https://github.com/OpenAMP/meta-openamp/commit/1e06a82f039cb162930e984b00a3…
Author: Bill Mills <bill.mills(a)linaro.org>
Date: 2022-11-08 (Tue, 08 Nov 2022)
Changed paths:
M recipes-kernel/linux/openamp-kmeta/cfg/openamp.cfg
M recipes-kernel/linux/openamp-kmeta/cfg/remoteproc-arm64.cfg
M recipes-kernel/linux/openamp-kmeta/cfg/remoteproc-armv7a.cfg
Log Message:
-----------
kernel config fragments: add RPMSG_CTRL and RPMSG_TTY
Since 5.18 RPMSG_CTRL is separate from RPMSG_CHAR.
Enabled it as a module.
Older kernels will ignore this. You will get a warning.
Also enable RPMSG_TTY driver for TTY devices from RPMSG
This is done in the qemu and generic machines only for now.
Signed-off-by: Bill Mills <bill.mills(a)linaro.org>
Signed-off-by: Mark Hatle <mark.hatle(a)kernel.crashing.org>
Compare: https://github.com/OpenAMP/meta-openamp/compare/c00633a6ab8f...1e06a82f039c
Branch: refs/heads/master-next
Home: https://github.com/OpenAMP/meta-openamp
Commit: 49ddd1933e362c299310bab2571cb8a2a40fcfb2
https://github.com/OpenAMP/meta-openamp/commit/49ddd1933e362c299310bab2571c…
Author: Mark Hatle <mark.hatle(a)kernel.crashing.org>
Date: 2022-11-08 (Tue, 08 Nov 2022)
Changed paths:
A recipes-openamp/libmetal/libmetal-xlnx_v2022.2.bb
M vendor/xilinx/recipes-openamp/libmetal/libmetal_%.bbappend
Log Message:
-----------
libmetal-xlnx: Merge in Xilinx 2022.2 release
Signed-off-by: Mark Hatle <mark.hatle(a)kernel.crashing.org>
(cherry picked from commit 8678b5740c8e46010742888787806757b179ba81)
Signed-off-by: Mark Hatle <mark.hatle(a)kernel.crashing.org>
Commit: 9f33f80721147ca15ac49d1e08fbba9859088d43
https://github.com/OpenAMP/meta-openamp/commit/9f33f80721147ca15ac49d1e08fb…
Author: Mark Hatle <mark.hatle(a)kernel.crashing.org>
Date: 2022-11-08 (Tue, 08 Nov 2022)
Changed paths:
A recipes-openamp/open-amp/open-amp-xlnx_v2022.2.bb
M vendor/xilinx/recipes-openamp/open-amp/open-amp_%.bbappend
Log Message:
-----------
open-amp-xlnx: Merge in Xilinx 2022.2 release
Signed-off-by: Mark Hatle <mark.hatle(a)kernel.crashing.org>
(cherry picked from commit 889ec35932e2b009cb6b9ca87a33ce87a87291af)
Signed-off-by: Mark Hatle <mark.hatle(a)kernel.crashing.org>
Commit: 90519a331b5169a55fa332dc4b67855e9f5ef409
https://github.com/OpenAMP/meta-openamp/commit/90519a331b5169a55fa332dc4b67…
Author: Mark Hatle <mark.hatle(a)kernel.crashing.org>
Date: 2022-11-08 (Tue, 08 Nov 2022)
Changed paths:
M conf/layer.conf
Log Message:
-----------
meta-openamp: declare the layer also compatible with langdale
Signed-off-by: Mark Hatle <mark.hatle(a)kernel.crashing.org>
(cherry picked from commit 7d3227ad0320e1a6d389f913fd0e4f552db43a5d)
Signed-off-by: Mark Hatle <mark.hatle(a)kernel.crashing.org>
Commit: 11dc317f784aa84110cdb515ae20b2d7208ce461
https://github.com/OpenAMP/meta-openamp/commit/11dc317f784aa84110cdb515ae20…
Author: Mark Hatle <mark.hatle(a)amd.com>
Date: 2022-11-08 (Tue, 08 Nov 2022)
Changed paths:
M vendor/xilinx/recipes-kernel/linux/linux-%.bbappend
R vendor/xilinx/recipes-kernel/linux/openamp-kmeta/cfg/remoteproc-zynqmp.cfg
R vendor/xilinx/recipes-kernel/linux/openamp-kmeta/cfg/remoteproc-zynqmp.scc
R vendor/xilinx/recipes-kernel/linux/openamp-kmeta/cfg/sparsevmemmap.cfg
R vendor/xilinx/recipes-kernel/linux/openamp-kmeta/cfg/sparsevmemmap.scc
A vendor/xilinx/recipes-kernel/linux/openamp-xilinx-kmeta/cfg/remoteproc-zynqmp.cfg
A vendor/xilinx/recipes-kernel/linux/openamp-xilinx-kmeta/cfg/remoteproc-zynqmp.scc
A vendor/xilinx/recipes-kernel/linux/openamp-xilinx-kmeta/cfg/sparsevmemmap.cfg
A vendor/xilinx/recipes-kernel/linux/openamp-xilinx-kmeta/cfg/sparsevmemmap.scc
Log Message:
-----------
vendor linux-%.bbappend: Move kmeta to vendor specific name
Re-using the base openamp-kmeta name meant that only this one was available
and not both the base and vendor version. Rename to vendor specific to
allow both paths to be available for parsing.
Signed-off-by: Mark Hatle <mark.hatle(a)amd.com>
(cherry picked from commit ac878a11dd9c15e09b32c5e504fa92e984f7ee58)
Signed-off-by: Mark Hatle <mark.hatle(a)kernel.crashing.org>
Commit: 1e06a82f039cb162930e984b00a38bec8dcdc7dd
https://github.com/OpenAMP/meta-openamp/commit/1e06a82f039cb162930e984b00a3…
Author: Bill Mills <bill.mills(a)linaro.org>
Date: 2022-11-08 (Tue, 08 Nov 2022)
Changed paths:
M recipes-kernel/linux/openamp-kmeta/cfg/openamp.cfg
M recipes-kernel/linux/openamp-kmeta/cfg/remoteproc-arm64.cfg
M recipes-kernel/linux/openamp-kmeta/cfg/remoteproc-armv7a.cfg
Log Message:
-----------
kernel config fragments: add RPMSG_CTRL and RPMSG_TTY
Since 5.18 RPMSG_CTRL is separate from RPMSG_CHAR.
Enabled it as a module.
Older kernels will ignore this. You will get a warning.
Also enable RPMSG_TTY driver for TTY devices from RPMSG
This is done in the qemu and generic machines only for now.
Signed-off-by: Bill Mills <bill.mills(a)linaro.org>
Signed-off-by: Mark Hatle <mark.hatle(a)kernel.crashing.org>
Compare: https://github.com/OpenAMP/meta-openamp/compare/49ddd1933e36%5E...1e06a82f0…
Branch: refs/heads/main
Home: https://github.com/OpenAMP/open-amp
Commit: 46d041808804f83a902a9f60fdfb6beffed22470
https://github.com/OpenAMP/open-amp/commit/46d041808804f83a902a9f60fdfb6bef…
Author: Ed Mooring <ed.mooring(a)gmail.com>
Date: 2022-11-04 (Fri, 04 Nov 2022)
Changed paths:
M apps/machine/zynqmp_r5/rsc_table.c
Log Message:
-----------
zynqmp_r5 resource table: Change notifyid for the virtio device.
1. At firmware build time, the resource table for the Xilinx zynqmp_r5
is set up with notifyid==0 for the rpmsg virtio device. The vrings are
set up with notifyid==1 for vring0 and notifyid==2 for vring1.
2. When the firmware is loaded onto the R5 via the Linux remoteproc sysfs
interface, the kernel remoteproc implementation ignores the notifyid
values for the vrings, and reallocates them, changing the resource
table. On the Xilinx configuration I tested on, this results in vring0
being allocated notifyid 0, and vring1 being allocated notifyid 1.
3. When the remote processor is started, it parses the resource table. When
it gets to the virtio device, it calls handle_vdev_rsc(), which
in turn calls remoteproc_allocate_id() with the vdev's notifyid of
0. This successfully returns 0. Then handle_vdev_rsc() goes through the
vrings. On vring0, it calls remoteproc_allocate_id(), with notifyid set to
0, because Linux changed vring0.notifyid from 1 to 0 in (2) above. This
results in remoteproc_allocate_id() returning RSC_NOTIFY_ID_ANY. This
causes handle_vdev_rsc() to return -RPROC_ERR_RSC_TAB_NP after commit
03c80a1, which causes the firmware startup to fail.
This appeared to work in previous versions, because
remoteproc_allocate_id() returning RSC_NOTIFY_ID_ANY was effectively
ignored, leaving the notifyid unchanged and allowing execution to
continue.
Set the value of notifyid for the virtio device (rvdev) to 31 to
avoid possible conflicts with the Linux imposed values.
Signed-off-by: Ed Mooring <ed.mooring(a)gmail.com>
Commit: 568d507be81a27230ba3f0260485f2ee699f5aa0
https://github.com/OpenAMP/open-amp/commit/568d507be81a27230ba3f0260485f2ee…
Author: Arnaud Pouliquen <arnaud.pouliquen(a)foss.st.com>
Date: 2022-11-04 (Fri, 04 Nov 2022)
Changed paths:
M VERSION
Log Message:
-----------
release: open-amp 2022.10.0
Set library version to 1.3.0
Signed-off-by: Arnaud Pouliquen <arnaud.pouliquen(a)foss.st.com>
Signed-off-by: Ed Mooring <ed.mooring(a)gmail.com>
Compare: https://github.com/OpenAMP/open-amp/compare/88d2e4ce38b8...568d507be81a
Branch: refs/heads/main
Home: https://github.com/OpenAMP/open-amp
Commit: 88d2e4ce38b8fe4af4ce84b2ec68a6b10a328169
https://github.com/OpenAMP/open-amp/commit/88d2e4ce38b8fe4af4ce84b2ec68a6b1…
Author: Ed Mooring <ed.mooring(a)gmail.com>
Date: 2022-11-04 (Fri, 04 Nov 2022)
Changed paths:
M apps/machine/zynqmp_r5/rsc_table.c
Log Message:
-----------
zynqmp_r5 resource table: Change notifyid for the virtio device.
1. At firmware build time, the resource table for the Xilinx zynqmp_r5
is set up with notifyid==0 for the rpmsg virtio device. The vrings are
set up with notifyid==1 for vring0 and notifyid==2 for vring1.
2. When the firmware is loaded onto the R5 via the Linux remoteproc sysfs
interface, the kernel remoteproc implementation ignores the notifyid
values for the vrings, and reallocates them, changing the resource
table. On the Xilinx configuration I tested on, this results in vring0
being allocated notifyid 0, and vring1 being allocated notifyid 1.
3. When the remote processor is started, it parses the resource table. When
it gets to the virtio device, it calls handle_vdev_rsc(), which
in turn calls remoteproc_allocate_id() with the vdev's notifyid of
0. This successfully returns 0. Then handle_vdev_rsc() goes through the
vrings. On vring0, it calls remoteproc_allocate_id(), with notifyid set to
0, because Linux changed vring0.notifyid from 1 to 0 in (2) above. This
results in remoteproc_allocate_id() returning RSC_NOTIFY_ID_ANY. This
causes handle_vdev_rsc() to return -RPROC_ERR_RSC_TAB_NP after commit
03c80a1, which causes the firmware startup to fail.
This appeared to work in previous versions, because
remoteproc_allocate_id() returning RSC_NOTIFY_ID_ANY was effectively
ignored, leaving the notifyid unchanged and allowing execution to
continue.
Set the value of notifyid for the virtio device (rvdev) to 31 to
avoid possible conflicts with the Linux imposed values.
Signed-off-by: Ed Mooring <ed.mooring(a)gmail.com>
Hi All,
I have 2 items for discussion for the community call tomorrow:
For the Remoteproc-core API rproc_get_by_child
I have a use case where I would like to call this on the current
rproc->device.
2 things:
1. At
https://github.com/torvalds/linux/blob/master/drivers/remoteproc/remoteproc…
There may be a bug here in that if the device is copied, then
device->type comparison will fail.
Can we change this to “if (!strncmp(dev->type->name, (&rproc_type)->name,
strlen((&rproc_type)->name)) ? That way even if the device is copied the
check will work.
1. For the same API, is it Ok to extend the for loop so it supports
search on the ‘current’ device passed in?
That is change
https://github.com/torvalds/linux/blob/master/drivers/remoteproc/remoteproc…
“for (dev = dev->parent; dev; dev = dev->parent) {“
to
“for (; dev; dev = dev->parent) {“
This way we can account for the current device having the rproc dev.
The reasoning for why this arises is that I have a use case where a driver
is trying to call rproc_boot() to establish an RPMsg connection.
(1) comes up because a device structure is copied so the comparison will
not work as currently constructed.
(2) comes up in our use case because the rproc structure device in an
internal driver doesn’t yet have a child to iterate up from. (2) is solved
in our use case by starting at the current device.
Thanks,
Ben
Hi All,
I have 2 items for discussion for the community call tomorrow:
For the Remoteproc-core API rproc_get_by_child
I have a use case where I would like to call this on the current
rproc->device.
2 things:
1. At [1]https://github.com/torvalds/linux/blob/master/drivers/remotep
roc/remoteproc_core.c#L2644 There may be a bug here in that if
the device is copied, then device->type comparison will fail.
Can we change this to “if (!strncmp(dev->type->name,
(&rproc_type)->name, strlen((&rproc_type)->name)) ? That way even if
the device is copied the check will work.
2. For the same API, is it Ok to extend the for loop so it supports
search on the ‘current’ device passed in?
That is
change [2]https://github.com/torvalds/linux/blob/master/drivers/remotep
roc/remoteproc_core.c#L2643
“for (dev = dev->parent; dev; dev = dev->parent) {“
to
“for (; dev; dev = dev->parent) {“
This way we can account for the current device having the rproc dev.
The reasoning for why this arises is that I have a use case where a
driver is trying to call rproc_boot() to establish an RPMsg connection.
(1) comes up because a device structure is copied so the comparison
will not work as currently constructed.
(2) comes up in our use case because the rproc structure device in an
internal driver doesn’t yet have a child to iterate up from. (2) is
solved in our use case by starting at the current device.
Thanks,
Ben
References
1. https://github.com/torvalds/linux/blob/master/drivers/remoteproc/remoteproc…
2. https://github.com/torvalds/linux/blob/master/drivers/remoteproc/remoteproc…
Hi all,
During the late stages of testing of the v2022.10 OpenAMP library, I ran
across a failure that looks like there is an unexpected interaction between
the library and the Linux remoteproc implementations. We have decided
to delay the release until we understand the problem better.
Regards,
Ed M
Branch: refs/heads/main
Home: https://github.com/OpenAMP/open-amp
Commit: cd7f331045889650189d1357fc079987236c4c0c
https://github.com/OpenAMP/open-amp/commit/cd7f331045889650189d1357fc079987…
Author: Arnaud Pouliquen <arnaud.pouliquen(a)foss.st.com>
Date: 2022-10-20 (Thu, 20 Oct 2022)
Changed paths:
M lib/remoteproc/remoteproc_virtio.c
Log Message:
-----------
remoteproc: Fix build warning in rproc_virtio_create_vdev function
The arm-none-eabi-gcc complains when VIRTIO_DEVICE_ONLY is enable
remoteproc_virtio.c:222:29: warning: variable 'vring_rsc'
set but not used [-Wunused-but-set-variable]
222 | struct fw_rsc_vdev_vring *vring_rsc;
| ^~~~~~~~~
The vring_rsc variable should be declared and set only if
VIRTIO_DEVICE_ONLY is not enable.
Signed-off-by: Arnaud Pouliquen <arnaud.pouliquen(a)foss.st.com>
Branch: refs/heads/main
Home: https://github.com/OpenAMP/open-amp
Commit: 4e1fa03814331fb87ad238072789207db5dbc374
https://github.com/OpenAMP/open-amp/commit/4e1fa03814331fb87ad238072789207d…
Author: Arnaud Pouliquen <arnaud.pouliquen(a)foss.st.com>
Date: 2022-10-18 (Tue, 18 Oct 2022)
Changed paths:
M docs/rpmsg-design.md
M lib/include/openamp/rpmsg.h
M lib/rpmsg/rpmsg.c
Log Message:
-----------
rpmsg: Add rpmsg_release_tx_buffer API
Add an API to be able to release unused TX buffer that will not be
sent.
For instance this API can be called in case of error between the
buffer reservation and the send to the remote side.
Signed-off-by: Arnaud Pouliquen <arnaud.pouliquen(a)foss.st.com>
Commit: 753a20368b2ab4b27b893eb44d7a7a5bdd840394
https://github.com/OpenAMP/open-amp/commit/753a20368b2ab4b27b893eb44d7a7a5b…
Author: Arnaud Pouliquen <arnaud.pouliquen(a)foss.st.com>
Date: 2022-10-18 (Tue, 18 Oct 2022)
Changed paths:
M docs/rpmsg-design.md
Log Message:
-----------
docs: add no-copy user API description
Add short description of the no-copy user interface.
Add some sub-chapters to increase the readability.
Signed-off-by: Arnaud Pouliquen <arnaud.pouliquen(a)foss.st.com>
Commit: 2e0015af74cee05cb82ff65c73f725670e28603e
https://github.com/OpenAMP/open-amp/commit/2e0015af74cee05cb82ff65c73f72567…
Author: Arnaud Pouliquen <arnaud.pouliquen(a)foss.st.com>
Date: 2022-10-18 (Tue, 18 Oct 2022)
Changed paths:
M lib/include/openamp/virtqueue.h
M lib/virtio/virtqueue.c
Log Message:
-----------
virtqueue: Add helper to get the buffer address from descriptor index
As it possible to get the buffer length we need also to retrieve
the address associated to the descriptor index.
This is need by rpmsg virtio to implement the buffer recycler.
Signed-off-by: Arnaud Pouliquen <arnaud.pouliquen(a)foss.st.com>
Commit: 6dad72724fcb056414e0193805362647e347ae59
https://github.com/OpenAMP/open-amp/commit/6dad72724fcb056414e0193805362647…
Author: Arnaud Pouliquen <arnaud.pouliquen(a)foss.st.com>
Date: 2022-10-18 (Tue, 18 Oct 2022)
Changed paths:
M lib/include/openamp/rpmsg_virtio.h
M lib/rpmsg/rpmsg_virtio.c
Log Message:
-----------
rpmsg virtio: Implement the Tx buffer reclaimer
With the no-copy feature a tx buffer can be get, filled and then
sent to the remote side.
In Some error cases the application can need to release it instead
of sending it to the remote side.
As the virtqueue is updated when the buffer it get, it is not
possible to manage this use case at virtqueue level.
This patchset implements the release based on a buffer recycler.
The principle is to store the released buffer in a 'reclaimer' list.
On next get pmsg_virtio_get_tx_buffer call the buffer is reused.
Signed-off-by: Arnaud Pouliquen <arnaud.pouliquen(a)foss.st.com>
Commit: 80555a314e5cdc92533fec26e48941cd2db60108
https://github.com/OpenAMP/open-amp/commit/80555a314e5cdc92533fec26e48941cd…
Author: Arnaud Pouliquen <arnaud.pouliquen(a)foss.st.com>
Date: 2022-10-18 (Tue, 18 Oct 2022)
Changed paths:
M apps/tests/msg/CMakeLists.txt
A apps/tests/msg/rpmsg-nocopy-echo.c
A apps/tests/msg/rpmsg-nocopy-ping.c
Log Message:
-----------
test: Add test for the no-copy validation.
Add test to validate the no copy and the associated Tx buffer
recycler.
Signed-off-by: Arnaud Pouliquen <arnaud.pouliquen(a)foss.st.com>
Compare: https://github.com/OpenAMP/open-amp/compare/988da0074d9c...80555a314e5c
Branch: refs/heads/main
Home: https://github.com/OpenAMP/open-amp
Commit: 988da0074d9c5cd95b693218f0eea05bbcee6d2b
https://github.com/OpenAMP/open-amp/commit/988da0074d9c5cd95b693218f0eea05b…
Author: Tanmay Shah <tanmay.shah(a)amd.com>
Date: 2022-10-18 (Tue, 18 Oct 2022)
Changed paths:
M apps/examples/rpc_demo/rpc_demo.c
Log Message:
-----------
examples: apps: Update rpc_demo description
rpc_demo.c file creates firmware that runs on remote processor.
The current description implies that proxy service is implemented
on remote side which is not true. Fix description and explicitly
mention that proxy service is implemented on host side
Signed-off-by: Tanmay Shah <tanmay.shah(a)amd.com>
Branch: refs/heads/main
Home: https://github.com/OpenAMP/open-amp
Commit: 4f2d0c2106560b4bbe91e8b3f2d25d8b01e4958c
https://github.com/OpenAMP/open-amp/commit/4f2d0c2106560b4bbe91e8b3f2d25d8b…
Author: Arnaud Pouliquen <arnaud.pouliquen(a)foss.st.com>
Date: 2022-10-18 (Tue, 18 Oct 2022)
Changed paths:
M README.md
Log Message:
-----------
README: Remove deprecated method to build open-amp lib for zephyr
The instructions to build open-amp for zephyr do not work.
Instead of trying to maintain a cross dependency between the zephyr
and the open-amp, just reference the zephyr project and documentation
Signed-off-by: Arnaud Pouliquen <arnaud.pouliquen(a)foss.st.com>
Branch: refs/heads/main
Home: https://github.com/OpenAMP/open-amp
Commit: 17b2594ab6e7929bac7d876748bed0d16a657f1e
https://github.com/OpenAMP/open-amp/commit/17b2594ab6e7929bac7d876748bed0d1…
Author: Sergei Korneichuk <sergei.korneichuk(a)amd.com>
Date: 2022-10-18 (Tue, 18 Oct 2022)
Changed paths:
M apps/examples/rpc_demo/rpc_demod.c
Log Message:
-----------
app: rpc_demod: fix buffer overflow in handle_read
Fix the following error:
Remote>Opened file 'remote.file' with fd = 8
*** buffer overflow detected ***: rpc_demod-shared
1. Change RPC_BUFF_SIZE to accomodate the remote
2. Set size to the minimum of the request or the buffer size
Signed-off-by: Sergei Korneichuk <sergei.korneichuk(a)amd.com>
Commit: bb6d16837b2c0e8f5c6d2c18c220846c2df43607
https://github.com/OpenAMP/open-amp/commit/bb6d16837b2c0e8f5c6d2c18c220846c…
Author: Ben Levinsky <ben.levinsky(a)xilinx.com>
Date: 2022-10-18 (Tue, 18 Oct 2022)
Changed paths:
M apps/examples/load_fw/load_fw.c
M apps/examples/load_fw/zynqmp_rpu_lcm_rproc_example.c
Log Message:
-----------
apps: examples: load_fw: fix up for -werror
with werror flag compilation fails. update to build
Signed-off-by: Ben Levinsky <ben.levinsky(a)xilinx.com>
Commit: 29fbf24ef926d553e56092c9d4513a4752a7b0cb
https://github.com/OpenAMP/open-amp/commit/29fbf24ef926d553e56092c9d4513a47…
Author: Manikanta Sreeram <manikanta.sreeram(a)xilinx.com>
Date: 2022-10-18 (Tue, 18 Oct 2022)
Changed paths:
M apps/examples/load_fw/lscript.ld
M apps/system/generic/machine/zynqmp_r5/linker_large_text.ld
M apps/system/generic/machine/zynqmp_r5/linker_remote.ld
Log Message:
-----------
apps: update linker scripts to SPDX license
Update linker scripts to SPDX based licensing.
Signed-off-by: Manikanta Sreeram <manikanta.sreeram(a)xilinx.com>
Commit: 2e9f3a31cc70dc04bd2c5fc45fb96602173003b2
https://github.com/OpenAMP/open-amp/commit/2e9f3a31cc70dc04bd2c5fc45fb96602…
Author: Manikanta Sreeram <manikanta.sreeram(a)xilinx.com>
Date: 2022-10-18 (Tue, 18 Oct 2022)
Changed paths:
M LICENSE.md
Log Message:
-----------
Update LICENSE.md to cover CI test scripts
Add Apache and GPL licensing to cover CI test scripts in case they
are converted to SPDX:
Apache-2.0
scripts/ci/check_compliance.py
scripts/do_checkpatch.sh
scripts/gitlint/commit_rules.py
GPL-2.0
scripts/checkpatch.pl
scripts/spelling.txt
Note: Neither Apache nor GPL are used by the libmetal library itself.
Signed-off-by: Manikanta Sreeram <manikanta.sreeram(a)xilinx.com>
Commit: 4ab1ce6f95a9046363d4b3d3f19075d373c03bb4
https://github.com/OpenAMP/open-amp/commit/4ab1ce6f95a9046363d4b3d3f19075d3…
Author: Ben Levinsky <ben.levinsky(a)xilinx.com>
Date: 2022-10-18 (Tue, 18 Oct 2022)
Changed paths:
M apps/examples/rpc_demo/rpc_demod.c
Log Message:
-----------
app: rpc_demod: replace copy_from_shbuf with metal_io_block_read
After a toolchain upgrade, the OpenAMP rpc_demod application would
fail with a bus error on AArch64 Linux. This was because the call to
copy_from_shbuf() was now inlined by the optimizer and the compiler
generated code that used 8-byte copies ("ldp x10, x11 [x4, #16]" followed
by the corresponding store instruction). The bus error happened when
the address in x4 (the index) was 4-byte aligned, but not 8-byte aligned.
This would not be a problem with normal user-space memory, but the memory
used for the shared buffer between the remote processor and Linux is
mapped as device memory. On AArch64, device memory is strictly ordered
and the alignment and width of accesses must match.
Replace copy_from_shbuf() with a call to metal_io_block_read(), which
is intended to do this sort of thing, and also makes this a better
example of how to use OpenAMP.
Return error only on a negative return value from copy_from_shbuf in
rpmsg_endpoint_cb.
Signed-off-by: Ben Levinsky <ben.levinsky(a)xilinx.com>
Compare: https://github.com/OpenAMP/open-amp/compare/2b6a38a9c689...4ab1ce6f95a9
Branch: refs/heads/main
Home: https://github.com/OpenAMP/open-amp
Commit: 2b6a38a9c6890869960ed41d6a1dc9930c079e0d
https://github.com/OpenAMP/open-amp/commit/2b6a38a9c6890869960ed41d6a1dc993…
Author: Guiding Li <liguiding1(a)xiaomi.com>
Date: 2022-10-14 (Fri, 14 Oct 2022)
Changed paths:
M lib/rpmsg/rpmsg_virtio.c
Log Message:
-----------
openamp: should kick remote when use release_rx_buffer
There is missing virtqueue_kick when use hold_rx/release_rx
Signed-off-by: Guiding Li <liguiding1(a)xiaomi.com>
Branch: refs/heads/main
Home: https://github.com/OpenAMP/open-amp
Commit: bb0be05b8a4b5b7dc48e1db824c795ca5c551d61
https://github.com/OpenAMP/open-amp/commit/bb0be05b8a4b5b7dc48e1db824c795ca…
Author: Guiding Li <liguiding1(a)xiaomi.com>
Date: 2022-10-14 (Fri, 14 Oct 2022)
Changed paths:
M lib/rpmsg/rpmsg_virtio.c
Log Message:
-----------
openamp: should kick remote when use release_rx_buffer
There is missing virtqueue_kick when use hold_rx/release_rx
Signed-off-by: Guiding Li <liguiding1(a)xiaomi.com>
Branch: refs/heads/main
Home: https://github.com/OpenAMP/open-amp
Commit: e62c824489b0943212999311c7fe20f7b396b958
https://github.com/OpenAMP/open-amp/commit/e62c824489b0943212999311c7fe20f7…
Author: Jiuzhu Dong <dongjiuzhu1(a)xiaomi.com>
Date: 2022-10-14 (Fri, 14 Oct 2022)
Changed paths:
M lib/include/openamp/rpmsg_virtio.h
M lib/rpmsg/rpmsg_virtio.c
Log Message:
-----------
openamp: divide shram to TX shram & RX shram by config:split_shpool
In the multi core of lower power device, when one of core enters sleep,
it needs to put its corresponding share memory into retention mode to
save power consumption. Based on the limitations of the chip design,
when the CPU to which share memory belongs goes to sleep, the share
memory enters the retention mode, and other cores will not be able
to access it. When the share memory divides tx shm and rx shm
and the core of tx shm and rx shm are different, so that when one
CPU sleeps, the other CPU can still access its own tx shm.
Signed-off-by: Guiding Li <liguiding1(a)xiaomi.com>
Signed-off-by: Jiuzhu Dong <dongjiuzhu1(a)xiaomi.com>
Branch: refs/heads/main
Home: https://github.com/OpenAMP/open-amp
Commit: 88f38c90204bf5821c7f8232434aa1adefa976ac
https://github.com/OpenAMP/open-amp/commit/88f38c90204bf5821c7f8232434aa1ad…
Author: Tammy Leino <tammy_leino(a)mentor.com>
Date: 2022-10-14 (Fri, 14 Oct 2022)
Changed paths:
M lib/include/openamp/remoteproc.h
M lib/remoteproc/remoteproc.c
M lib/remoteproc/rsc_table_parser.c
Log Message:
-----------
Potential overflow of notifyid on 64-bit architectures
handle_vdev_rsc sets end to RSC_NOTIFY_ID_ANY in case of wildcard notifyid
Signed-off-by: Tammy Leino <tammy_leino(a)mentor.com>
Branch: refs/heads/master
Home: https://github.com/OpenAMP/meta-openamp
Commit: 5b7a7c3eb3e2e8ae39b37acf7cd410da5bba04b3
https://github.com/OpenAMP/meta-openamp/commit/5b7a7c3eb3e2e8ae39b37acf7cd4…
Author: Bill Mills <bill.mills(a)linaro.org>
Date: 2022-10-09 (Sun, 09 Oct 2022)
Changed paths:
M recipes-kernel/linux/linux-%.bbappend
A recipes-kernel/linux/openamp-kmeta/cfg/remoteproc-generic-arm64.scc
R recipes-kernel/linux/openamp-kmeta/cfg/remoteproc-genericarm64.scc
Log Message:
-----------
add real generic-arm64 support
Support the real generic-arm64 machine from meta-arm.
Since meta-arm uses a dash between generic and arm, match that.
(Even though genericx86 does not use a dash.)
Signed-off-by: Bill Mills <bill.mills(a)linaro.org>
Commit: c00633a6ab8f4ac48da783a082dd7b34e03ff065
https://github.com/OpenAMP/meta-openamp/commit/c00633a6ab8f4ac48da783a082dd…
Author: Bill Mills <bill.mills(a)linaro.org>
Date: 2022-10-09 (Sun, 09 Oct 2022)
Changed paths:
M recipes-kernel/linux/linux-%.bbappend
A recipes-kernel/linux/openamp-kmeta/cfg/armv7a-feature-parity.cfg
A recipes-kernel/linux/openamp-kmeta/cfg/remoteproc-armv7a.cfg
A recipes-kernel/linux/openamp-kmeta/cfg/remoteproc-generic-armv7a.scc
Log Message:
-----------
Add support for armv7 for qemuarm and generic-armv7a
Add real kernel config fragments for armv7a.
Support qemuarm from oe-core and generic-armv7a from meta-openamp-bsp.
Add a placeholder file to add things to multi_arm_v7 to make it match
arm64 defconfig. However currently nothing found.
Signed-off-by: Bill Mills <bill.mills(a)linaro.org>
Compare: https://github.com/OpenAMP/meta-openamp/compare/67e07aa036be...c00633a6ab8f
Branch: refs/heads/master
Home: https://github.com/OpenAMP/meta-openamp
Commit: f46cd2f8f696be324d02f3c8b810eaa25048de2e
https://github.com/OpenAMP/meta-openamp/commit/f46cd2f8f696be324d02f3c8b810…
Author: Bill Mills <bill.mills(a)linaro.org>
Date: 2022-05-20 (Fri, 20 May 2022)
Changed paths:
M recipes-openamp/libmetal/libmetal_git.bb
A recipes-openamp/libmetal/libmetal_v2022.04.bb
M recipes-openamp/open-amp/open-amp_git.bb
A recipes-openamp/open-amp/open-amp_v2022.04.bb
Log Message:
-----------
openamp & libmetal: add 2022.04 releases & make git autorev
Add specific recipies for openamp and libmetal 2022.04 release.
Make the _git versions AUTOREV on main and user must opt in.
Signed-off-by: Bill Mills <bill.mills(a)linaro.org>
Commit: c82a6aba6d2e7037cd188eec8c62f7d46f6fdcd8
https://github.com/OpenAMP/meta-openamp/commit/c82a6aba6d2e7037cd188eec8c62…
Author: Bill Mills <bill.mills(a)linaro.org>
Date: 2022-05-20 (Fri, 20 May 2022)
Changed paths:
M recipes-openamp/libmetal/libmetal.inc
M recipes-openamp/open-amp/open-amp.inc
Log Message:
-----------
openamp & libmetal: fix BSD QA warning
Declare specific BSD licenses to pass QA checks.
openamp uses mostly BSD-3-Clause but BSD-2-Clause for the virtio layer.
Signed-off-by: Bill Mills <bill.mills(a)linaro.org>
Commit: 67e07aa036be9dc9ac71b4567d484ae6c945f2b4
https://github.com/OpenAMP/meta-openamp/commit/67e07aa036be9dc9ac71b4567d48…
Author: Bill Mills <bill.mills(a)linaro.org>
Date: 2022-05-20 (Fri, 20 May 2022)
Changed paths:
M recipes-openamp/rpmsg-examples/rpmsg-echo-test_1.0.bb
M recipes-openamp/rpmsg-examples/rpmsg-mat-mul_1.0.bb
M recipes-openamp/rpmsg-examples/rpmsg-proxy-app_1.0.bb
Log Message:
-----------
rpmsg-examples: fix BSD QA warning
Declare specific BSD licenses to pass QA checks.
All these examples use BSD-3-Clause.
Signed-off-by: Bill Mills <bill.mills(a)linaro.org>
Compare: https://github.com/OpenAMP/meta-openamp/compare/b6e2a13fdd8f...67e07aa036be