| /Linux-v4.19/Documentation/media/uapi/v4l/ |
| D | subdev-formats.rst | 178 * .. _MEDIA-BUS-FMT-RGB444-1X12:
215 * .. _MEDIA-BUS-FMT-RGB444-2X8-PADHI-BE:
287 * .. _MEDIA-BUS-FMT-RGB444-2X8-PADHI-LE:
359 * .. _MEDIA-BUS-FMT-RGB555-2X8-PADHI-BE:
431 * .. _MEDIA-BUS-FMT-RGB555-2X8-PADHI-LE:
503 * .. _MEDIA-BUS-FMT-RGB565-1X16:
540 * .. _MEDIA-BUS-FMT-BGR565-2X8-BE:
612 * .. _MEDIA-BUS-FMT-BGR565-2X8-LE:
684 * .. _MEDIA-BUS-FMT-RGB565-2X8-BE:
756 * .. _MEDIA-BUS-FMT-RGB565-2X8-LE:
[all …]
|
| /Linux-v4.19/arch/sparc/kernel/ |
| D | psycho_common.h | 15 #define PSYCHO_CONFIG_ENCODE(BUS, DEVFN, REG) \ argument
16 (((unsigned long)(BUS) << 16) | \
|
| D | prom_irqtrans.c | 102 #define SABRE_CONFIG_ENCODE(BUS, DEVFN, REG) \ argument
103 (((unsigned long)(BUS) << 16) | \
|
| D | pci_schizo.c | 74 #define SCHIZO_CONFIG_ENCODE(BUS, DEVFN, REG) \ argument
75 (((unsigned long)(BUS) << 16) | \
|
| /Linux-v4.19/drivers/net/can/usb/ |
| D | Kconfig | 83 tristate "Microchip CAN BUS Analyzer interface"
85 This driver supports the CAN BUS Analyzer interface
105 tristate "Microchip CAN BUS Analyzer interface"
107 This driver supports the CAN BUS Analyzer interface
|
| /Linux-v4.19/Documentation/i2c/busses/ |
| D | i2c-sis5595 | 57 is a BUS driver, not a CHIP driver. A BUS driver is used by other CHIP
|
| /Linux-v4.19/Documentation/PCI/ |
| D | pci-iov-howto.txt | 62 /sys/bus/pci/devices/<DOMAIN:BUS:DEVICE.FUNCTION>/sriov_numvfs
69 /sys/bus/pci/devices/<DOMAIN:BUS:DEVICE.FUNCTION>/sriov_numvfs
75 /sys/bus/pci/devices/<DOMAIN:BUS:DEVICE.FUNCTION>/sriov_drivers_autoprobe
81 /sys/bus/pci/devices/<DOMAIN:BUS:DEVICE.FUNCTION>/sriov_drivers_autoprobe
|
| /Linux-v4.19/Documentation/scsi/ |
| D | sym53c8xx_2.txt | 39 10.2.6 Check SCSI BUS
47 10.4 SCSI BUS checking boot option
385 The driver will try to send a BUS DEVICE RESET message to the target.
476 10.2.6 Check SCSI BUS
560 10.4 SCSI BUS checking boot option.
565 Since SCSI devices shall release the BUS at most 800 nano-seconds after SCSI
566 RESET has been asserted, any signal to TRUE may indicate a SCSI BUS problem.
567 Unfortunately, the following common SCSI BUS problems are not detected:
630 Data parity error detected on the PCI BUS.
639 BF (0x20), then the cause may be likely due to a PCI BUS problem.
[all …]
|
| D | ncr53c8xx.txt | 52 10.2.19 Check SCSI BUS
59 10.6 SCSI BUS checking boot option
544 The driver will try to send a BUS DEVICE RESET message to the target.
819 10.2.19 Check SCSI BUS
851 when it arbitrated for the SCSI BUS.
877 SCSI BUS check do not attach on error buschk:1
993 10.6 SCSI BUS checking boot option.
998 Since SCSI devices shall release the BUS at most 800 nano-seconds after SCSI
999 RESET has been asserted, any signal to TRUE may indicate a SCSI BUS problem.
1000 Unfortunately, the following common SCSI BUS problems are not detected:
[all …]
|
| D | ChangeLog.sym53c8xx | 238 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.
|
| D | ChangeLog.sym53c8xx_2 | 35 Misdetection of BUS mode was triggered on module reload only,
|
| D | ChangeLog.ncr53c8xx | 487 This option enables checking of SCSI BUS data lines after SCSI
|
| /Linux-v4.19/Documentation/devicetree/bindings/mips/lantiq/ |
| D | fpi-bus.txt | 1 Lantiq XWAY SoC FPI BUS binding
|
| /Linux-v4.19/tools/perf/trace/beauty/ |
| D | signum.c | 16 P_SIGNUM(BUS); in syscall_arg__scnprintf_signum()
|
| /Linux-v4.19/Documentation/devicetree/bindings/sound/ |
| D | rockchip,pdm.txt | 13 - "pdm_hclk": clock for PDM BUS
|
| D | rockchip-i2s.txt | 27 - "i2s_hclk": clock for I2S BUS
|
| /Linux-v4.19/arch/arm/boot/dts/ |
| D | at91-sama5d27_som1_ek.dts | 58 serial1 = &uart4; /* mikro BUS 1 */
59 serial2 = &uart2; /* mikro BUS 2 */
|
| /Linux-v4.19/Documentation/networking/ |
| D | arcnet-hardware.txt | 35 There are two "types" of ARCnet - STAR topology and BUS topology. This
38 BUS cards to BUS cards. That makes sense, right? Well, it's not quite
98 Cards for coax cabling are shipped in two different variants: for BUS and
100 lies in the hybrid chip installed. BUS cards use high impedance output,
156 The BUS topology is very similar to the one used by Ethernet. The only
160 cable. A typical BUS ARCnet network looks like:
165 B - BUS type card
180 BUS network in place of a BUS card and a terminator:
185 But, according to my own experiments, you can simply hang a BUS type card
245 hubs in a large network is a bad idea. The maximum length of a single "BUS
[all …]
|
| /Linux-v4.19/drivers/mtd/spi-nor/ |
| D | Kconfig | 15 controller. This controller does not support generic SPI BUS, it only
|
| /Linux-v4.19/Documentation/devicetree/bindings/ |
| D | trivial-devices.txt | 54 epson,rx8010 I2C-BUS INTERFACE REAL TIME CLOCK MODULE
55 epson,rx8581 I2C-BUS INTERFACE REAL TIME CLOCK MODULE
|
| /Linux-v4.19/Documentation/devicetree/bindings/net/ |
| D | stmmac.txt | 65 - AXI BUS Mode parameters: below the list of all the parameters to program the
|
| /Linux-v4.19/drivers/eisa/ |
| D | eisa.ids | 77 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-v4.19/Documentation/devicetree/bindings/clock/ |
| D | exynos5433-clock.txt | 27 which generates clocks for Cortex-A5/BUS/AUDIO clocks.
|
| /Linux-v4.19/Documentation/spi/ |
| D | spi-summary | 506 BUS NUMBERING
|
| /Linux-v4.19/drivers/gpu/drm/nouveau/nvkm/engine/device/ |
| D | base.c | 2467 _(BUS , device->bus , &device->bus->subdev); in nvkm_device_subdev()
|
