Home
last modified time | relevance | path

Searched full:functionality (Results 1 – 25 of 1494) sorted by relevance

12345678910>>...60

/Linux-v5.4/Documentation/arm64/
Delf_hwcaps.rst51 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 …]
/Linux-v5.4/Documentation/i2c/
Dsmbus-protocol.rst27 Each transaction type corresponds to a functionality flag. Before calling a
29 the corresponding functionality flag to ensure that the underlying I2C
31 <file:Documentation/i2c/functionality.rst> for the details.
62 Functionality flag: I2C_FUNC_SMBUS_QUICK
75 Functionality flag: I2C_FUNC_SMBUS_READ_BYTE
88 Functionality flag: I2C_FUNC_SMBUS_WRITE_BYTE
99 Functionality flag: I2C_FUNC_SMBUS_READ_BYTE_DATA
111 Functionality flag: I2C_FUNC_SMBUS_READ_WORD_DATA
129 Functionality flag: I2C_FUNC_SMBUS_WRITE_BYTE_DATA
141 Functionality flag: I2C_FUNC_SMBUS_WRITE_WORD_DATA
[all …]
Dfunctionality.rst2 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
Di2c-stub.rst26 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-v5.4/drivers/mfd/
DKconfig20 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/devicetree/bindings/mfd/
Dtwl4030-audio.txt11 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-v5.4/drivers/staging/greybus/
Di2c.c21 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()
236 return gb_i2c_dev->functionality; in gb_i2c_functionality()
242 .functionality = gb_i2c_functionality,
/Linux-v5.4/Documentation/timers/
Dhighres.rst26 - 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/dwc3/
DKconfig63 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/Documentation/hwmon/
Dpmbus-core.rst30 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/i2c/busses/
Di2c-designware-pcidrv.c53 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/hwspinlock/
DKconfig25 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/staging/iio/Documentation/
Dring.txt3 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/admin-guide/
Drtc.rst25 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/include/uapi/linux/
Dhyperv.h151 * 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
/Linux-v5.4/drivers/pinctrl/
DKconfig52 functionality. This driver supports the pinmux, push-pull and
54 supports the GPIO functionality through gpiolib.
104 driver for memory mapped GPIO functionality on AMD platforms
106 functionality by firmware,so only a small amount is available
325 functionality. This driver supports the pinmux, push-pull and
/Linux-v5.4/drivers/i2c/
Di2c-stub.c26 * 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,
/Linux-v5.4/drivers/usb/chipidea/
DKconfig35 Say Y here to enable device controller functionality of the
43 Say Y here to enable host controller functionality of the
/Linux-v5.4/drivers/hwmon/pmbus/
Dpmbus.h210 * Drivers wanting to expose functionality for changing the number of
352 /* Functionality bit mask */
394 u32 func[PMBUS_PAGES]; /* Functionality, per page */
412 * The identify function determines supported PMBus functionality.
414 * chips, and the chip functionality is not pre-determined.
419 /* Regulator functionality, if supported by this chip driver. */
/Linux-v5.4/Documentation/ABI/testing/
Dsysfs-block165 Devices that support discard functionality may
176 Devices that support discard functionality may
187 Devices that support discard functionality may
194 that the device does not support discard functionality.
200 Devices that support discard functionality may have
210 discard functionality.
Dsysfs-bus-pci-drivers-xhci_hcd18 functionality and the shared root port will be assigned
20 will disable the DbC functionality and the shared root
/Linux-v5.4/Documentation/accounting/
Ddelay-accounting.rst9 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
/Linux-v5.4/drivers/clk/qcom/
DKconfig235 Say Y if you want to support camera devices and camera functionality.
265 functionality such as 3D graphics.
273 Say Y if you want to support video devices and functionality such as
282 Say Y if you want to support display devices and functionality such as
304 This driver supports the clkdiv functionality on the Qualcomm
/Linux-v5.4/Documentation/infiniband/
Dopa_vnic.rst6 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/usb/cdns3/
DKconfig19 Say Y here to enable device controller functionality of the
29 Say Y here to enable host controller functionality of the

12345678910>>...60