| /openbmc/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 …]
|
| /openbmc/linux/drivers/clk/qcom/ |
| H A D | Kconfig | 375 functionality such as 3D graphics.
400 Say Y if you want to support display devices and functionality such as
417 Say Y if you want to support camera devices and functionality such as
427 Say Y if you want to support camera devices and functionality such as
437 Say Y if you want to support display devices and functionality such as
447 Say Y if you want to support display devices and functionality such as
457 Say Y if you want to support display devices and functionality such as
476 functionality such as 3D graphics.
525 functionality such as 3D graphics.
534 functionality such as 3D graphics.
[all …]
|
| /openbmc/linux/drivers/mfd/ |
| H A D | Kconfig | 21 necessary for using the board's GPIO and MFGPT functionality.
124 functionality of the device.
156 functionality of the device.
282 core functionality controlled via I2C.
291 core functionality controlled via SPI.
363 order to use the functionality of the device.
375 order to use the functionality of the device.
387 Additional drivers must be enabled in order to use the functionality
400 Additional drivers must be enabled in order to use the functionality
412 Additional drivers must be enabled in order to use the functionality
[all …]
|
| /openbmc/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_*
|
| /openbmc/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.
|
| /openbmc/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,
|
| /openbmc/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 …]
|
| /openbmc/phosphor-power/tools/i2c/ |
| H A D | i2c.hpp | 39 /** @brief Empty adapter functionality value with no bit flags set */
54 /** @brief Cached I2C adapter functionality value */
80 /** @brief Get I2C adapter functionality in closeWithoutException()
82 * Caches the adapter functionality value since it shouldn't change after
86 * @return Adapter functionality value
90 /** @brief Check i2c adapter read functionality
92 * Check if the i2c adapter has the functionality specified by the SMBus
101 /** @brief Check i2c adapter write functionality
103 * Check if the i2c adapter has the functionality specified by the SMBus
|
| /openbmc/u-boot/board/bosch/shc/ |
| H A D | Kconfig | 24 enable here the eMMC functionality on the bosch shc board.
29 enable here the ICT functionality on the bosch shc board
34 enable here the NETBOOT functionality on the bosch shc board
39 enable here the SDBOOT functionality on the bosch shc board
|
| /openbmc/u-boot/drivers/fpga/ |
| H A D | Kconfig | 22 This provides common functionality for Gen5 and Arria10 devices.
30 This provides common functionality for Altera Cyclone II devices.
41 This provides common functionality for Altera Stratix 10 devices.
77 This provides functionality and hardware configurations
|
| /openbmc/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.
|
| /openbmc/linux/Documentation/userspace-api/media/drivers/ |
| H A D | ccs.rst | 20 as analogue crop functionality present in many compliant devices. The analogue
28 The binner sub-device represents the binning functionality on the sensor. For
32 Additionally, if a device has no scaler or digital crop functionality, the
39 The scaler sub-device represents the digital crop and scaling functionality of
52 Digital crop functionality is referred to as cropping that effectively works by
|
| /openbmc/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
|
| /openbmc/openbmc/poky/meta/recipes-graphics/wayland/ |
| H A D | wayland-protocols_1.38.bb | 2 DESCRIPTION = "Wayland protocols that add functionality not \
4 completely new functionality, or extend the functionality of some other \
|
| /openbmc/webui-vue/docs/guide/unit-testing/ |
| H A D | readme.md | 4 or refactoring does not result in broken builds and functionality. Tests that
68 - Avoid coupling test code to source code when testing functionality
71 - A test should not break if the functionality it tests has not changed
93 1. Don't test third-party functionality
97 1. Don't test the functionality of other libraries
181 that functionality, which requires stubbing
|
| /openbmc/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
|
| /openbmc/linux/Documentation/driver-api/media/drivers/ccs/ |
| H A D | ccs.rst | 20 as analogue crop functionality present in many compliant devices. The analogue
28 The binner sub-device represents the binning functionality on the sensor. For
32 Additionally, if a device has no scaler or digital crop functionality, the
39 The scaler sub-device represents the digital crop and scaling functionality of
52 Digital crop functionality is referred to as cropping that effectively works by
|
| /openbmc/linux/Documentation/hwmon/ |
| H A 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
199 Determine supported PMBus functionality. This function is only necessary
200 if a chip driver supports multiple chips, and the chip functionality is not
|
| /openbmc/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
|
| /openbmc/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.
|
| /openbmc/u-boot/drivers/tpm/ |
| H A D | Kconfig | 24 support Chrome OS verified boot. Extend functionality is not
101 The functionality is available via the 'tpm' command as well.
109 The functionality is available via the 'tpm' command as well.
116 The functionality is available via the 'tpm' command as well.
|
| /openbmc/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
|
| H A 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
|