| /linux/Documentation/arch/arm64/ |
| H A 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 …]
|
| /linux/drivers/clk/qcom/ |
| H A D | Kconfig | 28 Say Y if you want to support camera devices and camera functionality.
37 Say Y if you want to support display devices and functionality such as
57 functionality such as 3D graphics.
74 functionality such as 3D graphics.
443 functionality such as 3D graphics.
468 Say Y if you want to support display devices and functionality such as
485 Say Y if you want to support camera devices and functionality such as
505 Say Y if you want to support camera devices and functionality such as
515 Say Y if you want to support camera devices and functionality such as
525 Say Y if you want to support camera devices and functionality such as
[all …]
|
| /linux/Documentation/i2c/ |
| H A 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 …]
|
| H A 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
|
| H A 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_*
|
| /linux/drivers/mfd/ |
| H A D | Kconfig | 21 necessary for using the board's GPIO and MFGPT functionality.
136 functionality of the device.
168 functionality of the device.
306 core functionality controlled via I2C.
315 core functionality controlled via SPI.
387 order to use the functionality of the device.
399 order to use the functionality of the device.
411 Additional drivers must be enabled in order to use the functionality
424 Additional drivers must be enabled in order to use the functionality
436 Additional drivers must be enabled in order to use the functionality
[all …]
|
| /linux/drivers/staging/greybus/ |
| H A 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,
|
| /linux/Documentation/devicetree/bindings/mfd/ |
| H A 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.
|
| /linux/Documentation/timers/ |
| H A 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 …]
|
| /linux/drivers/usb/dwc3/ |
| H A 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.
|
| /linux/Documentation/userspace-api/media/drivers/ |
| H A D | ccs.rst | 24 as analogue crop functionality present in many compliant devices. The analogue
32 The binner sub-device represents the binning functionality on the sensor. For
36 Additionally, if a device has no scaler or digital crop functionality, the
43 The scaler sub-device represents the digital crop and scaling functionality of
56 Digital crop functionality is referred to as cropping that effectively works by
|
| /linux/drivers/platform/surface/aggregator/ |
| H A 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
|
| /linux/drivers/usb/cdns3/ |
| H A 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
|
| /linux/Documentation/admin-guide/ |
| H A 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.
|
| /linux/drivers/hwspinlock/ |
| H A 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
|
| /linux/Documentation/admin-guide/media/ |
| H A 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
|
| /linux/Documentation/sound/cards/ |
| H A D | pcmtest.rst | 25 layer data transferring functionality. Additionally, this driver redefines the default
26 RESET ioctl, and the selftest covers this PCM API functionality as well.
103 This driver can be also used for the playback functionality testing - every time you
113 this functionality, we can trigger the reset ioctl and check the 'ioctl_test' debugfs
|
| /linux/drivers/i2c/ |
| H A D | i2c-stub.c | 25 * in the 'functionality' module parameter.
40 static unsigned long functionality = STUB_FUNC_DEFAULT; variable
41 module_param(functionality, ulong, S_IRUGO | S_IWUSR);
42 MODULE_PARM_DESC(functionality, "Override functionality bitfield");
301 return STUB_FUNC_ALL & functionality; in stub_func()
305 .functionality = stub_func,
|
| /linux/include/uapi/linux/ |
| H A D | hyperv.h | 162 * An implementation of HyperV key value pair (KVP) functionality for Linux.
176 * for the IC KVP exchange functionality. Note that Windows Me/98/95 are
200 * In Linux, we implement the KVP functionality in two components:
228 * data gathering functionality in a user mode daemon. The user level daemon
257 * As we look at expanding the KVP functionality to include
258 * IP injection functionality, we need to maintain binary
|
| /linux/drivers/hwmon/pmbus/ |
| H A D | pmbus.h | 228 * Drivers wanting to expose functionality for changing the number of
390 /* Functionality bit mask */
440 u32 func[PMBUS_PAGES]; /* Functionality, per page */
441 u32 pfunc[PMBUS_PHASES];/* Functionality, per phase */
462 * The identify function determines supported PMBus functionality.
464 * chips, and the chip functionality is not pre-determined.
469 /* Regulator functionality, if supported by this chip driver. */
|
| /linux/Documentation/infiniband/ |
| H A 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.
|
| /linux/drivers/gpio/ |
| H A D | Kconfig | 140 Say yes here to support GPIO functionality for 74xx-compatible ICs
162 Driver for GPIO functionality on Promontory IOHub.
178 Say Y here to support Aspeed AST2500 SGPIO functionality.
298 Support for common GPIO functionality provided on some GE Single Board
331 The driver enables basic GPIO functionality and implements interrupt
373 Say yes here to support the GPIO functionality of a number of Intel
392 Say yes here to support the GPIO functionality of a number of Intel
401 Say yes here to support GPIO functionality of the Xylon LogiCVC
408 Driver for GPIO functionality on Loongson-2F/3A/3B processors.
416 Say yes here to support the GPIO functionality of a number of
[all …]
|
| /linux/Documentation/process/ |
| H A D | adding-syscalls.rst | 23 also makes it easier to encapsulate the new functionality in a kernel module
26 - If the new functionality involves operations where the kernel notifies
45 existing :manpage:`fcntl(2)` functionality, or the new functionality is very simple
139 in particular it allows userspace to request the functionality for an
154 If your new :manpage:`xyzzy(2)` system call involves privileged functionality,
157 page. Choose an existing capability bit that governs related functionality,
230 Your new kernel functionality, and the system call that controls it, should
234 - Include a description of the new functionality and system call controlled
474 For more extensive and thorough testing of new functionality, you should also
500 table, but not from elsewhere in the kernel. If the syscall functionality is
|
| /linux/Documentation/networking/ |
| H A D | sriov.rst | 9 functionality.
19 the API is considered frozen; no new functionality or extensions
|
| /linux/drivers/virt/nitro_enclaves/ |
| H A D | Kconfig | 19 bool "Tests for the misc device functionality of the Nitro Enclaves" if !KUNIT_ALL_TESTS
23 Enable KUnit tests for the misc device functionality of the Nitro
|