Zephyr API Documentation 4.0.0
A Scalable Open Source RTOS
|
For drivers which need to manage multiple MMIO regions, which will be referenced by name. More...
Macros | |
#define | DEVICE_MMIO_NAMED_RAM(name) |
Declare storage for MMIO data within a device's dev_data struct. | |
#define | DEVICE_MMIO_NAMED_RAM_PTR(dev, name) |
Return a pointer to the RAM storage for a device's named MMIO address. | |
#define | DEVICE_MMIO_NAMED_ROM(name) |
Declare storage for MMIO data within a device's config struct. | |
#define | DEVICE_MMIO_NAMED_ROM_PTR(dev, name) |
Return a pointer to the ROM-based storage area for a device's MMIO information. | |
#define | DEVICE_MMIO_NAMED_ROM_INIT(name, node_id) |
Initialize a named DEVICE_MMIO_NAMED_ROM member. | |
#define | DEVICE_MMIO_NAMED_ROM_INIT_BY_NAME(name, node_id) |
Initialize a named DEVICE_MMIO_NAMED_ROM member using a named DT reg property. | |
#define | DEVICE_MMIO_NAMED_MAP(dev, name, flags) |
Set up memory for a named MMIO region. | |
#define | DEVICE_MMIO_NAMED_GET(dev, name) |
Obtain a named MMIO address for a device. | |
For drivers which need to manage multiple MMIO regions, which will be referenced by name.
#define DEVICE_MMIO_NAMED_GET | ( | dev, | |
name ) |
#include <zephyr/sys/device_mmio.h>
Obtain a named MMIO address for a device.
This macro returns the MMIO base address for a named region from the appropriate place within the device object's linked data structures.
This is for drivers which have multiple MMIO regions.
This macro requires that the macros DEV_DATA and DEV_CFG are locally defined and return properly typed pointers to the particular dev_data and config structs for this driver.
dev | Device object |
name | Member name for MMIO information, as declared with DEVICE_MMIO_NAMED_RAM/DEVICE_MMIO_NAMED_ROM |
#define DEVICE_MMIO_NAMED_MAP | ( | dev, | |
name, | |||
flags ) |
#include <zephyr/sys/device_mmio.h>
Set up memory for a named MMIO region.
This performs the necessary PCI probing and/or MMU virtual memory mapping such that DEVICE_MMIO_GET(name) returns a suitable linear memory address for the MMIO region.
If such operations are not required by the target hardware, this expands to nothing.
This should be called from the driver's init function, once for each MMIO region that needs to be mapped.
This macro requires that the macros DEV_DATA and DEV_CFG are locally defined and return properly typed pointers to the particular dev_data and config structs for this driver.
The flags argument is currently used for caching mode, which should be one of the DEVICE_CACHE_* macros. Unused bits are reserved for future expansion.
dev | Device object |
name | Member name for MMIO information, as declared with DEVICE_MMIO_NAMED_RAM/DEVICE_MMIO_NAMED_ROM |
flags | One of the DEVICE_CACHE_* caching modes |
#define DEVICE_MMIO_NAMED_RAM | ( | name | ) |
#include <zephyr/sys/device_mmio.h>
Declare storage for MMIO data within a device's dev_data struct.
This gets accessed by the DEVICE_MMIO_NAMED_MAP() and DEVICE_MMIO_NAMED_GET() macros.
Depending on configuration, no memory may be reserved at all. Multiple named regions may be declared.
There must be a corresponding DEVICE_MMIO_ROM in config if the physical address is known at build time, but may be omitted if not (such as with PCIe.
Example for a driver named "foo":
No build-time initialization of this memory is necessary; it will be set up in the init function by DEVICE_MMIO_NAMED_MAP().
name | Member name to use to store within dev_data. |
#define DEVICE_MMIO_NAMED_RAM_PTR | ( | dev, | |
name ) |
#include <zephyr/sys/device_mmio.h>
Return a pointer to the RAM storage for a device's named MMIO address.
This macro requires that the macro DEV_DATA is locally defined and returns a properly typed pointer to the particular dev_data struct for this driver.
dev | device instance object |
name | Member name within dev_data |
mm_reg_t | pointer to storage location |
#define DEVICE_MMIO_NAMED_ROM | ( | name | ) |
#include <zephyr/sys/device_mmio.h>
Declare storage for MMIO data within a device's config struct.
This gets accessed by DEVICE_MMIO_NAMED_MAP() and DEVICE_MMIO_NAMED_GET() macros.
What gets stored here varies considerably by configuration. Multiple named regions may be declared. There must be corresponding entries in the dev_data struct.
This storage is not used if the device is PCIe and may be omitted.
If used, this must be initialized at build time with information from DTS using DEVICE_MMIO_NAMED_ROM_INIT()
A pointer to this memory may be obtained with DEVICE_MMIO_NAMED_ROM_PTR().
Example for a driver named "foo":
name | Member name to store within config |
#define DEVICE_MMIO_NAMED_ROM_INIT | ( | name, | |
node_id ) |
#include <zephyr/sys/device_mmio.h>
Initialize a named DEVICE_MMIO_NAMED_ROM member.
Initialize MMIO-related information within a specific instance of a device config struct, using information from DTS.
Example for an instance of a driver belonging to the "foo" subsystem that will have two regions named 'corge' and 'grault':
name | Member name within config for the MMIO region |
node_id | DTS node identifier |
#define DEVICE_MMIO_NAMED_ROM_INIT_BY_NAME | ( | name, | |
node_id ) |
#include <zephyr/sys/device_mmio.h>
Initialize a named DEVICE_MMIO_NAMED_ROM member using a named DT reg property.
Same as DEVICE_MMIO_NAMED_ROM_INIT but the size and address are taken from a named DT reg property.
Example for an instance of a driver belonging to the "foo" subsystem that will have two DT-defined regions named 'chip' and 'dale':
name | Member name within config for the MMIO region and name of the reg property in the DT |
node_id | DTS node identifier |
#define DEVICE_MMIO_NAMED_ROM_PTR | ( | dev, | |
name ) |
#include <zephyr/sys/device_mmio.h>
Return a pointer to the ROM-based storage area for a device's MMIO information.
This macro requires that the macro DEV_CFG is locally defined and returns a properly typed pointer to the particular config struct for this driver.
dev | device instance object |
name | Member name within config |
struct | device_mmio_rom * pointer to storage location |