| /kernel/linux/linux-6.6/Documentation/arch/arm64/ |
| D | elf_hwcaps.rst | 53 Functionality implied by idreg.field == val.
55 Such hwcaps indicate the availability of functionality that the ARM ARM
58 indicate the absence of functionality implied by other values of
70 Functionality implied by ID_AA64PFR0_EL1.FP == 0b0000.
73 Functionality implied by ID_AA64PFR0_EL1.AdvSIMD == 0b0000.
80 Functionality implied by ID_AA64ISAR0_EL1.AES == 0b0001.
83 Functionality implied by ID_AA64ISAR0_EL1.AES == 0b0010.
86 Functionality implied by ID_AA64ISAR0_EL1.SHA1 == 0b0001.
89 Functionality implied by ID_AA64ISAR0_EL1.SHA2 == 0b0001.
92 Functionality implied by ID_AA64ISAR0_EL1.CRC32 == 0b0001.
[all …]
|
| /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-6.6/drivers/clk/qcom/ |
| D | Kconfig | 375 functionality such as 3D graphics.
400 Say Y if you want to support display devices and functionality such as
417 Say Y if you want to support camera devices and functionality such as
427 Say Y if you want to support camera devices and functionality such as
437 Say Y if you want to support display devices and functionality such as
447 Say Y if you want to support display devices and functionality such as
457 Say Y if you want to support display devices and functionality such as
476 functionality such as 3D graphics.
525 functionality such as 3D graphics.
534 functionality such as 3D graphics.
[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-6.6/drivers/mfd/ |
| D | Kconfig | 21 necessary for using the board's GPIO and MFGPT functionality.
124 functionality of the device.
156 functionality of the device.
282 core functionality controlled via I2C.
291 core functionality controlled via SPI.
363 order to use the functionality of the device.
375 order to use the functionality of the device.
387 Additional drivers must be enabled in order to use the functionality
400 Additional drivers must be enabled in order to use the functionality
412 Additional drivers must be enabled in order to use the functionality
[all …]
|
| /kernel/linux/linux-6.6/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
31 Documentation/i2c/functionality.rst for the details.
64 Functionality flag: I2C_FUNC_SMBUS_QUICK
79 Functionality flag: I2C_FUNC_SMBUS_READ_BYTE
94 Functionality flag: I2C_FUNC_SMBUS_WRITE_BYTE
107 Functionality flag: I2C_FUNC_SMBUS_READ_BYTE_DATA
121 Functionality flag: I2C_FUNC_SMBUS_READ_WORD_DATA
141 Functionality flag: I2C_FUNC_SMBUS_WRITE_BYTE_DATA
155 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-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-6.6/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-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-6.6/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/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 | 276 functionality such as 3D graphics.
300 Say Y if you want to support display devices and functionality such as
327 functionality such as 3D graphics.
343 Say Y if you want to support video devices and functionality such as
351 Say Y if you want to support camera devices and camera functionality.
389 functionality such as 3D graphics.
397 Say Y if you want to support video devices and functionality such as
406 Say Y if you want to support display devices and functionality such as
423 Say Y if you want to support display devices and functionality such as
447 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-6.6/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-6.6/drivers/usb/dwc3/ |
| D | Kconfig | 64 AM437x use this IP for USB2/3 functionality.
98 Support of USB2/3 functionality in TI Keystone2 and AM654 platforms.
109 Support USB2/3 functionality in Amlogic G12A platforms.
117 Support USB2/3 functionality in simple SoC integrations.
138 functionality.
150 functionality.
|
| /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-6.6/Documentation/userspace-api/media/drivers/ |
| D | ccs.rst | 20 as analogue crop functionality present in many compliant devices. The analogue
28 The binner sub-device represents the binning functionality on the sensor. For
32 Additionally, if a device has no scaler or digital crop functionality, the
39 The scaler sub-device represents the digital crop and scaling functionality of
52 Digital crop functionality is referred to as cropping that effectively works by
|
| /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-6.6/drivers/platform/surface/aggregator/ |
| D | Kconfig | 16 functionality, including:
27 basic kernel interface exposing the EC functionality to other client
30 client drivers and therefore no functionality beyond the in-kernel
31 interface. Said functionality is the responsibility of the respective
|
| /kernel/linux/linux-6.6/drivers/usb/cdns3/ |
| D | Kconfig | 33 Say Y here to enable device controller functionality of the
44 Say Y here to enable host controller functionality of the
113 Say Y here to enable device controller functionality of the
127 Say Y here to enable host controller functionality of the
|
| /kernel/linux/linux-6.6/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
199 Determine supported PMBus functionality. This function is only necessary
200 if a chip driver supports multiple chips, and the chip functionality is not
|
| /kernel/linux/linux-6.6/Documentation/driver-api/media/drivers/ccs/ |
| D | ccs.rst | 20 as analogue crop functionality present in many compliant devices. The analogue
28 The binner sub-device represents the binning functionality on the sensor. For
32 Additionally, if a device has no scaler or digital crop functionality, the
39 The scaler sub-device represents the digital crop and scaling functionality of
52 Digital crop functionality is referred to as cropping that effectively works by
|
| /kernel/linux/linux-6.6/drivers/hwspinlock/ |
| D | Kconfig | 25 Say y here to support the Qualcomm Hardware Mutex functionality, which
57 tristate "STE Hardware Semaphore functionality"
60 Say y here to support the STE Hardware Semaphore functionality, which
|