| /kernel/linux/linux-5.10/Documentation/arm64/ |
| D | elf_hwcaps.rst | 51 Functionality implied by idreg.field == val.
53 Such hwcaps indicate the availability of functionality that the ARM ARM
56 indicate the absence of functionality implied by other values of
68 Functionality implied by ID_AA64PFR0_EL1.FP == 0b0000.
71 Functionality implied by ID_AA64PFR0_EL1.AdvSIMD == 0b0000.
78 Functionality implied by ID_AA64ISAR0_EL1.AES == 0b0001.
81 Functionality implied by ID_AA64ISAR0_EL1.AES == 0b0010.
84 Functionality implied by ID_AA64ISAR0_EL1.SHA1 == 0b0001.
87 Functionality implied by ID_AA64ISAR0_EL1.SHA2 == 0b0001.
90 Functionality implied by ID_AA64ISAR0_EL1.CRC32 == 0b0001.
[all …]
|
| /kernel/linux/linux-4.19/Documentation/arm64/ |
| D | elf_hwcaps.txt | 50 Functionality implied by idreg.field == val.
52 Such hwcaps indicate the availability of functionality that the ARM ARM
55 indicate the absence of functionality implied by other values of
68 Functionality implied by ID_AA64PFR0_EL1.FP == 0b0000.
72 Functionality implied by ID_AA64PFR0_EL1.AdvSIMD == 0b0000.
81 Functionality implied by ID_AA64ISAR1_EL1.AES == 0b0001.
85 Functionality implied by ID_AA64ISAR1_EL1.AES == 0b0010.
89 Functionality implied by ID_AA64ISAR0_EL1.SHA1 == 0b0001.
93 Functionality implied by ID_AA64ISAR0_EL1.SHA2 == 0b0001.
97 Functionality implied by ID_AA64ISAR0_EL1.CRC32 == 0b0001.
[all …]
|
| /kernel/linux/linux-5.10/drivers/mfd/ |
| D | Kconfig | 20 necessary for using the board's GPIO and MFGPT functionality.
111 functionality of the device.
143 functionality of the device.
245 core functionality controlled via I2C.
254 core functionality controlled via SPI.
325 order to use the functionality of the device.
337 order to use the functionality of the device.
349 Additional drivers must be enabled in order to use the functionality
365 Additional drivers must be enabled in order to use the functionality
377 Additional drivers must be enabled in order to use the functionality
[all …]
|
| /kernel/linux/linux-4.19/Documentation/i2c/ |
| D | smbus-protocol | 26 Each transaction type corresponds to a functionality flag. Before calling a
28 the corresponding functionality flag to ensure that the underlying I2C
30 <file:Documentation/i2c/functionality> for the details.
58 Functionality flag: I2C_FUNC_SMBUS_QUICK
71 Functionality flag: I2C_FUNC_SMBUS_READ_BYTE
82 Functionality flag: I2C_FUNC_SMBUS_WRITE_BYTE
93 Functionality flag: I2C_FUNC_SMBUS_READ_BYTE_DATA
105 Functionality flag: I2C_FUNC_SMBUS_READ_WORD_DATA
121 Functionality flag: I2C_FUNC_SMBUS_WRITE_BYTE_DATA
133 Functionality flag: I2C_FUNC_SMBUS_WRITE_WORD_DATA
[all …]
|
| D | functionality | 8 functionality.
11 FUNCTIONALITY CONSTANTS
14 For the most up-to-date list of functionality constants, please check
61 function callback `functionality'. Typical implementations are given
96 check whether the needed functionality is present. The typical way to do
114 thumb, the functionality constants you test for with
130 functionality you need is supported, of course. This is done using
144 /* Oops, the needed functionality (SMBus write_quick function) is
|
| /kernel/linux/linux-5.10/Documentation/i2c/ |
| D | smbus-protocol.rst | 27 Each transaction type corresponds to a functionality flag. Before calling a
29 the corresponding functionality flag to ensure that the underlying I2C
30 adapter supports the transaction in question. See :doc:`functionality` for
62 Functionality flag: I2C_FUNC_SMBUS_QUICK
77 Functionality flag: I2C_FUNC_SMBUS_READ_BYTE
92 Functionality flag: I2C_FUNC_SMBUS_WRITE_BYTE
105 Functionality flag: I2C_FUNC_SMBUS_READ_BYTE_DATA
119 Functionality flag: I2C_FUNC_SMBUS_READ_WORD_DATA
139 Functionality flag: I2C_FUNC_SMBUS_WRITE_BYTE_DATA
153 Functionality flag: I2C_FUNC_SMBUS_WRITE_WORD_DATA
[all …]
|
| D | functionality.rst | 2 I2C/SMBus Functionality
12 functionality.
15 FUNCTIONALITY CONSTANTS
18 For the most up-to-date list of functionality constants, please check
69 function callback ``functionality``. Typical implementations are given
104 check whether the needed functionality is present. The typical way to do
122 thumb, the functionality constants you test for with
138 functionality you need is supported, of course. This is done using
152 /* Oops, the needed functionality (SMBus write_quick function) is
|
| /kernel/linux/linux-4.19/drivers/mfd/ |
| D | Kconfig | 19 necessary for using the board's GPIO and MFGPT functionality.
100 functionality of the device.
122 functionality of the device.
233 core functionality controlled via I2C.
242 core functionality controlled via SPI.
298 order to use the functionality of the device.
310 order to use the functionality of the device.
322 Additional drivers must be enabled in order to use the functionality
338 Additional drivers must be enabled in order to use the functionality
350 Additional drivers must be enabled in order to use the functionality
[all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/mfd/ |
| D | twl4030-audio.txt | 11 Audio functionality:
12 - codec { }: Need to be present if the audio functionality is used. Within this
22 Vibra functionality
23 - ti,enable-vibra: Need to be set to <1> if the vibra functionality is used. if
24 missing or it is 0, the vibra functionality is disabled.
|
| /kernel/linux/linux-4.19/Documentation/devicetree/bindings/mfd/ |
| D | twl4030-audio.txt | 11 Audio functionality:
12 - codec { }: Need to be present if the audio functionality is used. Within this
22 Vibra functionality
23 - ti,enable-vibra: Need to be set to <1> if the vibra functionality is used. if
24 missing or it is 0, the vibra functionality is disabled.
|
| /kernel/linux/linux-4.19/drivers/staging/greybus/ |
| D | i2c.c | 21 u32 functionality; member
27 * Map Greybus i2c functionality bits into Linux ones
37 u32 functionality; in gb_i2c_functionality_operation() local
46 functionality = le32_to_cpu(response.functionality); in gb_i2c_functionality_operation()
47 gb_i2c_dev->functionality = gb_i2c_functionality_map(functionality); in gb_i2c_functionality_operation()
229 return gb_i2c_dev->functionality; in gb_i2c_functionality()
235 .functionality = gb_i2c_functionality,
241 * If that's OK, we get and cached its functionality bits.
247 /* Assume the functionality never changes, just get it once */ in gb_i2c_device_setup()
|
| /kernel/linux/linux-5.10/drivers/staging/greybus/ |
| D | i2c.c | 21 u32 functionality; member
27 * Map Greybus i2c functionality bits into Linux ones
37 * If that's OK, we get and cached its functionality bits.
44 u32 functionality; in gb_i2c_device_setup() local
53 functionality = le32_to_cpu(response.functionality); in gb_i2c_device_setup()
54 gb_i2c_dev->functionality = gb_i2c_functionality_map(functionality); in gb_i2c_device_setup()
222 return gb_i2c_dev->functionality; in gb_i2c_functionality()
227 .functionality = gb_i2c_functionality,
|
| /kernel/linux/linux-5.10/drivers/clk/qcom/ |
| D | Kconfig | 275 functionality such as 3D graphics.
299 Say Y if you want to support display devices and functionality such as
326 functionality such as 3D graphics.
342 Say Y if you want to support video devices and functionality such as
350 Say Y if you want to support camera devices and camera functionality.
388 functionality such as 3D graphics.
396 Say Y if you want to support video devices and functionality such as
405 Say Y if you want to support display devices and functionality such as
422 Say Y if you want to support display devices and functionality such as
446 functionality such as 3D graphics.
[all …]
|
| /kernel/linux/linux-5.10/Documentation/timers/ |
| D | highres.rst | 26 - high resolution timer functionality
55 related functionality is moved into the generic code. The GTOD base patch got
82 functionality like high resolution timers or dynamic ticks.
90 architectures as it provides generic functionality down to the interrupt
101 event devices are used to provide local CPU functionality such as process
117 clock event devices and the assignment of timer interrupt related functionality
142 high resolution timer functionality
146 functionality, while making it possible would be difficult and would serve no
150 the high resolution functionality can work. Up to the point where hrtimers are
190 The periodic tick functionality is provided by an per-cpu hrtimer. The callback
[all …]
|
| /kernel/linux/linux-4.19/Documentation/timers/ |
| D | highres.txt | 25 - high resolution timer functionality
53 related functionality is moved into the generic code. The GTOD base patch got
79 functionality like high resolution timers or dynamic ticks.
87 architectures as it provides generic functionality down to the interrupt
98 event devices are used to provide local CPU functionality such as process
113 clock event devices and the assignment of timer interrupt related functionality
138 high resolution timer functionality
142 functionality, while making it possible would be difficult and would serve no
146 the high resolution functionality can work. Up to the point where hrtimers are
186 The periodic tick functionality is provided by an per-cpu hrtimer. The callback
[all …]
|
| /kernel/linux/linux-5.10/drivers/usb/dwc3/ |
| D | Kconfig | 64 AM437x use this IP for USB2/3 functionality.
97 Support of USB2/3 functionality in TI Keystone2 and AM654 platforms.
108 Support USB2/3 functionality in Amlogic G12A platforms.
116 Support USB2/3 functionality in simple SoC integrations.
137 functionality.
|
| /kernel/linux/linux-4.19/Documentation/hwmon/ |
| D | pmbus-core | 29 simply unknown what new device specific functionality PMBus device developers
35 pmbus_core.c) provides generic functionality. The generic code (in pmbus.c)
38 functionality into generic functionality. This is to some degree comparable
53 used to inform the core driver about functionality supported by individual
78 functionality which has been implemented by several chip vendors and is thus
115 - Supported chip functionality can be provided to the core driver. This may be
119 augmenting generic command execution. This functionality can be used to map
175 Determine supported PMBus functionality. This function is only necessary
176 if a chip driver supports multiple chips, and the chip functionality is not
|
| /kernel/linux/linux-5.10/Documentation/hwmon/ |
| D | pmbus-core.rst | 30 simply unknown what new device specific functionality PMBus device developers
36 pmbus_core.c) provides generic functionality. The generic code (in pmbus.c)
39 functionality into generic functionality. This is to some degree comparable
54 used to inform the core driver about functionality supported by individual
79 functionality which has been implemented by several chip vendors and is thus
116 - Supported chip functionality can be provided to the core driver. This may be
120 augmenting generic command execution. This functionality can be used to map
190 Determine supported PMBus functionality. This function is only necessary
191 if a chip driver supports multiple chips, and the chip functionality is not
|
| /kernel/linux/linux-4.19/drivers/i2c/busses/ |
| D | i2c-designware-pcidrv.c | 52 u32 functionality; member
133 .functionality = I2C_FUNC_10BIT_ADDR,
142 .functionality = I2C_FUNC_10BIT_ADDR,
151 .functionality = I2C_FUNC_10BIT_ADDR,
159 .functionality = I2C_FUNC_10BIT_ADDR,
167 .functionality = I2C_FUNC_10BIT_ADDR,
249 dev->functionality = controller->functionality | in i2c_dw_pci_probe()
|
| /kernel/linux/linux-4.19/drivers/usb/dwc3/ |
| D | Kconfig | 61 AM437x use this IP for USB2/3 functionality.
94 Support of USB2/3 functionality in TI Keystone2 platforms.
102 Support USB2/3 functionality in simple SoC integrations.
123 functionality.
|
| /kernel/linux/linux-4.19/drivers/hwspinlock/ |
| D | Kconfig | 25 Say y here to support the Qualcomm Hardware Mutex functionality, which
53 tristate "STE Hardware Semaphore functionality"
57 Say y here to support the STE Hardware Semaphore functionality, which
|
| /kernel/linux/linux-5.10/drivers/hwspinlock/ |
| D | Kconfig | 25 Say y here to support the Qualcomm Hardware Mutex functionality, which
59 tristate "STE Hardware Semaphore functionality"
62 Say y here to support the STE Hardware Semaphore functionality, which
|
| /kernel/linux/linux-4.19/drivers/staging/iio/Documentation/ |
| D | ring.txt | 3 This document is intended as a general overview of the functionality
23 as much buffer functionality as possible. Note almost all of these
31 This provides polling like functionality whilst the ring buffering is in
|
| /kernel/linux/linux-4.19/Documentation/ |
| D | rtc.txt | 25 Programmers need to understand that the PC/AT functionality is not
29 same functionality. For example, not every RTC is hooked up to an
43 ACPI has standardized that MC146818 functionality, and extended it in
45 That functionality is NOT exposed in the old driver.
135 a high functionality RTC is integrated into the SOC. That system might read
137 other tasks, because of its greater functionality.
|
| /kernel/linux/linux-5.10/Documentation/admin-guide/ |
| D | rtc.rst | 25 Programmers need to understand that the PC/AT functionality is not
29 same functionality. For example, not every RTC is hooked up to an
43 ACPI has standardized that MC146818 functionality, and extended it in
45 That functionality is NOT exposed in the old driver.
135 a high functionality RTC is integrated into the SOC. That system might read
137 other tasks, because of its greater functionality.
|