Searched full:board (Results 1 – 25 of 594) sorted by relevance
12345678910>>...24
| /Documentation/devicetree/bindings/arm/ |
| D | fsl.yaml | 65 - description: i.MX27 APF27 SoM Board
71 - description: i.MX27 Eukrea CPUIMX27 SoM Board
77 - description: i.MX27 Phytec pca100 Board
83 - description: i.MX27 Phytec pcm970 Board
93 - bluegiga,apx4devkit # Bluegiga APx4 SoM on dev board
101 - msr,m28cu3 # M28 SoM with custom base board
106 - description: i.MX28 Aries M28 SoM Board
112 - description: i.MX28 Aries M28EVK Board
118 - description: i.MX28 Armadeus Systems APF28Dev Board
152 - description: i.MX28 Eukrea Electromatique MBMX283LC Board
[all …]
|
| D | ste-nomadik.txt | 3 For various board the "board" node may contain specific properties
4 that pertain to this particular board, such as board-specific GPIOs.
13 Nomadik NHK-15 board manufactured by ST Microelectronics:
|
| D | arm,integrator.yaml | 23 - description: ARM Integrator Application Platform, this board has a PCI
27 rapid prototyping. See ARM DUI 0098B. This board can physically come
32 - description: ARM Integrator Compact Platform (HBI-0086), this board has
37 - description: ARM Integrator Standard Development Board (SDB) Platform,
38 this board is a PCI-based board conforming to the Microsoft SDB
|
| D | atmel-at91.yaml | 41 - overkiz,kizboxmini-base # Overkiz kizbox Mini Base Board
42 - overkiz,kizboxmini-mb # Overkiz kizbox Mini Mother Board
44 - overkiz,smartkiz # Overkiz SmartKiz Board
60 - description: Overkiz kizbox3 board
109 - description: Nattis v2 board with Natte v2 power board
118 - description: TSE-850 v3 board
132 - description: Overkiz kizbox2 board with two heads
139 - description: Microchip SAMA5D3 Ethernet Development System Board
146 - description: CalAmp LMU5000 board
152 - description: Exegin Q5xR5 board
[all …]
|
| D | arm,versatile.yaml | 21 When fitted with the IB2 Interface Board, the Versatile AB will present an
23 interface board.
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
38 PCI host controller. Like the sibling board, it is done specifically
|
| /Documentation/networking/devlink/ |
| D | nfp.rst | 33 * - ``board.id``
35 - Identifier of the board design
36 * - ``board.rev``
38 - Revision of the board design
39 * - ``board.manufacture``
41 - Vendor of the board design
42 * - ``board.model``
44 - Model name of the board design
45 * - ``board.part_number``
47 - Part number of the board and its components
|
| D | devlink-info.rst | 47 * - ``board.serial_number``
48 - Board serial number of the device.
50 This is usually the serial number of the board, often available in
58 component identifiers or the board version reported in the PCI VPD.
124 board.id
127 Unique identifier of the board design.
129 board.rev
132 Board design revision.
144 board.manufacture
149 board.part_number
[all …]
|
| /Documentation/arch/sh/ |
| D | new-machine.rst | 4 Adding a new board to LinuxSH
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::
31 | | `-- board-specific files
33 | | `-- board-specific files
40 | `-- board-specific headers
42 | `-- board-specific headers
57 board-specific headers. Thus, include/asm-sh/hd64461 is home to all of the
[all …]
|
| /Documentation/arch/arm/google/ |
| D | chromebook-boot-flow.rst | 16 - Board name, specified at depthcharge_ compile time. This is $(BOARD) below.
17 - Board revision number, determined at runtime (perhaps by reading GPIO
23 - google,$(BOARD)-rev$(REV)-sku$(SKU)
24 - google,$(BOARD)-rev$(REV)
25 - google,$(BOARD)-sku$(SKU)
26 - google,$(BOARD)
31 Note that for some boards there may be extra board-specific logic to inject
41 As an example, if we're on board "lazor", rev 4, SKU 0 and we have two device
52 match board or SKU revisions that are "close by". That is to say that
53 if depthcharge_ knows it's on "rev4" of a board but there is no "rev4"
[all …]
|
| /Documentation/devicetree/bindings/clock/ |
| D | cirrus,lochnagar.yaml | 7 title: Cirrus Logic Lochnagar Audio Development Board
13 Lochnagar is an evaluation and development board for Cirrus Logic
59 - ln-pmic-32k # On board fixed clock.
60 - ln-clk-12m # On board fixed clock.
61 - ln-clk-11m # On board fixed clock.
62 - ln-clk-24m # On board fixed clock.
63 - ln-clk-22m # On board fixed clock.
64 - ln-clk-8m # On board fixed clock.
65 - ln-usb-clk-24m # On board fixed clock.
66 - ln-usb-clk-12m # On board fixed clock.
|
| D | qcom,videocc.yaml | 69 - description: Board XO source
83 - description: Board XO source
84 - description: Board active XO source
100 - description: Board XO source
116 - description: Board XO source
117 - description: Board active XO source
|
| /Documentation/devicetree/bindings/powerpc/4xx/ |
| D | akebono.txt | 2 IBM Akebono board device tree
5 The IBM Akebono board is a development board for the PPC476GTR SoC.
36 The Akebono board stores some board information such as the revision
46 The Akebono board has an Atmel AVR microprocessor attached to the I2C
47 bus as a power controller for the board.
|
| /Documentation/arch/arm/spear/ |
| D | overview.rst | 21 - SPEAr300 Evaluation Board
23 - SPEAr310 Evaluation Board
25 - SPEAr320 Evaluation Board
28 - SPEAr600 Evaluation Board
31 - SPEAr1310 Evaluation Board
33 - SPEAr1340 Evaluation Board
59 spear600.c. mach-spear* doesn't contains board specific files as they fully
|
| /Documentation/ABI/testing/ |
| D | sysfs-firmware-turris-mox-rwtm | 5 Description: (Read) Board version burned into eFuses of this Turris Mox board.
12 Description: (Read) MAC addresses burned into eFuses of this Turris Mox board.
21 Turris Mox Board.
28 Description: (Read) RAM size in MiB of this Turris Mox board as was detected
|
| D | sysfs-bus-i2c-devices-turris-omnia-mcu | 5 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).
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
110 Only available if board information is burned in the MCU (older
111 revisions have board information burned in the ATSHA204-A chip).
|
| D | sysfs-platform-mellanox-bootctl | 95 provided on a board-level label.
102 The "opn" sysfs attribute holds the board's part number.
103 This value is provided on a board-level label.
110 The "sku" sysfs attribute holds the board's SKU number.
111 This value is provided on a board-level label.
118 The "modl" sysfs attribute holds the board's model number.
119 This value is provided on a board-level label.
126 The "sn" sysfs attribute holds the board's serial number.
127 This value is provided on a board-level label.
134 The "uuid" sysfs attribute holds the board's UUID.
[all …]
|
| /Documentation/devicetree/bindings/riscv/ |
| D | sunxi.yaml | 27 - description: D1 Nezha board
32 - description: ClockworkPi R-01 SoM and v3.14 board
37 - description: ClockworkPi R-01 SoM, v3.14 board, and DevTerm expansion
57 - description: MangoPi MQ board
62 - description: MangoPi MQ Pro board
67 - description: MangoPi MQ-R board
|
| /Documentation/devicetree/bindings/arm/hisilicon/ |
| D | hisilicon.yaml | 33 - description: Hi4511 Board
47 - description: HiP04 D01 Board
51 - description: HiP05 D02 Board
55 - description: HiP06 D03 Board
59 - description: HiP07 D05 Board
|
| /Documentation/admin-guide/ |
| D | edid.rst | 10 Today, with the advent of Kernel Mode Setting, a graphics board is
15 - The graphics board does not recognize the monitor.
16 - The graphics board is unable to detect any EDID data.
17 - The graphics board incorrectly forwards EDID data to the driver.
|
| /Documentation/driver-api/media/drivers/ |
| D | bttv-devel.rst | 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
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
57 Most grabber board vendors use these pins to control an external chip
58 which does the sound routing. But every board is a little different.
64 information for each known board. You basically have to create a new
65 line for your board. The important fields are these two::
[all …]
|
| /Documentation/spi/ |
| D | spi-lm70llp.rst | 5 Supported board/chip:
7 * National Semiconductor LM70 LLP evaluation board
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
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:
63 A "gotcha": National Semiconductor's LM70 LLP eval board circuit schematic
|
| /Documentation/driver-api/tty/ |
| D | moxa-smartio.rst | 25 - 2 ports multiport board
31 - 4 ports multiport board
42 - 8 ports multiport board
89 PCI/UPCI board
99 Each port within the same multiport board shares the same IRQ. Up to
113 Naming convention for each Smartio/Industio multiport board is
117 Board Num. Device node
118 1st board ttyM0 - ttyM7
119 2nd board ttyM8 - ttyM15
120 3rd board ttyM16 - ttyM23
[all …]
|
| /Documentation/devicetree/bindings/sound/ |
| D | sirf-audio.txt | 9 - hp-pa-gpios: Need to be present if the board need control external
11 - spk-pa-gpios: Need to be present if the board need control external
13 - hp-switch-gpios: Need to be present if the board capable to detect jack
18 Board connectors:
|
| /Documentation/devicetree/bindings/soc/xilinx/ |
| D | xilinx.yaml | 52 - description: Xilinx internal board zc1232
58 - description: Xilinx internal board zc1254
64 - description: Xilinx evaluation board zcu1275
70 - description: Xilinx 96boards compatible board zcu100
76 - description: Xilinx 96boards compatible board Ultra96
84 - description: Xilinx evaluation board zcu102
94 - description: Xilinx evaluation board zcu104
103 - description: Xilinx evaluation board zcu106
111 - description: Xilinx evaluation board zcu111
|
| /Documentation/scsi/ |
| D | g_NCR5380.rst | 18 Use of an interrupt is recommended, if supported by the board, as this will
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
71 E.g. a port mapped NCR5380 board, driver to probe for IRQ::
79 E.g. a memory mapped NCR53C400 board with no IRQ::
|
12345678910>>...24