Home
last modified time | relevance | path

Searched +full:board +full:- +full:type (Results 1 – 25 of 204) sorted by relevance

123456789

/Documentation/arch/sh/
Dnew-machine.rst1 .. 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,
21 companion chip type, and CPU type. Looking at a tree view of this directory
24 Board-specific code::
27 |-- arch
28 | `-- sh
[all …]
/Documentation/devicetree/bindings/arm/
Darm,versatile.yaml1 # 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 …]
Dmicrochip,sparx5.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Lars Povlsen <lars.povlsen@microchip.com>
13 The Microchip Sparx5 SoC is a ARMv8-based used in a family of
14 gigabit TSN-capable gigabit switches.
16 The SparX-5 Ethernet switch family provides a rich set of switching
17 features such as advanced TCAM-based VLAN and QoS processing
19 TCAM-based frame processing using versatile content aware processor
27 - description: The Sparx5 pcb125 board is a modular board,
[all …]
/Documentation/devicetree/bindings/net/bluetooth/
Dbrcm,bcm4377-bluetooth.yaml1 # 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/networking/devlink/
Dnfp.rst1 .. SPDX-License-Identifier: GPL-2.0
13 .. list-table:: Generic parameters implemented
15 * - Name
16 - Mode
17 * - ``fw_load_policy``
18 - permanent
19 * - ``reset_dev_on_drv_probe``
20 - permanent
27 .. list-table:: devlink info versions implemented
30 * - Name
[all …]
Dbnxt.rst1 .. SPDX-License-Identifier: GPL-2.0
13 .. list-table:: Generic parameters implemented
15 * - Name
16 - Mode
17 * - ``enable_sriov``
18 - Permanent
19 * - ``ignore_ari``
20 - Permanent
21 * - ``msix_vec_per_pf_max``
22 - Permanent
[all …]
Di40e.rst1 .. SPDX-License-Identifier: GPL-2.0
15 .. list-table:: devlink info versions implemented
18 * - Name
19 - Type
20 - Example
21 - Description
22 * - ``board.id``
23 - fixed
24 - K15190-000
25 - The Product Board Assembly (PBA) identifier of the board.
[all …]
/Documentation/driver-api/media/drivers/
Dbttv-devel.rst1 .. 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.
18 log, telling which card type is used. Like this one::
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
[all …]
/Documentation/devicetree/bindings/nvmem/layouts/
Dkontron,sl28-vpd.yaml1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/nvmem/layouts/kontron,sl28-vpd.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: NVMEM layout of the Kontron SMARC-sAL28 vital product data
10 - Michael Walle <michael@walle.cc>
15 on-board ethernet devices are derived from this base MAC address by
22 const: kontron,sl28-vpd
24 serial-number:
25 type: object
[all …]
/Documentation/devicetree/bindings/sound/
Dimx-audio-hdmi.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/sound/imx-audio-hdmi.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Shengjiu Wang <shengjiu.wang@nxp.com>
15 - fsl,imx-audio-hdmi
16 - fsl,imx-audio-sii902x
22 audio-cpu:
26 hdmi-out:
27 type: boolean
[all …]
/Documentation/ABI/testing/
Dsysfs-bus-i2c-devices-turris-omnia-mcu5 Description: (RO) Contains board revision number.
7 Only available if board information is burned in the MCU (older
8 revisions have board information burned in the ATSHA204-A chip).
20 Only available if board information is burned in the MCU (older
21 revisions have board information burned in the ATSHA204-A chip).
35 - ``mcu`` makes the button press event be handled by the MCU to
37 - ``cpu`` makes the button press event be handled by the CPU.
89 Description: (RO) Contains the microcontroller type (STM32, GD32, MKL).
98 how long the rear reset button was held by the user during board
107 Description: (RO) Contains the 64-bit board serial number in hexadecimal
[all …]
Dsysfs-firmware-lefi-boardinfo6 this is useful to point out the current used mainboard type
18 Board Info
20 Board Name : LEMOTE-LS3A4000-7A1000-1w-V01-pc
25 Version : Kunlun-A1901-V4.1.3-20200414093938
27 Release Date : 2020-04-14
/Documentation/sound/hd-audio/
Dmodels.rst2 HD-Audio Codec-Specific Models
8 3-jack in back and a headphone out
9 3stack-digout
10 3-jack in back, a HP out and a SPDIF out
12 5-jack in back, 2-jack in front
13 5stack-digout
14 5-jack in back, 2-jack in front, a SPDIF out
16 6-jack in back, 2-jack in front
17 6stack-digout
18 6-jack with a SPDIF out
[all …]
/Documentation/devicetree/bindings/net/wireless/
Dbrcm,bcm4329-fmac.yaml1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/net/wireless/brcm,bcm4329-fmac.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Arend van Spriel <arend@broadcom.com>
19 - $ref: ieee80211.yaml#
24 - items:
25 - enum:
26 - brcm,bcm43143-fmac
27 - brcm,bcm4341b0-fmac
[all …]
/Documentation/devicetree/bindings/power/reset/
Datmel,sama5d2-shdwc.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/power/reset/atmel,sama5d2-shdwc.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Claudiu Beznea <claudiu.beznea@microchip.com>
14 and VDDCORE and the wake-up detection on debounced input lines.
19 - items:
20 - const: microchip,sama7g5-shdwc
21 - const: syscon
22 - enum:
[all …]
/Documentation/scsi/
Dg_NCR5380.rst1 .. 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
39 card=xx[,...] card type(s):
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/fb/
Dvesafb.rst20 * You can run XF68_FBDev on top of /dev/fb0 (=> non-accelerated X11
21 support for every VBE 2.0 compliant graphics board).
22 * Most important: boot logo :-)
33 Documentation/admin-guide/svga.rst for details.
70 lilo.conf file and rerun LILO. Then you can type in the desired
76 Even if your board does, it might be the BIOS which does not. VESA BIOS
81 "vga=mode-number" you have to transform the numbers to decimal.
88 XF68_FBDev should work just fine, but it is non-accelerated. Running
89 another (accelerated) X-Server like XF86_SVGA might or might not work.
90 It depends on X-Server and graphics board.
[all …]
/Documentation/devicetree/bindings/usb/
Domap-usb.txt4 - compatible : Should be "ti,omap4-musb" or "ti,omap3-musb"
5 - ti,hwmods : must be "usb_otg_hs"
6 - multipoint : Should be "1" indicating the musb controller supports
7 multipoint. This is a MUSB configuration-specific setting.
8 - num-eps : Specifies the number of endpoints. This is also a
9 MUSB configuration-specific setting. Should be set to "16"
10 - ram-bits : Specifies the ram address size. Should be set to "12"
11 - interface-type : This is a board specific setting to describe the type of
14 - mode : Should be "3" to represent OTG. "1" signifies HOST and "2"
16 - power : Should be "50". This signifies the controller can supply up to
[all …]
/Documentation/driver-api/tty/
Dmoxa-smartio.rst25 - 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,
36 CP-114, CP-114I, CP-114S, CP-114IS, CP-114UL,
[all …]
/Documentation/devicetree/bindings/net/
Dwiznet,w5x00.txt9 - compatible: Should be one of the following strings:
13 - reg: Specify the SPI chip select the chip is wired to.
14 - interrupts: Specify the interrupt index within the interrupt controller (referred
15 to above in interrupt-parent) and interrupt type. w5x00 natively
16 generates falling edge interrupts, however, additional board logic
18 - pinctrl-names: List of assigned state names, see pinctrl binding documentation.
19 - pinctrl-0: List of phandles to configure the GPIO pin used as interrupt line,
24 - spi-max-frequency: Maximum frequency of the SPI bus when accessing the w5500.
26 board designs may need to limit this value.
27 - local-mac-address: See ethernet.txt in the same directory.
[all …]
Dmicrochip,enc28j60.txt9 - compatible: Should be "microchip,enc28j60"
10 - reg: Specify the SPI chip select the ENC28J60 is wired to
11 - interrupts: Specify the interrupt index within the interrupt controller (referred
12 to above in interrupt-parent) and interrupt type. The ENC28J60 natively
13 generates falling edge interrupts, however, additional board logic
15 - pinctrl-names: List of assigned state names, see pinctrl binding documentation.
16 - pinctrl-0: List of phandles to configure the GPIO pin used as interrupt line,
21 - spi-max-frequency: Maximum frequency of the SPI bus when accessing the ENC28J60.
23 board designs may need to limit this value.
31 compatible = "fsl,imx28-spi";
[all …]
/Documentation/arch/powerpc/
Dbootwrapper.rst16 used firmware type on general purpose PowerPC systems from Apple, IBM and
17 others. U-Boot is typically found on embedded PowerPC hardware, but there
28 U-Boot (for versions that don't understand the device
31 are all embedded inside the U-Boot uImage file format
37 bd_info structure used in the old U-Boot interfaces,
39 U-Boot platform has a different platform init file
44 cuImage init code for a specific board can be found in
56 data from the board firmware, but simpleImages do not
60 Planet boards using the PlanetCore firmware. Board
70 kernel with this image type and it depends entirely on
[all …]
Dbooting.rst1 .. SPDX-License-Identifier: GPL-2.0
4 ------------------
9 bootloader <-> kernel interfaces, in order to avoid the degeneration that had
12 this scheme, but no new board support will be accepted in the main tree that
14 merged architecture for ppc32 and ppc64, new 32-bit platforms and 32-bit
19 of a device-tree whose format is defined after Open Firmware specification.
20 However, in order to make life easier to embedded board vendors, the kernel
21 doesn't require the device-tree to represent every device in the system and only
29 code all sorts of tables. It also makes it more flexible for board vendors to do
47 bindings to powerpc. Only the 32-bit client interface
[all …]
/Documentation/devicetree/bindings/
Ddts-coding-style.rst1 .. SPDX-License-Identifier: GPL-2.0
16 ---------------------------
24 * Lowercase characters: [a-z]
25 * Digits: [0-9]
26 * Dash: -
30 * Lowercase characters: [a-z]
31 * Digits: [0-9]
42 gpi_dma2: dma-controller@a00000 {
43 compatible = "qcom,sm8550-gpi-dma", "qcom,sm6350-gpi-dma";
48 --------------
[all …]
/Documentation/devicetree/bindings/soc/renesas/
Drenesas.yaml1 # 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 …]

123456789