Home
last modified time | relevance | path

Searched refs:addresses (Results 1 – 200 of 390) sorted by relevance

12

/linux-4.1.27/Documentation/i2c/
Dten-bit-addresses1 The I2C protocol knows about two kinds of device addresses: normal 7 bit
2 addresses, and an extended set of 10 bit addresses. The sets of addresses
11 * Not all bus drivers support 10-bit addresses. Some don't because the
16 * Some optional features do not support 10-bit addresses. This is the
20 10-bit addresses.
Di2c-stub9 You need to provide chip addresses as a module parameter when loading this
10 driver, which will then only react to SMBus commands to these addresses.
13 quick commands to the specified addresses; it will respond to the other
14 commands (also to the specified addresses) by reading from or writing to
42 The SMBus addresses to emulate chips at.
Dinstantiating-devices46 addresses and custom data needed by their drivers. When the I2C bus in
123 it may have different addresses from one board to the next (manufacturer
164 at 25 different addresses. Given the huge number of mainboards out there,
211 what addresses they live at. However, in certain cases, it does not, so a
Ddev-interface105 argument (except for 10 bit addresses, passed in the 10 lower bits in this
109 Selects ten bit addresses if select not equals 0, selects normal 7 bit
110 addresses if select equals 0. Default 0. This request is only valid
Dwriting-clients177 models, and I2C device addresses change from one model to the next. In
180 possible I2C addresses to probe. A device is created for the first
202 for unsupported ones), a list of addresses to probe, and a device type
/linux-4.1.27/Documentation/arm64/
Dtagged-pointers.txt1 Tagged virtual addresses in AArch64 Linux
8 addresses in the AArch64 translation system and their potential uses
16 (1) The kernel requires that all user addresses passed to EL1
18 parameters containing user virtual addresses *must* have
24 addresses being maintained for fields inside siginfo_t.
31 virtual addresses differing only in the upper byte.
Dmemory.txt12 (256TB) virtual addresses, respectively, for both user and kernel. With
16 User addresses have bits 63:48 set to 0 while the kernel addresses have
/linux-4.1.27/Documentation/parisc/
Ddebugging5 1. Absolute addresses
8 absolute addresses are used instead of virtual addresses as in the
18 the System Responder/Requestor addresses. The System Requestor
19 address should match (one of the) processor HPAs (high addresses in
23 Typical values for the System Responder address are addresses larger
/linux-4.1.27/Documentation/networking/
Dipv6.txt19 IPv6 addresses or operations are desired.
31 No IPv6 addresses will be added to interfaces, and
40 for addresses to be automatically generated from prefixes
48 Only the IPv6 loopback address (::1) and link-local addresses
59 This might be used when no IPv6 addresses are desired.
71 No IPv6 addresses will be added to interfaces.
Ddecnet.txt47 which is that its added to the addresses on the loopback device.
49 With 2.4 kernels, DECnet would only recognise addresses as local if they
52 prevent you adding further addresses to the loopback device if you
55 N.B. Since the address list of an interface determines the addresses for
119 IP and DECnet, albeit with DECnet addresses instead of IP addresses and
184 -e flag also provides very useful information (ethernet MAC addresses))
188 A quick FAQ on ethernet MAC addresses to explain how Linux and DECnet
194 Linux has an interface which allows the setting of extra addresses for
205 addresses on each physical interface. If you do this, be aware that if your
209 packets from the DECnet specified addresses. So if you have one of these
Dip-sysctl.txt780 If set, allows processes to bind() to non-local IP addresses,
785 If set non-zero, enables support for dynamic addresses.
909 Log packets with impossible addresses to kernel log.
1011 Accept packets with local source addresses. In combination with
1017 Do not consider loopback addresses as martian source or destination
1050 0 - (default) The kernel can respond to arp requests with addresses
1053 IP addresses are owned by the complete host on Linux, not by
1066 1 - Try to avoid local addresses that are not in the target's
1079 for primary IP addresses on all our subnets on the outgoing
1094 received ARP requests that resolve local target IP addresses:
[all …]
Dpolicy-routing.txt24 RT_CLASS_LOCAL=255 - local interface addresses,
25 broadcasts, nat addresses.
101 255 local addresses
DREADME.sb1000116 IP addresses (like 204.71.200.67), be sure your /etc/resolv.conf file
117 has no syntax errors and has the right nameserver IP addresses in it.
131 numerical IP addresses. (This happens predominantly on Debian systems due
141 addresses.
153 option in the lines that allocate the two I/O addresses for the SB1000 card.
154 This first popped up on RH 6.0. Delete "(CHECK)" for the SB1000 I/O addresses.
Dalias.txt5 IP-aliases are an obsolete way to manage multiple IP-addresses/masks
Dl2tp.txt71 tunnel, the interface can be given an IP addresses of itself and its
213 and peer 192.168.1.2, using IP addresses 10.5.1.1 and 10.5.1.2 for the
226 Choose IP addresses to be the address of a local IP interface and that
227 of the remote system. The IP addresses of the l2tpeth0 interface can be
231 addresses reversed. The tunnel and session IDs can be any non-zero
Darcnet-hardware.txt459 addresses) \----------------------------------/
621 of eight possible I/O Base addresses using the following table
862 of 32 possible I/O Base addresses using the following table
1033 SW2: DIP-Switches for Memory Base and I/O Base addresses
1191 This was difficult to test by trial and error, and the I/O addresses
1194 addresses (mostly between 0x200 and 0x400). The address that caused
1200 an address of 0x300 since Windows may not like addresses below
1217 0xD000, it will use up addresses 0xD000 to 0xD100.
1222 using these addresses.
1378 of eight possible I/O Base addresses using the following table
[all …]
Drds.txt29 RDS uses IPv4 addresses and 16bit port numbers to identify
31 passing addresses between kernel and user space generally
34 The fact that IPv4 addresses are used does not mean the underlying
235 indicate which ports on bound addresses are congested. As the
Dtproxy.txt26 addresses. All you have to do is enable the (SOL_IP, IP_TRANSPARENT) socket
Dipddp.txt46 proper IP Gateway and IP addresses for your machine. Included in this
Dbonding.txt243 generated via ARP probes issued for the addresses specified by
261 Specifies the IP addresses to use as ARP monitoring peers when
265 addresses must be separated by a comma. At least one IP
268 default value is no IP addresses.
617 different peers use different hardware addresses for
804 Uses XOR of hardware MAC addresses and packet type ID
820 Uses XOR of hardware MAC addresses and IP addresses to
830 addresses are first hashed using ipv6_addr_hash.
861 addresses are first hashed using ipv6_addr_hash.
996 devices (the MAC addresses correspond to those of the slave devices).
[all …]
/linux-4.1.27/Documentation/
Dprintk-formats.txt74 Physical addresses types phys_addr_t:
82 DMA addresses types dma_addr_t:
131 MAC/FDDI addresses:
139 For printing 6-byte MAC/FDDI addresses in hex notation. The 'M' and 'm'
143 Where FDDI addresses are concerned the 'F' specifier can be used after
147 For Bluetooth addresses the 'R' specifier shall be used after the 'M'
149 of Bluetooth addresses which are in the little endian order.
153 IPv4 addresses:
159 For printing IPv4 dot-separated decimal addresses. The 'I4' and 'i4'
164 host, network, big or little endian order addresses respectively. Where
[all …]
Dzorro.txt73 they are CPU physical addresses as well.
80 Conversion from bus/physical Zorro II addresses to kernel virtual addresses
Drpmsg.txt68 set to the channel's src and dst addresses.
98 addresses provided by the user.
100 its length (in bytes), and explicit source and destination addresses.
102 channel belongs, but the channel's src and dst addresses will be
103 ignored (and the user-provided addresses will be used instead).
118 set to the channel's src and dst addresses.
142 destination addresses provided by the user.
144 its length (in bytes), and explicit source and destination addresses.
146 channel belongs, but the channel's src and dst addresses will be
147 ignored (and the user-provided addresses will be used instead).
[all …]
DDMA-API-HOWTO.txt12 CPU and DMA addresses
14 There are several kinds of addresses involved in the DMA API, and it's
17 The kernel normally uses virtual addresses. Any address returned by
22 addresses to CPU physical addresses, which are stored as "phys_addr_t" or
24 physical addresses. These are the addresses in /proc/iomem. The physical
30 memory, the addresses used by the device are bus addresses. In some
31 systems, bus addresses are identical to CPU physical addresses, but in
33 mappings between physical and bus addresses.
37 supports 64-bit addresses for main memory and PCI BARs, it may use an IOMMU
38 so devices only need to use 32-bit DMA addresses.
[all …]
Dbus-virt-phys-mapping.txt15 at memory addresses, and in this case we actually want the third, the
30 addresses, with each device seeing memory in some device-specific way, but
61 where all the addresses actually point to the same thing. It's just seen
116 use that from the CPU (the CPU only uses translated virtual addresses), and
125 shouldn't need to know about "bus addresses" etc).
Dunaligned-memory-access.txt72 memory addresses of certain variables, etc.
102 will never cause an unaligned access, because all memory addresses are evenly
142 ethernet MAC addresses for equality.
168 16-bit-aligned addresses. It is up to the caller to ensure this alignment or
242 addresses can be very expensive and dwarf the cost of unaligned loads.
244 For some ethernet hardware that cannot DMA to unaligned addresses like
Dcachetlb.txt61 virtual addresses in the range 'start' to 'end-1'.
171 addresses from the cache. After running, there will be no
172 entries in the cache for 'vma->vm_mm' for virtual addresses in
221 of (kernel) virtual addresses from the cache. After running,
223 space for virtual addresses in the range 'start' to 'end-1'.
266 kernel virtual addresses during the copy. The virtual address
268 load/store instructions happen to virtual addresses which are
370 When the kernel stores into addresses that it will execute
Dio_ordering.txt3 memory-mapped addresses on their device arrive in the order intended. This is
DDMA-ISA-LPC.txt18 The first is the generic DMA API used to convert virtual addresses to
19 bus addresses (see Documentation/DMA-API.txt for details).
Dio-mapping.txt27 Accessing addresses beyond the region specified in the
DIPMI.txt143 The IPMI addressing works much like IP addresses, you have an overlay
154 currently understands two different types of addresses.
156 "System Interface" addresses are defined as:
404 register start addresses. For instance, if the regspacing is set to 4
506 The addresses are normal I2C addresses. The adapter is the string
531 When compiled into the kernel, the addresses can be specified on the
DIntel-IOMMU.txt65 address from PCI MMIO ranges so they are not allocated for IOVA addresses.
Dparport.txt35 addresses should not be specified for supported PCI cards since they
141 base-addr Parallel port's base address, or addresses if the port
Dkmemleak.txt90 the values against the addresses stored in the rbtree. If
93 3. scan the gray objects for matching addresses (some white objects
/linux-4.1.27/Documentation/misc-devices/
Dmax687543 Valid addresses for the MAX6875 are 0x50 and 0x52.
44 Valid addresses for the MAX6874 are 0x50, 0x52, 0x54 and 0x56.
53 addresses. For example, for address 0x50, it also reserves 0x51.
63 The configuration registers are at addresses 0x00 - 0x45.
76 The configuration EEPROM is at addresses 0x8000 - 0x8045.
77 The user EEPROM is at addresses 0x8100 - 0x82ff.
Deeprom63 addresses, is found.
81 multiple addresses.
/linux-4.1.27/Documentation/devicetree/bindings/pci/
Dmvebu-pci.txt62 - assigned-addresses: reference to the MMIO registers used to control
72 standard PCI addresses.
133 assigned-addresses = <0x82000800 0 0x40000 0 0x2000>;
154 assigned-addresses = <0x82001000 0 0x44000 0 0x2000>;
171 assigned-addresses = <0x82001800 0 0x48000 0 0x2000>;
188 assigned-addresses = <0x82002000 0 0x4c000 0 0x2000>;
205 assigned-addresses = <0x82002800 0 0x80000 0 0x2000>;
222 assigned-addresses = <0x82003000 0 0x84000 0 0x2000>;
239 assigned-addresses = <0x82003800 0 0x88000 0 0x2000>;
256 assigned-addresses = <0x82004000 0 0x8c000 0 0x2000>;
[all …]
Dnvidia,tegra20-pcie.txt29 - ranges: Describes the translation of addresses for root ports and standard
34 - The first two entries are expected to translate the addresses for the root
35 port registers, which are referenced by the assigned-addresses property of
114 - assigned-addresses: Address and size of the port configuration registers
162 assigned-addresses = <0x82000800 0 0x80000000 0 0x1000>;
176 assigned-addresses = <0x82001000 0 0x80001000 0 0x1000>;
Dversatile.txt8 - reg: base addresses and lengths of the pci controller. There must be 3
Dsamsung,exynos5440-pcie.txt8 - reg: base addresses and lengths of the pcie controller,
Dlayerscape-pci.txt8 - reg: base addresses and lengths of the PCIe controller
/linux-4.1.27/Documentation/i2c/busses/
Dscx200_acb11 Base addresses for the ACCESS.bus controllers on SCx200 and SC1100 devices
13 By default the driver uses two base addresses 0x820 and 0x840.
26 The SC1100 WRAP boards are known to use base addresses 0x810 and 0x820.
Di2c-piix464 parts of the PIIX4 needs a range of 8 of these addresses to function
65 correctly. If these addresses are already reserved by some other device,
/linux-4.1.27/arch/arm/boot/dts/
Darmada-xp-mv78460.dtsi155 assigned-addresses = <0x82000800 0 0x40000 0 0x2000>;
172 assigned-addresses = <0x82001000 0 0x44000 0 0x2000>;
189 assigned-addresses = <0x82001800 0 0x48000 0 0x2000>;
206 assigned-addresses = <0x82002000 0 0x4c000 0 0x2000>;
223 assigned-addresses = <0x82002800 0 0x80000 0 0x2000>;
240 assigned-addresses = <0x82003000 0 0x84000 0 0x2000>;
257 assigned-addresses = <0x82003800 0 0x88000 0 0x2000>;
274 assigned-addresses = <0x82004000 0 0x8c000 0 0x2000>;
291 assigned-addresses = <0x82004800 0 0x42000 0 0x2000>;
308 assigned-addresses = <0x82005000 0 0x82000 0 0x2000>;
Darmada-xp-mv78260.dtsi134 assigned-addresses = <0x82000800 0 0x40000 0 0x2000>;
151 assigned-addresses = <0x82000800 0 0x44000 0 0x2000>;
168 assigned-addresses = <0x82000800 0 0x48000 0 0x2000>;
185 assigned-addresses = <0x82000800 0 0x4c000 0 0x2000>;
202 assigned-addresses = <0x82000800 0 0x80000 0 0x2000>;
219 assigned-addresses = <0x82000800 0 0x84000 0 0x2000>;
236 assigned-addresses = <0x82000800 0 0x88000 0 0x2000>;
253 assigned-addresses = <0x82000800 0 0x8c000 0 0x2000>;
270 assigned-addresses = <0x82000800 0 0x42000 0 0x2000>;
Darmada-xp-mv78230.dtsi119 assigned-addresses = <0x82000800 0 0x40000 0 0x2000>;
136 assigned-addresses = <0x82000800 0 0x44000 0 0x2000>;
153 assigned-addresses = <0x82000800 0 0x48000 0 0x2000>;
170 assigned-addresses = <0x82000800 0 0x4c000 0 0x2000>;
187 assigned-addresses = <0x82000800 0 0x80000 0 0x2000>;
Darmada-385.dtsi111 assigned-addresses = <0x82000800 0 0x80000 0 0x2000>;
129 assigned-addresses = <0x82000800 0 0x40000 0 0x2000>;
147 assigned-addresses = <0x82000800 0 0x44000 0 0x2000>;
168 assigned-addresses = <0x82000800 0 0x48000 0 0x2000>;
Darmada-380.dtsi100 assigned-addresses = <0x82000800 0 0x80000 0 0x2000>;
118 assigned-addresses = <0x82000800 0 0x40000 0 0x2000>;
136 assigned-addresses = <0x82000800 0 0x44000 0 0x2000>;
Dkirkwood-6282.dtsi24 assigned-addresses = <0x82000800 0 0x00040000 0 0x2000>;
41 assigned-addresses = <0x82001000 0 0x00044000 0 0x2000>;
Dkirkwood-98dx4122.dtsi20 assigned-addresses = <0x82000800 0 0x00040000 0 0x2000>;
Darmada-39x.dtsi426 assigned-addresses = <0x82000800 0 0x80000 0 0x2000>;
444 assigned-addresses = <0x82000800 0 0x40000 0 0x2000>;
462 assigned-addresses = <0x82000800 0 0x44000 0 0x2000>;
483 assigned-addresses = <0x82000800 0 0x48000 0 0x2000>;
Dkirkwood-6281.dtsi20 assigned-addresses = <0x82000800 0 0x00040000 0 0x2000>;
Dkirkwood-6192.dtsi20 assigned-addresses = <0x82000800 0 0x00040000 0 0x2000>;
Darmada-370.dtsi94 assigned-addresses = <0x82000800 0 0x40000 0 0x2000>;
111 assigned-addresses = <0x82002800 0 0x80000 0 0x2000>;
Dtegra30.dtsi52 assigned-addresses = <0x82000800 0 0x00000000 0 0x1000>;
65 assigned-addresses = <0x82001000 0 0x00001000 0 0x1000>;
78 assigned-addresses = <0x82001800 0 0x00004000 0 0x1000>;
Darmada-375.dtsi583 assigned-addresses = <0x82000800 0 0x40000 0 0x2000>;
600 assigned-addresses = <0x82000800 0 0x44000 0 0x2000>;
Ddove.dtsi70 assigned-addresses = <0x82000800 0 0x40000 0 0x2000>;
88 assigned-addresses = <0x82002800 0 0x80000 0 0x2000>;
/linux-4.1.27/arch/mips/sgi-ip27/
DPlatform13 OBJCOPYFLAGS := --change-addresses=0x3fffffff80000000
17 OBJCOPYFLAGS := --change-addresses=0x57ffffff80000000
/linux-4.1.27/net/wireless/
Dsysfs.c56 if (!wiphy->addresses) in addresses_show()
60 buf += sprintf(buf, "%pM\n", &wiphy->addresses[i].addr); in addresses_show()
64 static DEVICE_ATTR_RO(addresses);
Dcore.c598 if (WARN_ON(wiphy->addresses && !wiphy->n_addresses)) in wiphy_register()
601 if (WARN_ON(wiphy->addresses && in wiphy_register()
603 memcmp(wiphy->perm_addr, wiphy->addresses[0].addr, in wiphy_register()
612 if (wiphy->addresses) in wiphy_register()
613 memcpy(wiphy->perm_addr, wiphy->addresses[0].addr, ETH_ALEN); in wiphy_register()
/linux-4.1.27/Documentation/devicetree/bindings/net/
Dbrcm,bcm7445-switch-v4.0.txt6 - reg: addresses and length of the register sets for the device, must be 6
7 pairs of register addresses and lengths
21 - reg-names: litteral names for the device base register addresses, when present
Dcavium-mdio.txt12 - #size-cells: Must be <0>. MDIO addresses have no size component.
Ddavicom-dm9000.txt5 - reg : physical addresses and sizes of registers, must contain 2 entries:
Dcavium-mix.txt9 - reg: The base addresses of four separate register banks. The first
Daltera_tse.txt29 If present, TSE supports additional unicast addresses.
30 Otherwise additional unicast addresses are not supported.
Dmarvell-pp2.txt6 - reg: addresses and length of the register sets for the device.
Drockchip-dwmac.txt7 - reg: addresses and length of the register sets for the device.
/linux-4.1.27/drivers/net/wireless/ti/wlcore/
Dboot.c346 nvs_ptr[11] = wl->addresses[0].addr[0]; in wlcore_boot_upload_nvs()
347 nvs_ptr[10] = wl->addresses[0].addr[1]; in wlcore_boot_upload_nvs()
348 nvs_ptr[6] = wl->addresses[0].addr[2]; in wlcore_boot_upload_nvs()
349 nvs_ptr[5] = wl->addresses[0].addr[3]; in wlcore_boot_upload_nvs()
350 nvs_ptr[4] = wl->addresses[0].addr[4]; in wlcore_boot_upload_nvs()
351 nvs_ptr[3] = wl->addresses[0].addr[5]; in wlcore_boot_upload_nvs()
Dmain.c2614 memcpy(wl->addresses[0].addr, vif->addr, ETH_ALEN); in wl1271_op_add_interface()
5937 wl->addresses[i].addr[0] = (u8)(oui >> 16); in wl12xx_derive_mac_addresses()
5938 wl->addresses[i].addr[1] = (u8)(oui >> 8); in wl12xx_derive_mac_addresses()
5939 wl->addresses[i].addr[2] = (u8) oui; in wl12xx_derive_mac_addresses()
5940 wl->addresses[i].addr[3] = (u8)(nic >> 16); in wl12xx_derive_mac_addresses()
5941 wl->addresses[i].addr[4] = (u8)(nic >> 8); in wl12xx_derive_mac_addresses()
5942 wl->addresses[i].addr[5] = (u8) nic; in wl12xx_derive_mac_addresses()
5955 memcpy(&wl->addresses[idx], &wl->addresses[0], in wl12xx_derive_mac_addresses()
5956 sizeof(wl->addresses[0])); in wl12xx_derive_mac_addresses()
5958 wl->addresses[idx].addr[0] |= BIT(1); in wl12xx_derive_mac_addresses()
[all …]
/linux-4.1.27/Documentation/devicetree/bindings/iommu/
Drockchip,iommu.txt4 A Rockchip DRM iommu translates io virtual addresses to physical addresses for
/linux-4.1.27/Documentation/hwmon/
Dadc128d81845 addresses 0x35 to 0x37. Those addresses are not scanned. You have to instantiate
46 the driver explicitly if the chip is configured for any of those addresses in
Dltc421525 of the possible addresses are unfriendly to probing. You will have to
Dw8379324 This is used to force the i2c addresses for subclients of
26 to force the subclients of chip 0x2f on bus 0 to i2c addresses
Dnct668334 with different register addresses. The specification describing the Intel
Dads782857 some addresses to try to auto-detect it. That means that you will have to
Dw83792d22 This is used to force the i2c addresses for subclients of
24 to force the subclients of chip 0x2f on bus 0 to i2c addresses
Dabituguru-datasheet66 See below for all known bank addresses, numbers of sensors in that bank,
99 Sending bank and sensor addresses to the uGuru
115 First send the bank and sensor addresses as described above.
134 First send the bank and sensor addresses as described above.
Dw83791d44 This is used to force the i2c addresses for subclients of
46 to force the subclients of chip 0x2f on bus 0 to i2c addresses
Dadm102515 * Only two possible addresses (0x2c - 0x2d).
Dltc424526 of the possible addresses are unfriendly to probing. You will have to
/linux-4.1.27/Documentation/serial/
Drocket.txt87 You must assign and configure the I/O addresses used by the ISA Rocketport
96 a range of I/O addresses for it to use. The first RocketPort card
97 requires a 68-byte contiguous block of I/O addresses, starting at one
103 contiguous block of I/O addresses, starting at one of the following
104 I/O addresses: 0x100h, 0x140h, 0x180h, 0x1C0h, 0x200h, 0x240h, 0x280h,
123 identifying what I/O addresses are being used by devices on your
126 Remember, the FIRST RocketPort uses 68 I/O addresses. So, if you set it
/linux-4.1.27/Documentation/devicetree/bindings/misc/
Dsram.txt25 - ranges : standard definition, should translate from local addresses
26 within the sram to bus addresses
/linux-4.1.27/Documentation/input/
Damijoy.txt66 These addresses each read a 16 bit register. These in turn
83 addresses is shown below. Each 6 bit counter (Y7-Y2,X7-X2) is
130 These addresses each read a pair of 8 bit pot counters.
132 addresses is shown below. The counters are stopped by signals
Dgameport-programming.txt20 addresses is preferred, because the likelihood of clashing with the standard
23 Eg. if your driver supports addresses 0x200, 0x208, 0x210 and 0x218, then
31 occupies from one to sixteen addresses in the io space.
37 callback, so that it doesn't fail if some of the possible addresses are
/linux-4.1.27/arch/s390/kernel/
Dhead.S37 .long 0x02000018,0x60000050 # by ipl to addresses 0-23.
41 .long 0x02000140,0x60000050 # to addresses 0x18-0xb7
100 st %r2,4(%r6) # initialize CCW data addresses
137 l %r0,4(%r6) # update CCW data addresses
/linux-4.1.27/Documentation/devicetree/bindings/soc/ti/
Dkeystone-navigator-dma.txt32 navigator cloud and number of addresses depends on SOC integration
34 into DMA and the DMA uses it as the physical addresses to reach queue
35 managers. Note that these addresses though points to queue managers,
/linux-4.1.27/scripts/
Dget_maintainer.pl322 addresses => {}
354 $mailmap->{addresses}->{$wrong_address} = $real_address;
365 $mailmap->{addresses}->{$wrong_address} = $real_address;
383 $mailmap->{addresses}->{$wrong_email} = $real_address;
1212 exists $mailmap->{addresses}->{$email}) {
1216 if (exists $mailmap->{addresses}->{$email}) {
1217 $real_address = $mailmap->{addresses}->{$email};
1223 if (exists $mailmap->{addresses}->{$address}) {
1224 $real_address = $mailmap->{addresses}->{$address};
1231 my (@addresses) = @_;
[all …]
/linux-4.1.27/Documentation/devicetree/bindings/crypto/
Dfsl-sec4.txt69 for representing physical addresses in child nodes.
75 for representing the size of physical addresses in
186 contains up to 5 sets of addresses and their lengths (sizes) that
188 calculated, these addresses are checked by HW to monitor any
202 for representing physical addresses in child nodes. Must
209 for representing the size of physical addresses in
309 for representing physical addresses in child nodes. Must
316 for representing the size of physical addresses in
Dfsl-sec6.txt35 for representing physical addresses in child nodes.
41 for representing the size of physical addresses in
/linux-4.1.27/Documentation/devicetree/bindings/video/
Dti,omap5-dss.txt60 - reg: addresses and lengths of the register spaces for 'proto', 'phy' and 'pll'
82 - reg: addresses and lengths of the register spaces for 'wp', 'pll', 'phy',
Dti,omap4-dss.txt79 - reg: addresses and lengths of the register spaces for 'proto', 'phy' and 'pll'
101 - reg: addresses and lengths of the register spaces for 'wp', 'pll', 'phy',
Dti,dra7-dss.txt55 - reg: addresses and lengths of the register spaces for 'wp', 'pll', 'phy',
Dti,omap3-dss.txt73 - reg: addresses and lengths of the register spaces for 'proto', 'phy' and 'pll'
/linux-4.1.27/net/x25/
Dx25_subr.c120 unsigned char addresses[1 + X25_ADDR_LEN]; in x25_write_internal() local
189 len = x25_addr_aton(addresses, &x25->dest_addr, in x25_write_internal()
192 memcpy(dptr, addresses, len); in x25_write_internal()
/linux-4.1.27/Documentation/virtual/kvm/
Dmmu.txt6 physical addresses to host physical addresses.
59 addresses for the guest. Different translations are required at different
62 - when guest paging is disabled, we translate guest physical addresses to
63 host physical addresses (gpa->hpa)
64 - when guest paging is enabled, we translate guest virtual addresses, to
65 guest physical addresses, to host physical addresses (gva->gpa->hpa)
67 virtual addresses, to nested guest physical addresses, to guest physical
68 addresses, to host physical addresses (ngva->ngpa->gpa->hpa)
79 using kvm. Userspace defines the translation between guest addresses and user
80 addresses (gpa->hva); note that two gpas may alias to the same hva, but not
/linux-4.1.27/Documentation/isdn/
DREADME.hfc-pci27 There tree cards installed in your machine at IO-base addresses 0xd000, 0xd400
34 If the io parameter is used the io addresses of all used cards should be
DsyncPPP.FAQ169 A: You must know, how the ipppd gets the addresses it wanna
174 addresses from the net interface. Or you set the address
/linux-4.1.27/arch/mn10300/mm/
Dcache-flush-by-tag.S56 # read the addresses tagged in the cache's tag RAM and attempt to flush
Dcache-dbg-flush-by-tag.S43 # read the addresses tagged in the cache's tag RAM and attempt to flush
Dcache-flush-by-reg.S94 # Flush a range of addresses on a page in the dcache
227 # Flush and invalidate a range of addresses on a page in the dcache
Dcache-inv-by-reg.S99 # Invalidate a range of addresses on a page in the dcache
Dcache-inv-by-tag.S107 # Invalidate a range of addresses on a page in the dcache
/linux-4.1.27/Documentation/arm/SA1100/
DVictor15 addresses.
/linux-4.1.27/drivers/of/
Daddress.c38 const char *addresses; member
198 prop = of_get_property(dev, bus->addresses, &psize); in of_get_pci_address()
412 .addresses = "assigned-addresses",
423 .addresses = "reg",
433 .addresses = "reg",
651 prop = of_get_property(dev, bus->addresses, &psize); in of_get_address()
/linux-4.1.27/Documentation/devicetree/bindings/i2c/
Dbrcm,iproc-i2c.txt19 Always 1 (for I2C addresses)
Di2c-octeon.txt11 - #size-cells: Must be <0>. I2C addresses have no size component.
Di2c-pnx.txt8 - #address-cells: always 1 (for i2c addresses)
Dqcom,i2c-qup.txt18 - #size-cells: Should be <0> as i2c addresses have no size component
Di2c-mux-pca954x.txt21 multiplexers on the bus and the devices behind them use same I2C addresses.
Di2c-exynos5.txt21 - #address-cells: always 1 (for i2c addresses)
/linux-4.1.27/arch/arm/mach-lpc32xx/
Dsuspend.S44 @ Load a few common register addresses
/linux-4.1.27/net/rxrpc/
Dar-key.c194 if (rxk5->addresses) { in rxrpc_rxk5_free()
196 rxrpc_free_krb5_tagged(&rxk5->addresses[loop]); in rxrpc_rxk5_free()
197 kfree(rxk5->addresses); in rxrpc_rxk5_free()
488 ret = rxrpc_krb5_decode_tagged_array(&rxk5->addresses, in rxrpc_preparse_xdr_rxk5()
1102 toksize += RND(token->k5->addresses[loop].data_len); in rxrpc_read()
1209 ENCODE(token->k5->addresses[loop].tag); in rxrpc_read()
1210 ENCODE_DATA(token->k5->addresses[loop].data_len, in rxrpc_read()
1211 token->k5->addresses[loop].data); in rxrpc_read()
/linux-4.1.27/arch/mips/include/asm/mach-cavium-octeon/
Dkernel-entry-init.h20 # (only 32 bits set by bootloader, all addresses are physical
21 # addresses, and need to have the appropriate memory region set
/linux-4.1.27/Documentation/arm/
DPorting18 virtual or physical addresses here, since the MMU will be off at
94 Virtual addresses bounding the vmalloc() area. There must not be
96 The addresses must also be in the kernel segment (see above).
/linux-4.1.27/Documentation/w1/masters/
Dds248225 Valid addresses are 0x18, 0x19, 0x1a, and 0x1b.
/linux-4.1.27/include/keys/
Drxrpc-type.h79 struct krb5_tagged_data *addresses; /* addresses */ member
/linux-4.1.27/arch/frv/mm/
Dtlb-flush.S126 # flush a range of addresses from the TLB
153 # flush a range of addresses from the TLB
/linux-4.1.27/drivers/vfio/pci/
DKconfig16 region on VGA devices for accessing legacy VGA addresses used by
/linux-4.1.27/drivers/scsi/
Dfdomain.c419 static unsigned long addresses[] = { variable
428 #define ADDRESS_COUNT ARRAY_SIZE(addresses)
677 if (chip != tmc18c30 && !PCI_bus && addresses[(options & 0xc0) >> 6 ] != bios_base) in fdomain_get_irq()
693 void __iomem *p = ioremap(addresses[i], 0x2000); in fdomain_isa_detect()
697 printk( " %lx(%lx),", addresses[i], bios_base ); in fdomain_isa_detect()
707 bios_base = addresses[i]; in fdomain_isa_detect()
DNCR53c406a.c211 static void *addresses[] = { variable
215 #define ADDRESS_COUNT ARRAY_SIZE(addresses)
465 …if (!memcmp((void *) addresses[ii] + signatures[jj].sig_offset, (void *) signatures[jj].signature,… in NCR53c406a_detect()
466 bios_base = addresses[ii]; in NCR53c406a_detect()
/linux-4.1.27/Documentation/devicetree/bindings/arm/omap/
Ddmm.txt7 translation for initiators which need contiguous dma bus addresses.
/linux-4.1.27/Documentation/devicetree/bindings/usb/
Dohci-st.txt6 - reg : physical base addresses of the controller and length of memory mapped
Dehci-st.txt5 - reg : physical base addresses of the controller and length of memory mapped
/linux-4.1.27/arch/x86/realmode/rm/
Dtrampoline_64.S124 # Now jump into the kernel using virtual addresses
/linux-4.1.27/Documentation/devicetree/bindings/mips/cavium/
Dcib.txt10 - reg: Two elements consisting of the addresses of the RAW and EN
/linux-4.1.27/Documentation/devicetree/bindings/interrupt-controller/
Drenesas,intc-irqpin.txt15 addresses, length and number of required register banks varies with soctype.
/linux-4.1.27/drivers/bcma/
DREADME4 Standard AMBA drivers are platform specific, have hardcoded addresses and use
/linux-4.1.27/net/ceph/
DKconfig37 If you say Y here, hostnames (e.g. monitor addresses) will
/linux-4.1.27/arch/arm/include/debug/
Dsa1100.S46 @ clear top bits, and generate both phys and virt addresses
Dtegra.S84 bne 100f @ no; go load the addresses
/linux-4.1.27/drivers/gpu/vga/
DKconfig7 hard-decoded addresses as they did on ISA. When multiple PCI devices
/linux-4.1.27/tools/perf/Documentation/
Dperf-lock.txt27 'perf lock info' shows metadata like threads or addresses
Dperf-report.txt183 - address: compare on individual code addresses
271 Use the addresses of sampled taken branches instead of the instruction
280 Add the addresses of sampled taken branches to the callstack.
298 Use the data addresses of samples in addition to instruction addresses
Dperf-buildid-cache.txt35 the same addresses. Use the -v option to see if a copy of kcore is
/linux-4.1.27/drivers/net/can/sja1000/
DKconfig99 PLD IO base addresses are read from jumpers JP1 and JP2,
101 SJA1000 IO base addresses are chosen heuristically (first that works).
/linux-4.1.27/net/netfilter/ipset/
DKconfig32 can store IPv4 addresses (or network addresse) from a range.
59 can store arbitrary IPv4 or IPv6 addresses (or network addresses)
/linux-4.1.27/Documentation/video4linux/cx2341x/
Dfw-dma.txt64 Card "addresses" are derived from the offset supplied by Mailbox #10. Host
65 addresses are the physical memory location of the target DMA buffer.
/linux-4.1.27/Documentation/scsi/
Dsym53c500_cs.txt3 long overdue, and the current version addresses the following concerns:
Ddtc3x80.txt21 The driver detects the possible memory addresses (jumper selectable):
Dg_NCR5380.txt32 The driver does not probe for any addresses or ports other than those in
/linux-4.1.27/arch/arm/nwfpe/
Dentry.S79 mov r4, lr @ save the failure-return addresses
/linux-4.1.27/Documentation/devicetree/bindings/ata/
Dahci-st.txt7 - reg : Physical base addresses and length of register sets
/linux-4.1.27/Documentation/ABI/testing/
Dsysfs-firmware-efi-runtime-map6 bit set to be mapped to virtual addresses.
/linux-4.1.27/drivers/net/wireless/zd1211rw/
Dzd_chip.h809 const zd_addr_t *addresses, in zd_ioread16v_locked() argument
813 return zd_usb_ioread16v(&chip->usb, values, addresses, count); in zd_ioread16v_locked()
824 const zd_addr_t *addresses, unsigned int count);
884 int zd_ioread32v(struct zd_chip *chip, const zd_addr_t *addresses,
Dzd_usb.h271 const zd_addr_t *addresses, unsigned int count);
Dzd_chip.c308 int zd_ioread32v(struct zd_chip *chip, const zd_addr_t *addresses, in zd_ioread32v() argument
314 r = zd_ioread32v_locked(chip, values, addresses, count); in zd_ioread32v()
486 static const zd_addr_t addresses[] = { in read_ofdm_cal_values() local
494 E2P_CHANNEL_COUNT, addresses[i], 0); in read_ofdm_cal_values()
/linux-4.1.27/Documentation/trace/
Dmmiotrace.txt101 Access to hardware IO-memory is gained by mapping addresses from PCI bus by
151 physical addresses in the range [0xfb73ce40, 0xfb800000[
161 - replacing numeric addresses and values with hardware register names
/linux-4.1.27/arch/alpha/lib/
Dev6-memset.S161 subq $3, 24, $2 # E : For determining future wh64 addresses
338 subq $3, 24, $2 # E : For determining future wh64 addresses
525 subq $3, 24, $2 # E : For determining future wh64 addresses
/linux-4.1.27/Documentation/sound/oss/
DESS186820 For configuring the sound card's I/O addresses, IRQ and DMA, here is a
DPSS13 This is normally 0x530, but may be 0x604 or other addresses.
DAudioExcelDSP1626 set up I/O addresses, IRQ lines and DMA channels. Some parameters are
/linux-4.1.27/Documentation/metag/
Dkernel-ABI.txt166 from low addresses to high addresses in the metag ABI. The stack pointer (A0StP)
194 addresses):
/linux-4.1.27/Documentation/filesystems/
Dafs.txt65 list of volume location server IP addresses:
163 IP addresses of the volume location servers for those cells. The cell to which
223 Here's what I use to test this. Some of the names and IP addresses are local
Dlogfs.txt33 writes happen from front (low addresses) to back (high addresses. If
/linux-4.1.27/Documentation/mtd/
Dspi-nor.txt14 opcodes, addresses, or data payloads; a SPI controller simply knows to send or
/linux-4.1.27/Documentation/devicetree/bindings/c6x/
Ddscr.txt16 provide device ID information, provide ethernet MAC addresses, as well as other
56 MAC addresses are contained in two registers. Each element of a MAC address
/linux-4.1.27/drivers/net/wireless/iwlwifi/dvm/
Dmain.c1311 memcpy(priv->addresses[0].addr, priv->nvm_data->hw_addr, ETH_ALEN); in iwl_op_mode_dvm_start()
1312 IWL_DEBUG_INFO(priv, "MAC address: %pM\n", priv->addresses[0].addr); in iwl_op_mode_dvm_start()
1313 priv->hw->wiphy->addresses = priv->addresses; in iwl_op_mode_dvm_start()
1317 memcpy(priv->addresses[1].addr, priv->addresses[0].addr, in iwl_op_mode_dvm_start()
1319 priv->addresses[1].addr[5]++; in iwl_op_mode_dvm_start()
/linux-4.1.27/Documentation/devicetree/bindings/dma/
Dfsl-imx-sdma.txt12 correct ROM script addresses needed for the driver to work without additional
/linux-4.1.27/arch/arm/
DKconfig-nommu9 Say Y to manually set the base addresses and sizes.
/linux-4.1.27/drivers/hwmon/
Dasc7621.c55 const unsigned short *addresses; member
66 .addresses = normal_i2c,
75 .addresses = normal_i2c,
1067 for (i = 0; asc7621_chips[chip_type].addresses[i] != I2C_CLIENT_END; in valid_address_for_chip()
1069 if (asc7621_chips[chip_type].addresses[i] == address) in valid_address_for_chip()
/linux-4.1.27/Documentation/powerpc/
Dpci_iov_resource_on_powernv.txt105 * Do not translate addresses (the address on PCIe is the same as the
131 because the addresses we use directly determine the PE#. We then
162 discover the BAR sizes and assign addresses for them. For VF devices,
164 discover sizes and assign addresses. The BARs in the VF's config space
199 use several M64 windows, they can be set to different base addresses
Dptrace.txt24 watchpoints and whether it supports a range of addresses and a condition.
/linux-4.1.27/arch/powerpc/boot/dts/
Dbsc9131rdb.dtsi2 * BSC9131 RDB Device Tree Source stub (no addresses or top-level ranges)
Dp1010rdb_32b.dtsi2 * P1010 RDB Device Tree Source stub (no addresses or top-level ranges)
Dbsc9132qds.dtsi2 * BSC9132 QDS Device Tree Source stub (no addresses or top-level ranges)
Dp1010rdb-pa.dtsi2 * P1010 RDB Device Tree Source stub (no addresses or top-level ranges)
Dp1010rdb_36b.dtsi2 * P1010 RDB Device Tree Source stub (no addresses or top-level ranges)
Dp1020utm-pc.dtsi2 * P1020 UTM-PC Device Tree Source stub (no addresses or top-level ranges)
Dp1020mbg-pc.dtsi2 * P1020 MBG-PC Device Tree Source stub (no addresses or top-level ranges)
Dmpc8544ds.dtsi2 * MPC8544DS Device Tree Source stub (no addresses or top-level ranges)
Dmpc8536ds.dtsi2 * MPC8536DS Device Tree Source stub (no addresses or top-level ranges)
Dp1010rdb.dtsi2 * P1010 RDB Device Tree Source stub (no addresses or top-level ranges)
Dp1022ds.dtsi2 * P1022 DS Device Tree Source stub (no addresses or top-level ranges)
Dp1024rdb.dtsi2 * P1024 RDB Device Tree Source stub (no addresses or top-level ranges)
/linux-4.1.27/drivers/net/team/
DKconfig59 Mac addresses of ports are not modified. Userspace is responsible
/linux-4.1.27/Documentation/devicetree/bindings/phy/
Dphy-miphy365x.txt27 - reg-names : The names of the register addresses corresponding to the
Dphy-miphy28lp.txt25 - reg-names : The names of the register addresses corresponding to the registers
Dti-phy.txt64 - reg-names: The names of the register addresses corresponding to the registers
/linux-4.1.27/arch/arm/kernel/
Dhead-common.S156 add r5, r5, r3 @ convert virt addresses to
/linux-4.1.27/Documentation/devicetree/bindings/mfd/
Ds2mpa01.txt8 addresses.
Ds2mps11.txt7 addressed by the host system using different I2C slave addresses.
/linux-4.1.27/Documentation/devicetree/
Dbooting-without-of.txt474 need to be in that order) looks like this (addresses go from top to
715 addresses format for devices directly mapped on the processor bus.
725 Some 32-bit processors allow for physical addresses greater than 32
741 then, to provide a separate "assigned-addresses" property that
742 contains the fully allocated addresses. See the PCI OF bindings for
752 The "reg" property only defines addresses and sizes (if #size-cells is
753 non-0) within a given bus. In order to translate addresses upward
754 (that is into parent bus addresses, and possibly into CPU physical
755 addresses), all buses must contain a "ranges" property. If the
765 address, size) defines a range of addresses for child devices. "parent
[all …]
/linux-4.1.27/Documentation/devicetree/bindings/mtd/
Ddavinci-nand.txt40 addresses for given chipselect.
/linux-4.1.27/Documentation/devicetree/bindings/arm/
Darch_timer.txt67 - reg : The first and second view base addresses in that order. The second view
Dl2cc.txt46 addresses will go to the M0 port.
/linux-4.1.27/net/ipv4/netfilter/
DKconfig139 conflicting addresses. It works by modifying IP addresses
401 hardware and network addresses.
/linux-4.1.27/net/ipv6/
DKconfig46 Address Detection. It allows for autoconfigured addresses
247 destination addresses. If you say Y here, the multicast router
/linux-4.1.27/arch/frv/kernel/
Dcmode.S98 # Set up addresses in regs for later steps.
/linux-4.1.27/Documentation/power/regulator/
Dconsumer.txt197 regulator, addresses of various regulator registers etc. need to be configured
201 Bus-specific details, like I2C addresses or transfer rates are handled by the
/linux-4.1.27/Documentation/frv/
Dmmu-layout.txt15 16KB range of addresses, but can match a larger region.
92 addresses by installing a PTE in a special page table. The kernel can then access this page as it
131 see it directly. The kernel translates page references into real addresses for communicating to the
/linux-4.1.27/drivers/memory/
DKconfig78 physical addresses that mapped by no local access window
/linux-4.1.27/Documentation/usb/
Dgadget-testing.txt82 Configure IP addresses of the device and the host. Then:
115 Configure IP addresses of the device and the host. Then:
148 Configure IP addresses of the device and the host. Then:
406 Configure IP addresses of the device and the host. Then:
532 Configure IP addresses of the device and the host. Then:
/linux-4.1.27/Documentation/m68k/
DREADME.buddha94 chip. The addresses $0 to $fff of the rom
96 mapped to even addresses.
/linux-4.1.27/drivers/net/hamradio/
DKconfig65 possible I/O addresses are probed. This could irritate other devices
66 that are currently not in use. You may specify the list of addresses
/linux-4.1.27/net/ipv4/
DKconfig42 host which has several IP addresses on different interfaces. To turn
110 This enables automatic configuration of IP addresses of devices and
175 networks without changing their IP addresses).
220 packets that have several destination addresses. It is needed on the
233 destination addresses. If you say Y here, the multicast router
/linux-4.1.27/drivers/net/
DKconfig125 or from specific MAC addresses to a particular interface.
194 parameters (interface, IP addresses, port numbers, MAC addresses)
/linux-4.1.27/Documentation/devicetree/bindings/leds/
Dleds-lp55xx.txt63 Available addresses are 32/33/34/35h.
/linux-4.1.27/Documentation/devicetree/bindings/powerpc/fsl/cpm_qe/
Dqe.txt55 translation of MURAM addresses.
/linux-4.1.27/drivers/iommu/
DKconfig154 to use physical addresses for DMA, at least until this
267 devices) of the IP blocks on the ICB *must* use addresses
/linux-4.1.27/Documentation/devicetree/bindings/powerpc/fsl/
Ddcsr.txt31 or representing physical addresses in child nodes.
37 or representing the size of physical addresses in

12