Home
last modified time | relevance | path

Searched refs:BAR (Results 1 – 20 of 20) sorted by relevance

/linux-4.1.27/Documentation/powerpc/
Dpci_iov_resource_on_powernv.txt162 discover the BAR sizes and assign addresses for them. For VF devices,
163 software uses VF BAR registers in the *PF* SR-IOV Capability to
167 When a VF BAR in the PF SR-IOV Capability is programmed, it sets the
170 1MB VF BAR0, the address in that VF BAR sets the base of an 8MB region.
172 is a BAR0 for one of the VFs. Note that even though the VF BAR
185 the segment size matches the smallest VF BAR, which means larger VF
200 and different segment sizes. If we have VFs that each have a 1MB BAR
201 and a 32MB BAR, we could use one M64 window to assign 1MB segments and
205 more in the next two sections. For a given VF BAR, we need to
206 effectively reserve the entire 256 segments (256 * VF BAR size) and
[all …]
Deeh-pci-error-recovery.txt95 config space (the base address registers (BAR's), latency timer,
174 It saves the device BAR's and then calls rpaphp_unconfig_pci_adapter().
180 It then resets the PCI card, reconfigures the device BAR's, and
/linux-4.1.27/drivers/gpu/drm/nouveau/nvkm/subdev/bar/
Dgk20a.c43 .handle = NV_SUBDEV(BAR, 0xea),
Dgf100.c212 .handle = NV_SUBDEV(BAR, 0xc0),
Dnv50.c264 .handle = NV_SUBDEV(BAR, 0x50),
/linux-4.1.27/Documentation/devicetree/bindings/i2c/
Di2c-pxa-pci-ce4100.txt21 offset from be base of the BAR (which would be
23 the same BAR)
/linux-4.1.27/Documentation/kbuild/
Dkconfig-language.txt91 bool "foo" if BAR
92 default y if BAR
94 depends on BAR
110 if FOO depends on BAR that is not set.
393 depends on BAR && m
/linux-4.1.27/arch/cris/arch-v10/kernel/
Dkgdb.c309 BAR, DCCR, BRP, USP enumerator
/linux-4.1.27/Documentation/scsi/
DChangeLog.sym53c8xx37 - Get both the BAR cookies used by CPU and actual PCI BAR
40 BAR values to destination address to make decision.
44 PCI BAR value from the BAR cookie is now useless.
DChangeLog.ncr53c8xx10 - Get both the BAR cookies actual and PCI BAR values.
/linux-4.1.27/Documentation/x86/
Dearlyprintk.txt29 Capabilities: [58] Debug port: BAR=1 offset=00a0
/linux-4.1.27/Documentation/arm/
DIXP4xx79 To access PCI via this space, we simply ioremap() the BAR
/linux-4.1.27/arch/arm/mach-ixp4xx/
DKconfig206 To access PCI via this space, we simply ioremap() the BAR
/linux-4.1.27/Documentation/driver-model/
Ddevres.txt284 pcim_iomap_table() : array of mapped addresses indexed by BAR
/linux-4.1.27/Documentation/
DDMA-API-HOWTO.txt66 example, if a PCI device has a BAR, the kernel reads the bus address (A)
67 from the BAR and converts it to a CPU physical address (B). The address B
897 ringp->len = BAR;
902 dma_unmap_len_set(ringp, len, BAR);
/linux-4.1.27/Documentation/PCI/
DMSI-HOWTO.txt450 The MSI-X capability specifies a BAR and offset within that BAR for the
Dpci-error-recovery.txt268 restoring the PCI BAR's and PCI configuration header to a state
/linux-4.1.27/Documentation/input/
Datarikbd.txt662 39 SPACE BAR
/linux-4.1.27/drivers/tty/
Dsynclinkmp.c353 #define BAR 0x80 macro
/linux-4.1.27/Documentation/virtual/kvm/
Dapi.txt1310 Only PCI header type 0 devices with PCI BAR resources are supported by