| /linux/drivers/clk/qcom/ |
| H A D | Kconfig | 29 Say Y if you want to support display devices and functionality such as
59 Say Y if you want to support camera devices and functionality such as
70 Say Y if you want to support display devices and functionality such as
82 Say Y if you want to support EVA devices and functionality such as
102 functionality such as 3D graphics.
120 Say Y if you want to support video devices and functionality such as
131 Say Y if you want to support camera devices and functionality such as
142 Say Y if you want to support display devices and functionality such as
163 functionality such as 3D graphics.
181 Say Y if you want to support video devices and functionality such as
[all …]
|
| /linux/Documentation/ABI/testing/ |
| H A D | sysfs-driver-uniwill-laptop | 9 Reading this file returns the current enable status of the FN lock functionality.
26 Allows userspace applications to enable/disable the touchpad toggle functionality
30 functionality.
39 functionality.
41 Reading this file returns the current status of the rainbow animation functionality.
50 enables/disables this functionality.
53 functionality.
89 enables/disables this functionality. Enabling both AC auto boot and USB powershare
92 Reading this file returns the current status of the AC auto boot functionality.
102 file enables/disables this functionality. Enabling both USB powershare and AC auto
[all …]
|
| /linux/drivers/mfd/ |
| H A D | Kconfig | 21 necessary for using the board's GPIO and MFGPT functionality.
138 functionality of the device.
170 functionality of the device.
364 core functionality controlled via I2C.
373 core functionality controlled via SPI.
446 order to use the functionality of the device.
458 order to use the functionality of the device.
470 Additional drivers must be enabled in order to use the functionality
483 Additional drivers must be enabled in order to use the functionality
495 Additional drivers must be enabled in order to use the functionality
[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/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/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/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/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/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");
306 return STUB_FUNC_ALL & functionality; in stub_func()
310 .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/Documentation/userspace-api/ |
| H A D | rseq.rst | 114 functionality without disturbing each other. The ABI compliant optimized v2
125 The prerequisites for this functionality are:
134 The thread has to enable the functionality via prctl(2)::
144 EINVAL Functionality not available or invalid function arguments.
146 ENOTSUPP Functionality was disabled on the kernel command line
160 EINVAL Functionality not available or invalid function arguments.
|
| /linux/fs/btrfs/ |
| H A D | Kconfig | 53 This will run sanity tests for core functionality like free space,
67 Additional potentially expensive checks, debugging functionality or
92 to test the functionality and report problems.
|
| /linux/drivers/pinctrl/ |
| H A D | Kconfig | 50 The driver for memory mapped GPIO functionality on AMD platforms
52 functionality by firmware, so only a small amount is available
66 The driver for memory mapped GPIO functionality on AMD platforms
105 functionality. This driver supports the pinmux, push-pull and
107 supports the GPIO functionality through gpiolib.
158 expander with PWM functionality. This driver bundles a
466 functionality. This driver supports the pinmux, push-pull and
|
| /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
|
| /linux/drivers/media/usb/stk1160/ |
| H A 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,
|
| /linux/drivers/hwmon/pmbus/ |
| H A D | pmbus.h | 229 * Drivers wanting to expose functionality for changing the number of
392 /* Functionality bit mask */
448 u32 func[PMBUS_PAGES]; /* Functionality, per page */
449 u32 pfunc[PMBUS_PHASES];/* Functionality, per phase */
470 * The identify function determines supported PMBus functionality.
472 * chips, and the chip functionality is not pre-determined.
477 /* Regulator functionality, if supported by this chip driver. */
|
| /linux/drivers/usb/chipidea/ |
| H A D | Kconfig | 25 Say Y here to enable device controller functionality of the
33 Say Y here to enable host controller functionality of the
|
| /linux/drivers/platform/x86/amd/hsmp/ |
| H A D | Kconfig | 21 system management functionality on EPYC and MI300A server CPUs
39 system management functionality on EPYC and MI300A server CPUs
|
| /linux/Documentation/devicetree/bindings/mfd/ |
| H A D | as3722.txt | 38 Following are properties which is needed if GPIO and pinmux functionality
82 functionality is needed.
129 functionality
130 ams,system-power-controller: Boolean, to enable the power off functionality
|