| /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-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-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
|
| D | i2c-stub.rst | 26 explicitly by setting the respective bits (0x03000000) in the functionality
49 unsigned long functionality:
50 Functionality override, to disable some commands. See I2C_FUNC_*
|
| /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-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-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-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-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-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.
|
| /kernel/linux/linux-5.10/Documentation/admin-guide/media/ |
| D | avermedia.rst | 43 functionality of the remaining device nodes in respect of the
44 Avermedia DVBT. However, full functionality in respect of
47 It may be possible that additional functionality is available
75 functionality of any other part of the card yet. I will do so
|
| D | building.rst | 116 Other core functionality may also be needed (like PCI and/or USB support),
135 The ``LIRC user interface`` option adds enhanced functionality when using the
141 to add extra remote controller decoding functionality to the Linux Kernel.
238 functionality.
248 functionality are usually good enough to provide the basic functionality
250 functionality using the settings under each of the following
270 ``Media Core Support`` menu has all the core functionality your drivers
|
| /kernel/linux/linux-5.10/include/uapi/linux/ |
| D | hyperv.h | 151 * An implementation of HyperV key value pair (KVP) functionality for Linux.
165 * for the IC KVP exchange functionality. Note that Windows Me/98/95 are
189 * In Linux, we implement the KVP functionality in two components:
217 * data gathering functionality in a user mode daemon. The user level daemon
246 * As we look at expanding the KVP functionality to include
247 * IP injection functionality, we need to maintain binary
|
| /kernel/linux/linux-5.10/drivers/i2c/ |
| D | i2c-stub.c | 26 * in the 'functionality' module parameter.
41 static unsigned long functionality = STUB_FUNC_DEFAULT; variable
42 module_param(functionality, ulong, S_IRUGO | S_IWUSR);
43 MODULE_PARM_DESC(functionality, "Override functionality bitfield");
302 return STUB_FUNC_ALL & functionality; in stub_func()
306 .functionality = stub_func,
|
| /kernel/linux/linux-5.10/drivers/hwmon/pmbus/ |
| D | pmbus.h | 228 * Drivers wanting to expose functionality for changing the number of
380 /* Functionality bit mask */
424 u32 func[PMBUS_PAGES]; /* Functionality, per page */
425 u32 pfunc[PMBUS_PHASES];/* Functionality, per phase */
444 * The identify function determines supported PMBus functionality.
446 * chips, and the chip functionality is not pre-determined.
451 /* Regulator functionality, if supported by this chip driver. */
|
| /kernel/linux/linux-5.10/drivers/pinctrl/ |
| D | Kconfig | 52 functionality. This driver supports the pinmux, push-pull and
54 supports the GPIO functionality through gpiolib.
105 driver for memory mapped GPIO functionality on AMD platforms
107 functionality by firmware,so only a small amount is available
315 functionality. This driver supports the pinmux, push-pull and
|
| /kernel/linux/linux-5.10/Documentation/accounting/ |
| D | delay-accounting.rst | 9 The per-task delay accounting functionality measures
24 The functionality, through its use of the taskstats interface, also provides
41 statistics. The delay accounting functionality populates specific fields of
|
| /kernel/linux/linux-5.10/Documentation/ABI/testing/ |
| D | sysfs-bus-pci-drivers-xhci_hcd | 18 functionality and the shared root port will be assigned
20 will disable the DbC functionality and the shared root
|
| /kernel/linux/linux-5.10/drivers/usb/chipidea/ |
| D | Kconfig | 25 Say Y here to enable device controller functionality of the
33 Say Y here to enable host controller functionality of the
|
| /kernel/linux/linux-5.10/Documentation/infiniband/ |
| D | opa_vnic.rst | 6 supports Ethernet functionality over Omni-Path fabric by encapsulating
104 OPA VNIC functionality has a HW dependent component and a HW
112 The HW dependent VNIC functionality is part of the HFI1 driver. It
114 It involves HW resource allocation/management for VNIC functionality.
121 The OPA VNIC module implements the HW independent VNIC functionality.
|
| /kernel/linux/linux-5.10/drivers/mtd/ |
| D | Makefile | 6 # Core functionality.
12 # 'Users' - code which presents functionality to userspace.
|
| /kernel/linux/linux-5.10/drivers/media/usb/stk1160/ |
| D | stk1160-i2c.c | 221 * functionality(), what da heck is this?
223 static u32 functionality(struct i2c_adapter *adap) in functionality() function
230 .functionality = functionality,
|