Home
last modified time | relevance | path

Searched refs:BUS (Results 1 – 25 of 30) sorted by relevance

12

/linux-5.19.10/Documentation/userspace-api/media/v4l/
Dsubdev-formats.rst265 * .. _MEDIA-BUS-FMT-RGB444-1X12:
302 * .. _MEDIA-BUS-FMT-RGB444-2X8-PADHI-BE:
374 * .. _MEDIA-BUS-FMT-RGB444-2X8-PADHI-LE:
446 * .. _MEDIA-BUS-FMT-RGB555-2X8-PADHI-BE:
518 * .. _MEDIA-BUS-FMT-RGB555-2X8-PADHI-LE:
590 * .. _MEDIA-BUS-FMT-RGB565-1X16:
627 * .. _MEDIA-BUS-FMT-BGR565-2X8-BE:
699 * .. _MEDIA-BUS-FMT-BGR565-2X8-LE:
771 * .. _MEDIA-BUS-FMT-RGB565-2X8-BE:
843 * .. _MEDIA-BUS-FMT-RGB565-2X8-LE:
[all …]
/linux-5.19.10/Documentation/translations/zh_CN/PCI/
Dpci-iov-howto.rst77 /sys/bus/pci/devices/<DOMAIN:BUS:DEVICE.FUNCTION>/sriov_numvfs
88 /sys/bus/pci/devices/<DOMAIN:BUS:DEVICE.FUNCTION>/sriov_numvfs
95 /sys/bus/pci/devices/<DOMAIN:BUS:DEVICE.FUNCTION>/sriov_drivers_autoprobe
102 /sys/bus/pci/devices/<DOMAIN:BUS:DEVICE.FUNCTION>/sriov_drivers_autoprobe
/linux-5.19.10/Documentation/devicetree/bindings/rtc/
Dtrivial-rtc.yaml33 # I2C-BUS INTERFACE REAL TIME CLOCK MODULE
35 # I2C-BUS INTERFACE REAL TIME CLOCK MODULE
38 # I2C-BUS INTERFACE REAL TIME CLOCK MODULE with Battery Backed RAM
40 # I2C-BUS INTERFACE REAL TIME CLOCK MODULE
/linux-5.19.10/arch/sparc/kernel/
Dpsycho_common.h15 #define PSYCHO_CONFIG_ENCODE(BUS, DEVFN, REG) \ argument
16 (((unsigned long)(BUS) << 16) | \
Dprom_irqtrans.c102 #define SABRE_CONFIG_ENCODE(BUS, DEVFN, REG) \ argument
103 (((unsigned long)(BUS) << 16) | \
Dpci_schizo.c75 #define SCHIZO_CONFIG_ENCODE(BUS, DEVFN, REG) \ argument
76 (((unsigned long)(BUS) << 16) | \
/linux-5.19.10/Documentation/i2c/busses/
Di2c-sis5595.rst67 is a BUS driver, not a CHIP driver. A BUS driver is used by other CHIP
/linux-5.19.10/Documentation/PCI/
Dpci-iov-howto.rst77 /sys/bus/pci/devices/<DOMAIN:BUS:DEVICE.FUNCTION>/sriov_numvfs
88 /sys/bus/pci/devices/<DOMAIN:BUS:DEVICE.FUNCTION>/sriov_numvfs
96 /sys/bus/pci/devices/<DOMAIN:BUS:DEVICE.FUNCTION>/sriov_drivers_autoprobe
104 /sys/bus/pci/devices/<DOMAIN:BUS:DEVICE.FUNCTION>/sriov_drivers_autoprobe
/linux-5.19.10/Documentation/scsi/
Dsym53c8xx_2.rst46 10.2.6 Check SCSI BUS
54 10.4 SCSI BUS checking boot option
446 The driver will try to send a BUS DEVICE RESET message to the target.
565 10.2.6 Check SCSI BUS
691 10.4 SCSI BUS checking boot option
697 Since SCSI devices shall release the BUS at most 800 nano-seconds after SCSI
698 RESET has been asserted, any signal to TRUE may indicate a SCSI BUS problem.
699 Unfortunately, the following common SCSI BUS problems are not detected:
768 Data parity error detected on the PCI BUS.
779 BF (0x20), then the cause may be likely due to a PCI BUS problem.
[all …]
Dncr53c8xx.rst59 10.2.19 Check SCSI BUS
66 10.6 SCSI BUS checking boot option
607 The driver will try to send a BUS DEVICE RESET message to the target.
990 10.2.19 Check SCSI BUS
1038 when it arbitrated for the SCSI BUS.
1068 SCSI BUS check do not attach on error buschk:1
1210 10.6 SCSI BUS checking boot option.
1216 Since SCSI devices shall release the BUS at most 800 nano-seconds after SCSI
1217 RESET has been asserted, any signal to TRUE may indicate a SCSI BUS problem.
1218 Unfortunately, the following common SCSI BUS problems are not detected:
[all …]
DChangeLog.sym53c8xx238 that overclocked PCI BUS up to 48 MHz will not be refused.
239 The more the BUS is overclocked, the less the driver will
293 from a device that has received a BUS DEVICE RESET message from
310 - Add the control command 'resetdev' that allows to send a BUS
322 present and IGNORE WIDE RESIDUE message on the BUS at the same time).
411 kinds of screw-up that may happen on the SCSI BUS.
DChangeLog.sym53c8xx_235 Misdetection of BUS mode was triggered on module reload only,
/linux-5.19.10/Documentation/devicetree/bindings/mips/lantiq/
Dfpi-bus.txt1 Lantiq XWAY SoC FPI BUS binding
/linux-5.19.10/tools/perf/trace/beauty/
Dsignum.c18 P_SIGNUM(BUS); in syscall_arg__scnprintf_signum()
/linux-5.19.10/arch/arm/boot/dts/
Dat91-sama5d27_wlsom1_ek.dts20 serial2 = &uart5; /* mikro BUS 2 */
21 serial3 = &uart3; /* mikro BUS 1 */
Dat91-sama5d2_icp.dts23 serial0 = &uart0; /* debug uart0 + mikro BUS 1 */
24 serial1 = &uart1; /* mikro BUS 3 */
25 serial3 = &uart3; /* mikro BUS 2 */
Dat91-sama5d27_som1_ek.dts22 serial1 = &uart4; /* mikro BUS 1 */
23 serial2 = &uart2; /* mikro BUS 2 */
/linux-5.19.10/Documentation/devicetree/bindings/phy/
Dintel,lgm-usb-phy.yaml25 - description: APB BUS reset
/linux-5.19.10/Documentation/devicetree/bindings/spmi/
Dhisilicon,hisi-spmi-controller.yaml13 The HiSilicon SPMI BUS controller is found on some Kirin-based designs.
/linux-5.19.10/drivers/net/can/usb/
DKconfig102 tristate "Microchip CAN BUS Analyzer interface"
104 This driver supports the CAN BUS Analyzer interface
/linux-5.19.10/Documentation/devicetree/bindings/sound/
Drockchip,pdm.yaml38 - description: clock for PDM BUS
Drockchip-i2s.yaml46 - description: clock for I2S BUS
/linux-5.19.10/Documentation/networking/
Darcnet-hardware.rst39 There are two "types" of ARCnet - STAR topology and BUS topology. This
42 BUS cards to BUS cards. That makes sense, right? Well, it's not quite
107 Cards for coax cabling are shipped in two different variants: for BUS and
109 lies in the hybrid chip installed. BUS cards use high impedance output,
166 The BUS topology is very similar to the one used by Ethernet. The only
170 cable. A typical BUS ARCnet network looks like::
175 B - BUS type card
190 BUS network in place of a BUS card and a terminator::
195 But, according to my own experiments, you can simply hang a BUS type card
257 hubs in a large network is a bad idea. The maximum length of a single "BUS
[all …]
/linux-5.19.10/drivers/eisa/
Deisa.ids77 AIR3001 "ENET2E EISA BUS MASTER ETHERNET ADAPTER"
78 AIR3101 "ENET-2V LOCAL BUS MASTER ETHERNET ADAPTER"
1072 KCI3201 "ET32EM EISA 32-bit BUS-MASTER Ethernet Adapter"
1172 PLX1001 "OCEAN EISALink EISA 32-Bit BUS-MASTER Ethernet Controller"
1264 USC0340 "UltraStor - ULTRA-34F VESA VL-BUS Host Adapter"
/linux-5.19.10/Documentation/devicetree/bindings/remoteproc/
Dqcom,adsp.yaml267 - description: BUS clock

12