Searched full:counterparts (Results 1 – 25 of 93) sorted by relevance
1234
| /openbmc/u-boot/include/linux/ |
| H A D | dma-direction.h | 5 * interchangeably with their PCI_ counterparts.
|
| /openbmc/linux/arch/arm64/boot/dts/qcom/ |
| H A D | sa8155p.dtsi | 36 * SM8150 counterparts to make it more maintainable and only
|
| /openbmc/linux/Documentation/devicetree/bindings/regulator/ |
| H A D | mps,mpq7932.yaml | 24 after their hardware counterparts BUCK[1-6]
|
| H A D | maxim,max77826.yaml | 27 after their hardware counterparts LDO[1-15], BUCK and BUCKBOOST
|
| H A D | tps65023.txt | 10 after their hardware counterparts: VDCDC[1-3] and LDO[1-2]
|
| H A D | mps,mp5416.yaml | 27 after their hardware counterparts BUCK[1-4] and LDO[1-4]
|
| H A D | onnn,fan53880.yaml | 45 after their hardware counterparts LDO[1-4], BUCK and BOOST
|
| H A D | tps65217.txt | 7 after their hardware counterparts: dcdc[1-3] and ldo[1-4]
|
| H A D | tps65218.txt | 8 after their hardware counterparts: dcdc[1-6] and ldo1
|
| H A D | mt6360-regulator.yaml | 14 after their hardware counterparts buck1/2 or ldo1/2/3/5/6/7
|
| H A D | mps,mpq7920.yaml | 27 after their hardware counterparts BUCK[1-4], one LDORTC, and LDO[2-5]
|
| /openbmc/linux/Documentation/devicetree/bindings/mfd/ |
| H A D | tps65912.txt | 18 after their hardware counterparts: dcdc[1-4] and
|
| H A D | rohm,bd9571mwv.yaml | 65 Child nodes must be named after their hardware counterparts.
|
| H A D | ti,tps65086.yaml | 44 Child nodes must be named after their hardware counterparts:
|
| /openbmc/u-boot/arch/arm/thumb1/include/asm/proc-armv/ |
| H A D | system.h | 25 * ordering constraints as their original counterparts.
|
| /openbmc/linux/Documentation/arch/x86/ |
| H A D | usb-legacy-support.rst | 13 their classic PS/2 counterparts. This means one can use an USB keyboard to
|
| /openbmc/linux/kernel/gcov/ |
| H A D | gcov.h | 6 * defined to be compatible with gcc counterparts. For a better
|
| /openbmc/linux/include/asm-generic/ |
| H A D | fb.h | 36 * regular counterparts. The regular I/O functions provide in-order
|
| /openbmc/linux/Documentation/crypto/ |
| H A D | devel-algos.rst | 30 The counterparts to those functions are listed below.
157 The respective counterparts for unregistering the HASH transformation
|
| /openbmc/linux/Documentation/driver-api/hte/ |
| H A D | hte.rst | 16 in obtaining timestamps than using software counterparts i.e. ktime and
|
| /openbmc/openbmc-test-automation/lib/ |
| H A D | gen_robot_print.py | 142 …mes contains a list of all rprint functions which should be created from their sprint counterparts.
|
| /openbmc/u-boot/include/ |
| H A D | search.h | 46 * have reentrant counterparts ending with _r. The non-reentrant
|
| H A D | iotrace.h | 69 /* Tracing functions which mirror their io.h counterparts */
|
| /openbmc/linux/Documentation/admin-guide/hw-vuln/ |
| H A D | reg-file-data-sampling.rst | 35 part. Unlike their affected counterparts, they do not enumerate RFDS_CLEAR or
|
| /openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Telemetry/ |
| H A D | Report.interface.yaml | 52 equal to its counterparts in ReadingParameters property.
|
1234