| /OK3568_Linux_fs/kernel/Documentation/hwmon/ |
| H A D | isl68137.rst | 10 Addresses scanned: -
21 Addresses scanned: -
31 Addresses scanned: -
41 Addresses scanned: -
51 Addresses scanned: -
61 Addresses scanned: -
71 Addresses scanned: -
81 Addresses scanned: -
91 Addresses scanned: -
101 Addresses scanned: -
[all …]
|
| H A D | lm90.rst | 10 Addresses scanned: I2C 0x4c
20 Addresses scanned: I2C 0x4c and 0x4d
30 Addresses scanned: I2C 0x4c and 0x4d
40 Addresses scanned: I2C 0x4c
50 Addresses scanned: I2C 0x4c and 0x4d
60 Addresses scanned: I2C 0x4c and 0x4d
70 Addresses scanned: I2C 0x4c and 0x4d
80 Addresses scanned: I2C 0x4c and 0x4d
90 Addresses scanned: I2C 0x4d
100 Addresses scanned: I2C 0x4e
[all …]
|
| H A D | ltc2978.rst | 10 Addresses scanned: -
18 Addresses scanned: -
26 Addresses scanned: -
34 Addresses scanned: -
42 Addresses scanned: -
52 Addresses scanned: -
60 Addresses scanned: -
68 Addresses scanned: -
76 Addresses scanned: -
84 Addresses scanned: -
[all …]
|
| H A D | f71882fg.rst | 10 Addresses scanned: none, address read from Super I/O config space
18 Addresses scanned: none, address read from Super I/O config space
26 Addresses scanned: none, address read from Super I/O config space
34 Addresses scanned: none, address read from Super I/O config space
42 Addresses scanned: none, address read from Super I/O config space
50 Addresses scanned: none, address read from Super I/O config space
58 Addresses scanned: none, address read from Super I/O config space
66 Addresses scanned: none, address read from Super I/O config space
74 Addresses scanned: none, address read from Super I/O config space
82 Addresses scanned: none, address read from Super I/O config space
[all …]
|
| H A D | it87.rst | 10 Addresses scanned: from Super I/O config space (8 I/O ports)
18 Addresses scanned: from Super I/O config space (8 I/O ports)
24 Addresses scanned: from Super I/O config space (8 I/O ports)
32 Addresses scanned: from Super I/O config space (8 I/O ports)
40 Addresses scanned: from Super I/O config space (8 I/O ports)
48 Addresses scanned: from Super I/O config space (8 I/O ports)
56 Addresses scanned: from Super I/O config space (8 I/O ports)
64 Addresses scanned: from Super I/O config space (8 I/O ports)
72 Addresses scanned: from Super I/O config space (8 I/O ports)
80 Addresses scanned: from Super I/O config space (8 I/O ports)
[all …]
|
| H A D | lm75.rst | 10 Addresses scanned: I2C 0x48 - 0x4f
20 Addresses scanned: I2C 0x48 - 0x4f
30 Addresses scanned: none
40 Addresses scanned: none
50 Addresses scanned: none
60 Addresses scanned: none
70 Addresses scanned: none
80 Addresses scanned: none
90 Addresses scanned: none
100 Addresses scanned: none
[all …]
|
| H A D | adm1021.rst | 10 Addresses scanned: I2C 0x18 - 0x1a, 0x29 - 0x2b, 0x4c - 0x4e
18 Addresses scanned: I2C 0x18 - 0x1a, 0x29 - 0x2b, 0x4c - 0x4e
26 Addresses scanned: I2C 0x18 - 0x1a, 0x29 - 0x2b, 0x4c - 0x4e
34 Addresses scanned: I2C 0x18 - 0x1a, 0x29 - 0x2b, 0x4c - 0x4e
42 Addresses scanned: I2C 0x18 - 0x1a, 0x29 - 0x2b, 0x4c - 0x4e
50 Addresses scanned: I2C 0x18 - 0x1a, 0x29 - 0x2b, 0x4c - 0x4e
58 Addresses scanned: I2C 0x18 - 0x1a, 0x29 - 0x2b, 0x4c - 0x4e
66 Addresses scanned: I2C 0x18 - 0x1a, 0x29 - 0x2b, 0x4c - 0x4e
74 Addresses scanned: I2C 0x18 - 0x1a, 0x29 - 0x2b, 0x4c - 0x4e
82 Addresses scanned: I2C 0x18 - 0x1a, 0x29 - 0x2b, 0x4c - 0x4e
[all …]
|
| H A D | zl6100.rst | 10 Addresses scanned: -
18 Addresses scanned: -
26 Addresses scanned: -
34 Addresses scanned: -
42 Addresses scanned: -
50 Addresses scanned: -
58 Addresses scanned: -
66 Addresses scanned: -
74 Addresses scanned: -
82 Addresses scanned: -
[all …]
|
| H A D | tmp421.rst | 10 Addresses scanned: I2C 0x2a, 0x4c, 0x4d, 0x4e and 0x4f
18 Addresses scanned: I2C 0x4c, 0x4d, 0x4e and 0x4f
26 Addresses scanned: I2C 0x4c and 0x4d
34 Addresses scanned: I2C 0x2a, 0x4c, 0x4d, 0x4e and 0x4f
42 Addresses scanned: I2C 0x4c and 0x4d
|
| /OK3568_Linux_fs/kernel/Documentation/i2c/ |
| H A D | ten-bit-addresses.rst | 2 I2C Ten-bit Addresses
5 The I2C protocol knows about two kinds of device addresses: normal 7 bit
6 addresses, and an extended set of 10 bit addresses. The sets of addresses
9 To avoid ambiguity, the user sees 10 bit addresses mapped to a different
20 * Not all bus drivers support 10-bit addresses. Some don't because the
25 * Some optional features do not support 10-bit addresses. This is the
29 10-bit addresses.
|
| /OK3568_Linux_fs/kernel/net/core/ |
| H A D | dev_addr_lists.c | 7 * addresses lists.
189 * sync addresses to more then 1 destination, you need to use
234 * the addresses requiring removal will simply be removed without
287 * the addresses or references on it requiring removal will simply be
338 * __hw_addr_ref_unsync_dev - Remove synchronized addresses and references on
340 * @list: address list to remove synchronized addresses (references on it) from
344 * Remove all addresses that were added to the device by
349 * addresses in the list.
374 * __hw_addr_unsync_dev - Remove synchronized addresses from device
375 * @list: address list to remove synchronized addresses from
[all …]
|
| /OK3568_Linux_fs/kernel/Documentation/networking/ |
| H A D | ipv6.rst | 25 IPv6 addresses or operations are desired.
37 No IPv6 addresses will be added to interfaces, and
46 for addresses to be automatically generated from prefixes
54 Only the IPv6 loopback address (::1) and link-local addresses
65 This might be used when no IPv6 addresses are desired.
77 No IPv6 addresses will be added to interfaces.
|
| H A D | decnet.rst | 51 which is that its added to the addresses on the loopback device.
53 With 2.4 kernels, DECnet would only recognise addresses as local if they
56 prevent you adding further addresses to the loopback device if you
59 N.B. Since the address list of an interface determines the addresses for
125 IP and DECnet, albeit with DECnet addresses instead of IP addresses and
192 -e flag also provides very useful information (ethernet MAC addresses))
197 A quick FAQ on ethernet MAC addresses to explain how Linux and DECnet
203 Linux has an interface which allows the setting of extra addresses for
214 addresses on each physical interface. If you do this, be aware that if your
218 packets from the DECnet specified addresses. So if you have one of these
|
| /OK3568_Linux_fs/kernel/Documentation/parisc/ |
| H A D | debugging.rst | 9 1. Absolute addresses
13 absolute addresses are used instead of virtual addresses as in the
24 the System Responder/Requestor addresses. The System Requestor
25 address should match (one of the) processor HPAs (high addresses in
29 Typical values for the System Responder address are addresses larger
|
| /OK3568_Linux_fs/kernel/Documentation/arm64/ |
| H A D | tagged-pointers.rst | 2 Tagged virtual addresses in AArch64 Linux
10 addresses in the AArch64 translation system and their potential uses
19 Passing tagged addresses to the kernel
22 All interpretation of userspace memory addresses by the kernel assumes
27 This includes, but is not limited to, addresses found in:
60 on the tag information for user virtual addresses being maintained
87 likely that C compilers will not hazard two virtual addresses differing
|
| /OK3568_Linux_fs/kernel/Documentation/userspace-api/media/cec/ |
| H A D | cec-ioc-adap-g-log-addrs.rst | 15 CEC_ADAP_G_LOG_ADDRS, CEC_ADAP_S_LOG_ADDRS - Get or set the logical addresses
40 To query the current CEC logical addresses, applications call
42 struct :c:type:`cec_log_addrs` where the driver stores the logical addresses.
44 To set new logical addresses, applications fill in
52 To clear existing logical addresses set ``num_log_addrs`` to 0. All other fields
59 addresses have been claimed. If the file descriptor is in non-blocking mode then it will
60 not wait for the logical addresses to be claimed, instead it just returns 0.
63 logical addresses are claimed or cleared.
81 - The actual logical addresses that were claimed. This is set by the
88 - The bitmask of all logical addresses this adapter has claimed. If
[all …]
|
| /OK3568_Linux_fs/prebuilts/gcc/linux-x86/arm/gcc-arm-10.3-2021.07-x86_64-arm-none-linux-gnueabihf/share/doc/ld.html/ |
| H A D | Expression-Section.html | 78 <p>Addresses and symbols may be section relative, or absolute. A section
85 <p>Some terms in linker expressions are addresses. This is true of
94 section definition treat all numbers as absolute addresses.
122 <p>For expressions involving numbers, relative addresses and absolute
123 addresses, ld follows these rules to evaluate terms:
127 operations on two absolute addresses or two numbers, or between one
130 relative addresses in the same section or between one relative address
132 </li><li> Other binary operations, that is, between two relative addresses not
144 relative addresses in the same section or two absolute addresses
148 </li><li> The result of other operations on relative addresses or one
[all …]
|
| /OK3568_Linux_fs/prebuilts/gcc/linux-x86/aarch64/gcc-arm-10.3-2021.07-x86_64-aarch64-none-linux-gnu/share/doc/ld.html/ |
| H A D | Expression-Section.html | 78 <p>Addresses and symbols may be section relative, or absolute. A section
85 <p>Some terms in linker expressions are addresses. This is true of
94 section definition treat all numbers as absolute addresses.
122 <p>For expressions involving numbers, relative addresses and absolute
123 addresses, ld follows these rules to evaluate terms:
127 operations on two absolute addresses or two numbers, or between one
130 relative addresses in the same section or between one relative address
132 </li><li> Other binary operations, that is, between two relative addresses not
144 relative addresses in the same section or two absolute addresses
148 </li><li> The result of other operations on relative addresses or one
[all …]
|
| /OK3568_Linux_fs/kernel/Documentation/misc-devices/ |
| H A D | max6875.rst | 11 Addresses scanned: None (see below)
51 Valid addresses for the MAX6875 are 0x50 and 0x52.
53 Valid addresses for the MAX6874 are 0x50, 0x52, 0x54 and 0x56.
64 addresses. For example, for address 0x50, it also reserves 0x51.
75 The configuration registers are at addresses 0x00 - 0x45.
93 The configuration EEPROM is at addresses 0x8000 - 0x8045.
95 The user EEPROM is at addresses 0x8100 - 0x82ff.
|
| /OK3568_Linux_fs/kernel/arch/arm/mach-ux500/ |
| H A D | db8500-regs.h | 72 /* per6 base addresses */
85 /* per5 base addresses */
89 /* per4 base addresses */
104 /* per3 base addresses */
115 /* per2 base addresses */
129 /* per1 base addresses */
160 /* Modem and APE physical addresses */
167 /* Offsets to specific addresses in some IP blocks for DMA */
|
| /OK3568_Linux_fs/kernel/Documentation/core-api/ |
| H A D | dma-api-howto.rst | 13 CPU and DMA addresses
16 There are several kinds of addresses involved in the DMA API, and it's
19 The kernel normally uses virtual addresses. Any address returned by
24 addresses to CPU physical addresses, which are stored as "phys_addr_t" or
26 physical addresses. These are the addresses in /proc/iomem. The physical
32 memory, the addresses used by the device are bus addresses. In some
33 systems, bus addresses are identical to CPU physical addresses, but in
35 mappings between physical and bus addresses.
39 supports 64-bit addresses for main memory and PCI BARs, it may use an IOMMU
40 so devices only need to use 32-bit DMA addresses.
[all …]
|
| /OK3568_Linux_fs/u-boot/arch/arm/include/asm/ |
| H A D | types.h | 52 /* DMA addresses are 32-bits wide */
61 * If the DMA API only uses 32-bit addresses, dma_addr_t need only be 32
62 * bits wide. Bus addresses, e.g., PCI BARs, may be wider than 32 bits,
63 * but drivers do memory-mapped I/O to ioremapped kernel virtual addresses,
64 * so they don't care about the size of the actual bus addresses.
|
| /OK3568_Linux_fs/kernel/arch/alpha/kernel/ |
| H A D | pci_impl.h | 30 * We try to make the DEFAULT_MEM_BASE addresses *always* have more than
40 * PCI bus devices' memory addresses *below* the low DMA mapping window,
50 * APECS and LCA have only 34 bits for physical addresses, thus limiting PCI
51 * bus memory addresses for SPARSE access to be less than 128Mb.
57 * physical addresses, they should allow an expanded range of SPARSE
58 * memory addresses. However, we do not use them all, in order to
65 * Because CIA and PYXIS have more bits for physical addresses,
66 * they support an expanded range of SPARSE memory addresses.
|
| /OK3568_Linux_fs/prebuilts/gcc/linux-x86/arm/gcc-arm-10.3-2021.07-x86_64-arm-none-linux-gnueabihf/share/doc/as.html/ |
| H A D | Secs-Background.html | 72 <p>Roughly, a section is a range of addresses, with no gaps; all data
73 “in” those addresses is treated the same for some particular purpose.
81 <code>ld</code> assigns the final addresses for the partial program, so that
87 addresses. These blocks slide to their run-time addresses as rigid
90 run-time addresses to sections is called <em>relocation</em>. It includes
91 the task of adjusting mentions of object-file addresses so they refer to
92 the proper run-time addresses.
159 addresses in the absolute section remain unchanged. For example, address
162 data sections with overlapping addresses after linking, <em>by definition</em>
177 sections in contiguous addresses in the linked program. It is
[all …]
|
| /OK3568_Linux_fs/prebuilts/gcc/linux-x86/aarch64/gcc-arm-10.3-2021.07-x86_64-aarch64-none-linux-gnu/share/doc/as.html/ |
| H A D | Secs-Background.html | 72 <p>Roughly, a section is a range of addresses, with no gaps; all data
73 “in” those addresses is treated the same for some particular purpose.
81 <code>ld</code> assigns the final addresses for the partial program, so that
87 addresses. These blocks slide to their run-time addresses as rigid
90 run-time addresses to sections is called <em>relocation</em>. It includes
91 the task of adjusting mentions of object-file addresses so they refer to
92 the proper run-time addresses.
159 addresses in the absolute section remain unchanged. For example, address
162 data sections with overlapping addresses after linking, <em>by definition</em>
177 sections in contiguous addresses in the linked program. It is
[all …]
|