| /Linux-v5.4/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.
|
| D | twl6040.txt | 4 vibra and GPO functionality on OMAP4+ platforms.
25 Vibra functionality
|
| /Linux-v5.4/drivers/i2c/busses/ |
| D | i2c-designware-pcidrv.c | 53 u32 functionality; member
134 .functionality = I2C_FUNC_10BIT_ADDR,
143 .functionality = I2C_FUNC_10BIT_ADDR,
152 .functionality = I2C_FUNC_10BIT_ADDR,
160 .functionality = I2C_FUNC_10BIT_ADDR,
168 .functionality = I2C_FUNC_10BIT_ADDR,
177 .functionality = I2C_FUNC_10BIT_ADDR,
269 dev->functionality = controller->functionality | in i2c_dw_pci_probe()
|
| /Linux-v5.4/drivers/staging/greybus/ |
| D | i2c.c | 21 u32 functionality; member
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()
236 return gb_i2c_dev->functionality; in gb_i2c_functionality()
242 .functionality = gb_i2c_functionality,
|
| /Linux-v5.4/Documentation/i2c/ |
| D | functionality.rst | 12 functionality.
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
|
| /Linux-v5.4/drivers/hwspinlock/ |
| D | Kconfig | 25 Say y here to support the Qualcomm Hardware Mutex functionality, which
62 tristate "STE Hardware Semaphore functionality"
66 Say y here to support the STE Hardware Semaphore functionality, which
|
| /Linux-v5.4/drivers/usb/dwc3/ |
| D | Kconfig | 63 AM437x use this IP for USB2/3 functionality.
96 Support of USB2/3 functionality in TI Keystone2 and AM654 platforms.
107 Support USB2/3 functionality in Amlogic G12A platforms.
115 Support USB2/3 functionality in simple SoC integrations.
136 functionality.
|
| /Linux-v5.4/drivers/i2c/ |
| D | i2c-stub.c | 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,
|
| /Linux-v5.4/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
|
| /Linux-v5.4/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 …]
|
| /Linux-v5.4/drivers/usb/chipidea/ |
| D | Kconfig | 35 Say Y here to enable device controller functionality of the
43 Say Y here to enable host controller functionality of the
|
| /Linux-v5.4/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.
|
| /Linux-v5.4/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.
324 order to use the functionality of the device.
336 order to use the functionality of the device.
348 Additional drivers must be enabled in order to use the functionality
364 Additional drivers must be enabled in order to use the functionality
376 Additional drivers must be enabled in order to use the functionality
[all …]
|
| /Linux-v5.4/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
|
| D | sysfs-firmware-gsmi | 6 that provides callback functionality via explicit SMI
13 these firmware callbacks. Currently, this functionality
|
| /Linux-v5.4/drivers/media/usb/stk1160/ |
| D | stk1160-i2c.c | 223 static u32 functionality(struct i2c_adapter *adap) in functionality() function
230 .functionality = functionality,
|
| /Linux-v5.4/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
187 Determine supported PMBus functionality. This function is only necessary
188 if a chip driver supports multiple chips, and the chip functionality is not
|
| /Linux-v5.4/drivers/usb/cdns3/ |
| D | Kconfig | 19 Say Y here to enable device controller functionality of the
29 Say Y here to enable host controller functionality of the
|
| /Linux-v5.4/drivers/media/usb/tm6000/ |
| D | tm6000-i2c.c | 272 static u32 functionality(struct i2c_adapter *adap) in functionality() function
279 .functionality = functionality,
|
| /Linux-v5.4/drivers/media/v4l2-core/ |
| D | Kconfig | 20 bool "Enable advanced debug functionality on V4L2 drivers"
22 Say Y here to enable advanced debugging functionality on some
|
| /Linux-v5.4/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.
|
| /Linux-v5.4/Documentation/cpu-freq/ |
| D | amd-powernow.txt | 11 Note that the functionality to change frequency (and voltage)
26 Documentation on this functionality in 8th generation processors
|
| /Linux-v5.4/Documentation/devicetree/bindings/sifive/ |
| D | sifive-blocks-ip-versioning.txt | 19 interface to these IP blocks changes, or when the functionality of the
24 register interface and functionality associated with the relevant
|
| /Linux-v5.4/drivers/usb/gadget/udc/aspeed-vhub/ |
| D | Kconfig | 8 SoCs supporting the "vHub" functionality and USB2.0
|
| /Linux-v5.4/Documentation/devicetree/bindings/power/reset/ |
| D | st-reset.txt | 1 *Device-Tree bindings for ST SW reset functionality
|
