Searched refs:BAR (Results 1 – 25 of 28) sorted by relevance
12
/Linux-v4.19/Documentation/powerpc/ |
D | pci_iov_resource_on_powernv.txt | 162 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 …]
|
D | eeh-pci-error-recovery.txt | 95 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-v4.19/drivers/ntb/hw/idt/ |
D | Kconfig | 19 accepted by a BAR. Note that BAR0 must map PCI configuration space 23 BAR settings of peer NT-functions, the BAR setups can't be done over
|
/Linux-v4.19/Documentation/misc-devices/ |
D | pci-endpoint-test.txt | 10 *) verifying addresses programmed in BAR 24 PCITEST_BAR: Tests the BAR. The number of the BAR to be tested
|
/Linux-v4.19/samples/bpf/ |
D | test_cgrp2_attach2.c | 37 #define BAR "/foo/bar/" macro 96 bar = create_and_get_cgroup(BAR); in test_foo_bar() 100 if (join_cgroup(BAR)) in test_foo_bar()
|
/Linux-v4.19/Documentation/devicetree/bindings/i2c/ |
D | i2c-pxa-pci-ce4100.txt | 21 offset from be base of the BAR (which would be 23 the same BAR)
|
/Linux-v4.19/Documentation/PCI/endpoint/ |
D | pci-endpoint.txt | 43 * set_bar: ops to configure the BAR 44 * clear_bar: ops to reset the BAR 94 the BAR. 176 The PCI Function driver can allocate space for a particular BAR using
|
D | pci-test-howto.txt | 113 BAR tests
|
/Linux-v4.19/drivers/firmware/broadcom/ |
D | Kconfig | 20 a PCI BAR.
|
/Linux-v4.19/drivers/staging/gasket/ |
D | TODO | 8 the gasket APIs adds some extra conveniences like PCI BAR mapping, and
|
/Linux-v4.19/Documentation/ |
D | men-chameleon-bus.txt | 66 header lists the device id, PCI BAR, offset from the beginning of the PCI 67 BAR, size in the FPGA, interrupt number and some other properties currently
|
D | DMA-API-HOWTO.txt | 68 example, if a PCI device has a BAR, the kernel reads the bus address (A) 69 from the BAR and converts it to a CPU physical address (B). The address B 902 ringp->len = BAR; 907 dma_unmap_len_set(ringp, len, BAR);
|
/Linux-v4.19/Documentation/devicetree/bindings/pci/ |
D | cdns,cdns-pcie-host.txt | 22 - cdns,no-bar-match-nbits: Set into the no BAR match register to configure the
|
/Linux-v4.19/Documentation/kbuild/ |
D | kconfig-language.txt | 112 bool "foo" if BAR 113 default y if BAR 115 depends on BAR 131 if FOO depends on BAR that is not set. 150 depends on BAR 154 FOO BAR BAZ's default choice for BAZ 506 depends on BAR && m
|
/Linux-v4.19/Documentation/scsi/ |
D | ChangeLog.sym53c8xx | 37 - 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.
|
D | ChangeLog.ncr53c8xx | 10 - Get both the BAR cookies actual and PCI BAR values.
|
/Linux-v4.19/Documentation/x86/ |
D | earlyprintk.txt | 29 Capabilities: [58] Debug port: BAR=1 offset=00a0
|
/Linux-v4.19/Documentation/arm/ |
D | IXP4xx | 79 To access PCI via this space, we simply ioremap() the BAR
|
/Linux-v4.19/arch/arm/mach-ixp4xx/ |
D | Kconfig | 206 To access PCI via this space, we simply ioremap() the BAR
|
/Linux-v4.19/Documentation/gpu/ |
D | drm-internals.rst | 183 or exists on the PCI device in the ROM BAR. Note that after the ROM has
|
/Linux-v4.19/Documentation/driver-model/ |
D | devres.txt | 302 pcim_iomap_table() : array of mapped addresses indexed by BAR
|
/Linux-v4.19/Documentation/PCI/ |
D | acpi-info.txt | 21 namespace [2]. The _CRS is like a generalized PCI BAR: the OS can read
|
D | pci-error-recovery.txt | 244 restoring the PCI BAR's and PCI configuration header to a state
|
/Linux-v4.19/Documentation/networking/ |
D | ena.txt | 135 device memory BAR, which is mapped with write-combine capability.
|
/Linux-v4.19/Documentation/input/devices/ |
D | atarikbd.rst | 772 39 SPACE BAR
|
12