Searched +full:board +full:- +full:2 (Results 1 – 25 of 439) sorted by relevance
12345678910>>...18
| /Documentation/devicetree/bindings/arm/ |
| D | fsl.yaml | 1 # SPDX-License-Identifier: GPL-2.0 3 --- 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Shawn Guo <shawnguo@kernel.org> 17 - description: i.MX1 based Boards 19 - enum: 20 - armadeus,imx1-apf9328 21 - fsl,imx1ads 22 - const: fsl,imx1 24 - description: i.MX23 based Boards [all …]
|
| D | atmel-at91.yaml | 1 # SPDX-License-Identifier: GPL-2.0 3 --- 4 $id: http://devicetree.org/schemas/arm/atmel-at91.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Alexandre Belloni <alexandre.belloni@bootlin.com> 11 - Claudiu Beznea <claudiu.beznea@microchip.com> 12 - Nicolas Ferre <nicolas.ferre@microchip.com> 22 - items: 23 - const: atmel,at91rm9200 24 - items: [all …]
|
| D | arm,integrator.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Linus Walleij <linus.walleij@linaro.org> 14 They are ARMv4, ARMv5 and ARMv6-capable using different core tiles, 23 - description: ARM Integrator Application Platform, this board has a PCI 27 rapid prototyping. See ARM DUI 0098B. This board can physically come 28 pre-packaged in a PC Tower form factor called Integrator/PP1 or a 31 - const: arm,integrator-ap 32 - description: ARM Integrator Compact Platform (HBI-0086), this board has [all …]
|
| D | arm,versatile.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Linus Walleij <linus.walleij@linaro.org> 13 The ARM Versatile boards are two variants of ARM926EJ-S evaluation boards 21 When fitted with the IB2 Interface Board, the Versatile AB will present an 23 interface board. 30 - description: The ARM Versatile Application Baseboard (HBI-0118) is an 31 evaluation board specifically for the ARM926EJ-S. It can be connected 32 to an IB1 interface board for a touchscreen-type use case or an IB2 [all …]
|
| /Documentation/devicetree/bindings/clock/ |
| D | cirrus,lochnagar.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause 3 --- 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 7 title: Cirrus Logic Lochnagar Audio Development Board 10 - patches@opensource.cirrus.com 13 Lochnagar is an evaluation and development board for Cirrus Logic 15 Logic devices on mini-cards, as well as allowing connection of various 25 [1] Clock : ../clock/clock-bindings.txt 28 [2] include/dt-bindings/clock/lochnagar.h 36 - cirrus,lochnagar1-clk [all …]
|
| D | qcom,videocc.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Taniya Das <quic_tdas@quicinc.com> 17 include/dt-bindings/clock/qcom,videocc-sc7180.h 18 include/dt-bindings/clock/qcom,videocc-sc7280.h 19 include/dt-bindings/clock/qcom,videocc-sdm845.h 20 include/dt-bindings/clock/qcom,videocc-sm8150.h 21 include/dt-bindings/clock/qcom,videocc-sm8250.h 26 - qcom,sc7180-videocc [all …]
|
| D | qcom,mmcc.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only 3 --- 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Jeffrey Hugo <quic_jhugo@quicinc.com> 11 - Taniya Das <quic_tdas@quicinc.com> 20 - qcom,mmcc-apq8064 21 - qcom,mmcc-apq8084 22 - qcom,mmcc-msm8226 23 - qcom,mmcc-msm8660 24 - qcom,mmcc-msm8960 [all …]
|
| /Documentation/arch/sh/ |
| D | new-machine.rst | 1 .. SPDX-License-Identifier: GPL-2.0 4 Adding a new board to LinuxSH 7 Paul Mundt <lethal@linux-sh.org> 18 of the board-specific code (with the exception of stboards) ended up 19 in arch/sh/kernel/ directly, with board-specific headers ending up in 20 include/asm-sh/. For the new kernel, things are broken out by board type, 24 Board-specific code:: 27 |-- arch 28 | `-- sh 29 | `-- boards [all …]
|
| /Documentation/driver-api/tty/ |
| D | moxa-smartio.rst | 11 2. System Requirement 25 - 2 ports multiport board 26 CP-102U, CP-102UL, CP-102UF 27 CP-132U-I, CP-132UL, 28 CP-132, CP-132I, CP132S, CP-132IS, 29 (CP-102, CP-102S) 31 - 4 ports multiport board 32 CP-104EL, 33 CP-104UL, CP-104JU, 34 CP-134U, CP-134U-I, [all …]
|
| /Documentation/devicetree/bindings/arm/hisilicon/ |
| D | hisilicon.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Wei Xu <xuwei5@hisilicon.com> 18 - description: Hi3660 based boards. 20 - const: hisilicon,hi3660-hikey960 21 - const: hisilicon,hi3660 23 - description: Hi3670 based boards. 25 - const: hisilicon,hi3670-hikey970 26 - const: hisilicon,hi3670 [all …]
|
| /Documentation/devicetree/bindings/soc/renesas/ |
| D | renesas.yaml | 1 # SPDX-License-Identifier: GPL-2.0 3 --- 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 7 title: Renesas SH-Mobile, R-Mobile, and R-Car Platform 10 - Geert Uytterhoeven <geert+renesas@glider.be> 17 - description: Emma Mobile EV2 19 - enum: 20 - renesas,kzm9d # Kyoto Microcomputer Co. KZM-A9-Dual 21 - const: renesas,emev2 23 - description: RZ/A1H (R7S72100) [all …]
|
| /Documentation/devicetree/bindings/ |
| D | dts-coding-style.rst | 1 .. SPDX-License-Identifier: GPL-2.0 9 the Devicetree Specification and the dtc compiler (including W=1 and W=2 16 --------------------------- 24 * Lowercase characters: [a-z] 25 * Digits: [0-9] 26 * Dash: - 28 2. Labels can use only the following characters: 30 * Lowercase characters: [a-z] 31 * Digits: [0-9] 42 gpi_dma2: dma-controller@a00000 { [all …]
|
| /Documentation/devicetree/bindings/riscv/ |
| D | sunxi.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 7 title: Allwinner RISC-V SoC-based boards 10 - Chen-Yu Tsai <wens@csie.org> 11 - Jernej Skrabec <jernej.skrabec@gmail.com> 12 - Samuel Holland <samuel@sholland.org> 15 Allwinner RISC-V SoC-based boards 22 - description: Dongshan Nezha STU SoM 24 - const: 100ask,dongshan-nezha-stu [all …]
|
| /Documentation/devicetree/bindings/board/ |
| D | fsl,bcsr.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/board/fsl,bcsr.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 7 title: Board Control and Status 10 - Frank Li <Frank.Li@nxp.com> 15 - fsl,mpc8360mds-bcsr 21 - compatible 22 - reg 27 - | [all …]
|
| D | fsl,fpga-qixis-i2c.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/board/fsl,fpga-qixis-i2c.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 7 title: Freescale on-board FPGA connected on I2C bus 10 - Frank Li <Frank.Li@nxp.com> 15 - items: 16 - enum: 17 - fsl,bsc9132qds-fpga 18 - const: fsl,fpga-qixis-i2c [all …]
|
| D | fsl,fpga-qixis.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/board/fsl,fpga-qixis.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 7 title: Freescale on-board FPGA/CPLD 10 - Frank Li <Frank.Li@nxp.com> 15 - items: 16 - const: fsl,p1022ds-fpga 17 - const: fsl,fpga-ngpixis 18 - items: [all …]
|
| /Documentation/devicetree/bindings/mtd/ |
| D | cadence-nand-controller.txt | 4 - compatible : "cdns,hp-nfc" 5 - reg : Contains two entries, each of which is a tuple consisting of a 9 - reg-names: should contain "reg" and "sdma" 10 - #address-cells: should be 1. The cell encodes the chip select connection. 11 - #size-cells : should be 0. 12 - interrupts : The interrupt number. 13 - clocks: phandle of the controller core clock (nf_clk). 16 - dmas: shall reference DMA channel associated to the NAND controller 17 - cdns,board-delay-ps : Estimated Board delay. The value includes the total 21 board delay = RE#PAD delay + PCB trace to device + PCB trace from device [all …]
|
| /Documentation/devicetree/bindings/net/bluetooth/ |
| D | brcm,bcm4377-bluetooth.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/net/bluetooth/brcm,bcm4377-bluetooth.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Sven Peter <sven@svenpeter.dev> 13 This binding describes Broadcom BCM4377 family PCIe-attached bluetooth chips 14 usually found in Apple machines. The Wi-Fi part of the chip is described in 15 bindings/net/wireless/brcm,bcm4329-fmac.yaml. 18 - $ref: bluetooth-controller.yaml# 23 - pci14e4,5fa0 # BCM4377 [all …]
|
| /Documentation/spi/ |
| D | spi-lm70llp.rst | 2 spi_lm70llp : LM70-LLP parport-to-SPI adapter 5 Supported board/chip: 7 * National Semiconductor LM70 LLP evaluation board 15 ----------- 17 temperature sensor evaluation board to the kernel's SPI core subsystem. 21 In effect, this driver turns the parallel port interface on the eval board 27 -------------------- 28 The schematic for this particular board (the LM70EVAL-LLP) is 31 https://download.datasheets.com/pdfs/documentation/nat/kit&board/lm70llpevalmanual.pdf 33 The hardware interfacing on the LM70 LLP eval board is as follows: [all …]
|
| /Documentation/devicetree/bindings/arm/cirrus/ |
| D | cirrus,ep9301.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause 3 --- 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 The EP93xx SoC is a ARMv4T-based with 200 MHz ARM9 CPU. 13 - Alexander Sverdlin <alexander.sverdlin@gmail.com> 14 - Nikita Shubin <nikita.shubin@maquefel.me> 21 - description: The TS-7250 is a compact, full-featured Single Board 24 - const: technologic,ts7250 25 - const: cirrus,ep9301 27 - description: The Liebherr BK3 is a derivate from ts7250 board [all …]
|
| /Documentation/devicetree/bindings/sound/ |
| D | ti,j721e-cpb-ivi-audio.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 5 --- 6 $id: http://devicetree.org/schemas/sound/ti,j721e-cpb-ivi-audio.yaml# 7 $schema: http://devicetree.org/meta-schemas/core.yaml# 9 title: Texas Instruments J721e Common Processor Board Audio Support 12 - Peter Ujfalusi <peter.ujfalusi@gmail.com> 15 The Infotainment board plugs into the Common Processor Board, the support of the 16 extension board is extending the CPB audio support, described in: 17 sound/ti,j721e-cpb-audio.txt 19 The audio support on the Infotainment Expansion Board consists of McASP0 [all …]
|
| /Documentation/driver-api/media/drivers/ |
| D | bttv-devel.rst | 1 .. SPDX-License-Identifier: GPL-2.0 7 ------------------------- 12 sound is handled in slightly different ways on each board. 15 bttv-cards.c, which holds the information required for each board. 23 correct board type as insmod argument, ``insmod bttv card=2`` for 24 example. The file Documentation/admin-guide/media/bttv-cardlist.rst has a list 34 example. If your board has one, you might have to load a helper 36 chip used on your board: Bad luck. Start writing a new one. Well, 40 speakers connected directly to the grabber board. Hint: check the 48 Below is a do-it-yourself description for you. [all …]
|
| /Documentation/scsi/ |
| D | g_NCR5380.rst | 1 .. SPDX-License-Identifier: GPL-2.0 18 Use of an interrupt is recommended, if supported by the board, as this will 25 The NCR53c400 does not support DMA but it does have Pseudo-DMA which is 44 2 NCR53C400A, 50 These old-style parameters can support only one card: 56 ncr_5380=1 to set up for a NCR5380 board 57 ncr_53c400=1 to set up for a NCR53C400 board 58 ncr_53c400a=1 to set up for a NCR53C400A board 59 dtc_3181e=1 to set up for a Domex Technology Corp 3181E board 60 hp_c2502=1 to set up for a Hewlett Packard C2502 board [all …]
|
| /Documentation/devicetree/bindings/mips/ |
| D | ralink.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Sergio Paracuellos <sergio.paracuellos@gmail.com> 20 - description: Boards with Ralink RT2880 SoC 22 - enum: 23 - ralink,rt2880-eval-board 24 - const: ralink,rt2880-soc 26 - description: Boards with Ralink RT3050 SoC 28 - const: ralink,rt3050-soc [all …]
|
| /Documentation/networking/devlink/ |
| D | devlink-info.rst | 1 .. SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 7 The ``devlink-info`` mechanism enables device drivers to report device 10 The original motivation for the ``devlink-info`` API was twofold: 12 - making it possible to automate device and firmware management in a fleet 13 of machines in a vendor-independent fashion (see also 14 :ref:`Documentation/networking/devlink/devlink-flash.rst <devlink_flash>`); 15 - name the per component FW versions (as opposed to the crowded ethtool 18 ``devlink-info`` supports reporting multiple types of objects. Reporting driver 19 versions is generally discouraged - here, and via any other Linux API. 21 .. list-table:: List of top level info objects [all …]
|
12345678910>>...18