Searched +full:on +full:- +full:board (Results 1 – 25 of 447) 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 | 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
22 optional system controller node which controls the extra peripherals on the
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
[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,gcc-sdm845.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only
3 ---
4 $id: http://devicetree.org/schemas/clock/qcom,gcc-sdm845.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Qualcomm Global Clock & Reset Controller on SDM670 and SDM845
10 - Stephen Boyd <sboyd@kernel.org>
11 - Taniya Das <quic_tdas@quicinc.com>
15 domains on SDM670 and SDM845
17 See also:: include/dt-bindings/clock/qcom,gcc-sdm845.h
22 - qcom,gcc-sdm670
[all …]
|
| /Documentation/arch/arm/google/ |
| D | chromebook-boot-flow.rst | 1 .. SPDX-License-Identifier: GPL-2.0
16 - Board name, specified at depthcharge_ compile time. This is $(BOARD) below.
17 - Board revision number, determined at runtime (perhaps by reading GPIO
19 - SKU number, read from GPIO strappings at boot time. This is $(SKU) below.
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
[all …]
|
| /Documentation/arch/arm/spear/ |
| D | overview.rst | 6 ------------
11 The ST Microelectronics SPEAr range of ARM9/CortexA9 System-on-Chip CPUs are
19 - SPEAr3XX (3XX SOC series, based on ARM9)
20 - SPEAr300 (SOC)
21 - SPEAr300 Evaluation Board
22 - SPEAr310 (SOC)
23 - SPEAr310 Evaluation Board
24 - SPEAr320 (SOC)
25 - SPEAr320 Evaluation Board
26 - SPEAr6XX (6XX SOC series, based on ARM9)
[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/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
29 available (on page 4) here:
31 https://download.datasheets.com/pdfs/documentation/nat/kit&board/lm70llpevalmanual.pdf
[all …]
|
| /Documentation/ABI/testing/ |
| 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).
29 Description: (RW) The front button on the Turris Omnia router can be
30 configured either to change the intensity of all the LEDs on the
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.
47 low power mode. The router can be powered on by pressing the
[all …]
|
| D | sysfs-platform-mellanox-bootctl | 6 The Life-cycle state of the SoC, which could be one of the
12 GA Non-Secured Non-Secure chip and not able to change state
94 the out-of-band 1Gbps Ethernet port. This MAC address is
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.
[all …]
|
| D | sysfs-c2port | 13 The /sys/class/c2port/c2portX/ directory is related to X-th
37 access to the on-board flash of the connected micro.
45 the on-board flash block size of the connected micro.
52 the on-board flash blocks number of the connected micro.
59 the content of the on-board flash of the connected micro.
66 the "erase" command on the on-board flash of the connected
74 command on the connected micro.
|
| /Documentation/devicetree/ |
| D | usage-model.rst | 1 .. SPDX-License-Identifier: GPL-2.0
12 the device tree data format can be found on the device tree usage page
44 ----------
52 Since Open Firmware is commonly used on PowerPC and SPARC platforms,
56 In 2005, when PowerPC Linux began a major cleanup and to merge 32-bit
57 and 64-bit support, the decision was made to require DT support on all
61 blob without requiring a real Open Firmware implementation. U-Boot,
66 existing non-DT aware firmware.
74 -------------
79 -------------------
[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 -------------------------
11 completely by the bt8xx chip, which is common on all boards. But
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
[all …]
|
| /Documentation/devicetree/bindings/board/ |
| 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 …]
|
| /Documentation/admin-guide/ |
| D | edid.rst | 1 .. SPDX-License-Identifier: GPL-2.0
10 Today, with the advent of Kernel Mode Setting, a graphics board is
11 either correctly working because all components follow the standards -
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.
18 - The monitor sends no or bogus EDID data.
19 - A KVM sends its own EDID data instead of querying the connected monitor.
22 restrictions later on.
|
| D | devices.txt | 1 0 Unnamed devices (e.g. non-device mounts)
7 2 = /dev/kmem OBSOLETE - replaced by /proc/kcore
11 6 = /dev/core OBSOLETE - replaced by /proc/kcore
12 7 = /dev/full Returns ENOSPC on write
18 12 = /dev/oldmem OBSOLETE - replaced by /proc/vmcore
31 2 char Pseudo-TTY masters
37 Pseudo-tty's are named as follows:
40 the 1st through 16th series of 16 pseudo-ttys each, and
44 These are the old-style (BSD) PTY devices; Unix98
45 devices are on major 128 and above and use the PTY
[all …]
|
| /Documentation/devicetree/bindings/ |
| D | dts-coding-style.rst | 1 .. 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/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
18 round trip delay for the signals and is used for deciding on values
[all …]
|
| /Documentation/devicetree/bindings/mips/img/ |
| D | xilfpga.txt | 7 As we are dealing with a MIPS core instantiated on an FPGA, specifications
13 The example project runs on the Nexys4DDR board by Digilent powered by
14 the ARTIX-7 FPGA by Xilinx.
16 Relevant details about the example project and the Nexys4DDR board:
18 - microAptiv UP core m14Kc
19 - 50MHz clock speed
20 - 128Mbyte DDR RAM at 0x0000_0000
21 - 8Kbyte RAM at 0x1000_0000
22 - axi_intc at 0x1020_0000
23 - axi_uart16550 at 0x1040_0000
[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 …]
|
| /Documentation/devicetree/bindings/interrupt-controller/ |
| D | kontron,sl28cpld-intc.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/interrupt-controller/kontron,sl28cpld-intc.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Interrupt controller driver for the sl28cpld board management controller
10 - Michael Walle <michael@walle.cc>
13 This module is part of the sl28cpld multi-function device. For more
17 and handled by the board management controller.
22 0 RTC_INT# Interrupt line from on-board RTC
23 1 SMB_ALERT# Event on SMB_ALERT# line (P1)
[all …]
|
| /Documentation/devicetree/bindings/mfd/ |
| D | qriox.txt | 1 KEYMILE qrio Board Control CPLD
3 The qrio is a multifunction device that controls the KEYMILE boards based on
9 - compatible: "keymile,qriox"
10 - reg: access on the parent local bus (chip select, offset in chip select, size)
14 board-control@1,0 {
|
| /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
28 This driver provides some information on what it has detected in
33 When included as a module, parameters can be passed on the insmod/modprobe
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
[all …]
|
| /Documentation/arch/arm/sti/ |
| D | overview.rst | 6 ------------
9 CortexA9 System-on-Chip are supported by the 'STi' platform of
14 -------------
19 ------
22 are located in the platform code contained in arch/arm/mach-sti
24 There is a generic board board-dt.c in the mach folder which support
25 Flattened Device Tree, which means, It works with any compatible board with
30 ---------------
|
12345678910>>...18