Branch: refs/heads/main Home: https://github.com/OpenAMP/open-amp Commit: 6780dd2378b7c820af06f49eb817eb2d4ff78909 https://github.com/OpenAMP/open-amp/commit/6780dd2378b7c820af06f49eb817eb2d4... Author: Andrew Davis afd@ti.com Date: 2024-07-05 (Fri, 05 Jul 2024)
Changed paths: M lib/include/openamp/virtio_mmio.h M lib/virtio_mmio/virtio_mmio_drv.c
Log Message: ----------- virtio_mmio: Remove unneeded use of libmetal device
A virtual metal_device is created, then the needed IO regions are created and added to this device. Immediately we extract these same regions back out and make use of them. There is no reason to do this, instead simply use the created IO regions.
This also removes the need to have struct metal_device defined to have more than one IO region (METAL_MAX_DEVICE_REGIONS), which is not the default and can change per-platform. If the libmetal library was built with the default value for METAL_MAX_DEVICE_REGIONS, then this would have led to runtime failures.
Signed-off-by: Andrew Davis afd@ti.com
Commit: fdb8bf342479da9cdabe6077bc37f0eb34f0e1b7 https://github.com/OpenAMP/open-amp/commit/fdb8bf342479da9cdabe6077bc37f0eb3... Author: Andrew Davis afd@ti.com Date: 2024-07-05 (Fri, 05 Jul 2024)
Changed paths: M lib/include/openamp/virtio_mmio.h M lib/virtio_mmio/virtio_mmio_drv.c
Log Message: ----------- virtio_mmio: Statically allocate metal_io_regions
Make the metal_io_region for cfg_io and shm_io into full member structs instead of just pointers. This means they will be allocated along with the parent virtio_mmio_device struct and not need dynamically allocated later.
Signed-off-by: Andrew Davis afd@ti.com
Compare: https://github.com/OpenAMP/open-amp/compare/856680eb99ce...fdb8bf342479
To unsubscribe from these emails, change your notification settings at https://github.com/OpenAMP/open-amp/settings/notifications