|
NAMEbus_map_resource ,
bus_unmap_resource ,
resource_init_map_request —
map or unmap an active resource
SYNOPSIS#include <sys/param.h>
#include <sys/bus.h>
int
int
void
DESCRIPTIONThese functions create or destroy a mapping of a previously activated resource. Mappings permit CPU access to the resource via the bus_space(9) API.The arguments are as follows:
Resource MappingsResource mappings are described by a struct resource_map object. This structure contains a bus_space(9) tag and handle in the r_bustag and r_bushandle members that can be used for CPU access to the mapping. The structure also contains a r_vaddr member which contains the virtual address of the mapping if one exists.The wrapper API for struct resource objects
described in
bus_activate_resource(9)
can also be used with struct resource_map. For
example, a pointer to a mapping object can be passed as the first argument
to Optional Mapping PropertiesThe struct resource_map_request object passed in args can be used to specify optional properties of a mapping. The structure must be initialized by invokingresource_init_map_request (). Properties are then
specified by setting one or more of these members:
RETURN VALUESZero is returned on success, otherwise an error is returned.EXAMPLESThis maps a PCI memory BAR with the write-combining memory attribute and reads the first 32-bit word:struct resource *r; struct resource_map map; struct resource_map_request req; uint32_t val; int rid; rid = PCIR_BAR(0); r = bus_alloc_resource_any(dev, SYS_RES_MEMORY, &rid, RF_ACTIVE | RF_UNMAPPED); resource_init_map_request(&req); req.memattr = VM_MEMATTR_WRITE_COMBINING; bus_map_resource(dev, SYS_RES_MEMORY, r, &req, &map); val = bus_read_4(&map, 0); SEE ALSObus_activate_resource(9), bus_alloc_resource(9), bus_space(9), device(9), driver(9)AUTHORSThis manual page was written by John Baldwin <jhb@FreeBSD.org>.
Visit the GSP FreeBSD Man Page Interface. |