Home
last modified time | relevance | path

Searched full:communicating (Results 1 – 25 of 254) sorted by relevance

1234567891011

/openbmc/linux/drivers/char/xillybus/
H A DKconfig27 Set to M if you want Xillybus to use PCI Express for communicating
48 XillyUSB is the Xillybus variant which uses USB for communicating
51 Set to M if you want Xillybus to use USB for communicating with
/openbmc/linux/net/mctp/
H A DKconfig7 protocol for communicating between management controllers and
11 This option enables core MCTP support. For communicating with other
/openbmc/linux/drivers/slimbus/
H A DKconfig34 communicating with slave HW directly over the bus using messaging
35 interface, and communicating with master component residing on ADSP
/openbmc/linux/drivers/spmi/
H A DKconfig34 This is required for communicating with Qualcomm PMICs and
45 This is required for communicating with Mediatek PMICs and
/openbmc/linux/arch/arm64/include/asm/
H A Dsync_bitops.h12 * under Xen you might be communicating with a completely external entity
13 * who might be on another CPU (e.g. two uniprocessor guests communicating
/openbmc/linux/arch/arm/include/asm/
H A Dsync_bitops.h11 * under Xen you might be communicating with a completely external entity
12 * who might be on another CPU (e.g. two uniprocessor guests communicating
/openbmc/linux/drivers/media/radio/si4713/
H A Dsi4713.c185 * @sdev: si4713_device structure for the device we are communicating
254 * @sdev: si4713_device structure for the device we are communicating
291 * @sdev: si4713_device structure for the device we are communicating
338 * @sdev: si4713_device structure for the device we are communicating
417 * @sdev: si4713_device structure for the device we are communicating
462 * @sdev: si4713_device structure for the device we are communicating
491 * @sdev: si4713_device structure for the device we are communicating
535 * @sdev: si4713_device structure for the device we are communicating
578 * @sdev: si4713_device structure for the device we are communicating
626 * @sdev: si4713_device structure for the device we are communicating
[all …]
/openbmc/linux/Documentation/devicetree/bindings/slimbus/
H A Dqcom,slim-ngd.yaml14 SLIMBus NGD controller is a light-weight driver responsible for communicating
16 communicating with master component residing on ADSP for bandwidth and
/openbmc/openbmc-test-automation/bin/
H A Dobmc_ser_num36 help="The username for communicating with the OpenBMC machine.",
42 help="The password for communicating with the OpenBMC machine.",
/openbmc/openbmc/meta-evb/meta-evb-arm/meta-evb-fvp-base/
H A DREADME.md6 where the Base FVP represents the management controller which is communicating
40 - pldmd will start communicating with the MCP once it's ready
/openbmc/linux/Documentation/ABI/stable/
H A Dsysfs-driver-ib_srp91 descriptor list in an SRP_CMD when communicating with an SRP
139 Description: Name of the InfiniBand HCA used for communicating with the
146 Description: Number of the HCA port used for communicating with the
/openbmc/openbmc/meta-openembedded/meta-networking/recipes-support/mdio-tools/
H A Dmdio-tools.inc1 DESCRIPTION = "A low-level debug tool for communicating with devices attached to an MDIO bus"
/openbmc/linux/drivers/media/platform/mediatek/vpu/
H A DKconfig10 communicating with VPU. This driver for hw video
/openbmc/openbmc-test-automation/lib/
H A Dopenbmc_ffdc.py71 gp.print_error("BMC is not communicating via ssh.\n")
76 "BMC is not communicating via ssh or Redfish. Terminating"
/openbmc/linux/drivers/crypto/
H A Datmel-i2c.h38 * atmel_i2c_cmd - structure used for communicating with the device.
158 * @cmd : structure used for communicating with the device.
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-support/hidapi/
H A Dhidapi_0.14.0.bb1 SUMMARY = "A Simple library for communicating with USB and Bluetooth HID devices"
/openbmc/openbmc/poky/meta/recipes-graphics/xorg-app/
H A Dxdpyinfo_1.3.4.bb7 predefined values for various parameters used in communicating between \
/openbmc/linux/Documentation/ABI/testing/
H A Dsysfs-bus-pci-devices-catpt6 communicating with.
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-support/switchtec-user/
H A Dswitchtec-user_4.2.bb1 SUMMARY = "Easy to use CLI and C library for communicating with Microsemi's Switchtec management in…
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-devtools/microcom/
H A Dmicrocom_2023.09.0.bb1 SUMMARY = "Minimalistic terminal program for communicating with devices over a serial connection"
/openbmc/qemu/ui/
H A Ddbus-display1.xml35 the capabilities with which they are communicating.
150 capabilities with which they are communicating.
462 the capabilities with which they are communicating.
718 the capabilities with which they are communicating.
781 the capabilities with which they are communicating.
881 the capabilities with which they are communicating.
983 the capabilities with which they are communicating.
1078 the capabilities with which they are communicating.
/openbmc/linux/Documentation/i2c/busses/
H A Di2c-amd-mp2.rst18 The MP2 is an ARM processor programmed as an I2C controller and communicating
/openbmc/linux/net/qrtr/
H A DKconfig36 transport used for communicating to external modems.
/openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Dump/
H A DNewDump.interface.yaml22 have a unique id but when communicating to the source of the
/openbmc/openbmc/poky/meta/files/common-licenses/
H A DEUPL-1.231 …tion’ or ‘Communication’:any act of selling, giving, lending, renting, distributing, communicating,
76 …Work is expressly distributed only under this version of the Licence — for example by communicating
86 Provision of Source Code: When distributing or communicating copies of the Work, the Licensee will …

1234567891011