Searched +full:board +full:- +full:specific (Results 1 – 25 of 177) sorted by relevance
12345678
| /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/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
35 find one that matches the most specific compatible. It will then look
[all …]
|
| /Documentation/devicetree/bindings/arm/ |
| D | ste-nomadik.txt | 1 ST-Ericsson Nomadik Device Tree Bindings
3 For various board the "board" node may contain specific properties
4 that pertain to this particular board, such as board-specific GPIOs.
7 - Nomadik System and reset controller used for basic chip control, clock
9 - compatible: must be "stericsson,nomadik,src"
13 Nomadik NHK-15 board manufactured by ST Microelectronics:
17 compatible="st,nomadik-nhk-15";
23 compatible="calaosystems,usb-s8815";
25 Required node: usb-s8815
29 usb-s8815 {
[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/devicetree/bindings/display/hisilicon/ |
| D | dw-dsi.txt | 1 Device-Tree bindings for DesignWare DSI Host Controller v1.20a driver
7 - compatible: value should be "hisilicon,hi6220-dsi".
8 - reg: physical base address and length of dsi controller's registers.
9 - clocks: contains APB clock phandle + clock-specifier pair.
10 - clock-names: should be "pclk".
11 - ports: contains DSI controller input and output sub port.
17 A example of HiKey board hi6220 SoC and board specific DT entry:
20 SoC specific:
22 compatible = "hisilicon,hi6220-dsi";
25 clock-names = "pclk";
[all …]
|
| /Documentation/networking/devlink/ |
| D | bnxt.rst | 1 .. 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 …]
|
| 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/admin-guide/media/ |
| D | cardlist.rst | 1 .. SPDX-License-Identifier: GPL-2.0
8 platform-specific drivers. It also contains several ancillary I²C drivers.
10 The platform-specific drivers are usually present on embedded systems,
11 or are supported by the main board. Usually, setting them is done via
14 The PCI and USB drivers, however, are independent of the system's board,
24 usb-cardlist
25 pci-cardlist
26 platform-cardlist
27 radio-cardlist
28 i2c-cardlist
[all …]
|
| /Documentation/devicetree/ |
| D | usage-model.rst | 1 .. SPDX-License-Identifier: GPL-2.0
44 ----------
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 -------------------
84 hardware configuration from the board and device driver support in the
86 it allows board and device support to become data driven; to make
[all …]
|
| /Documentation/devicetree/bindings/input/ |
| D | brcm,bcm-keypad.txt | 3 Broadcom Keypad controller is used to interface a SoC with a matrix-type
6 The keypad controller can sense a key-press and key-release and report the
9 This binding is based on the matrix-keymap binding with the following
12 keypad,num-rows and keypad,num-columns are required.
14 Required SoC Specific Properties:
15 - compatible: should be "brcm,bcm-keypad"
17 - reg: physical base address of the controller and length of memory mapped
20 - interrupts: The interrupt number to the cpu.
22 Board Specific Properties:
23 - keypad,num-rows: Number of row lines connected to the keypad
[all …]
|
| /Documentation/process/ |
| D | maintainer-soc.rst | 1 .. SPDX-License-Identifier: GPL-2.0
8 --------
10 The SoC subsystem is a place of aggregation for SoC-specific code.
13 * devicetrees for 32- & 64-bit ARM and RISC-V
14 * 32-bit ARM board files (arch/arm/mach*)
15 * 32- & 64-bit ARM defconfigs
16 * SoC-specific drivers across architectures, in particular for 32- & 64-bit
17 ARM, RISC-V and Loongarch
19 These "SoC-specific drivers" do not include clock, GPIO etc drivers that have
20 other top-level maintainers. The drivers/soc/ directory is generally meant
[all …]
|
| /Documentation/devicetree/bindings/usb/ |
| D | omap-usb.txt | 1 OMAP GLUE AND OTHER OMAP SPECIFIC COMPONENTS
4 - 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"
[all …]
|
| /Documentation/arch/powerpc/ |
| D | bootwrapper.rst | 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,
38 cuImages are platform specific. Each specific
39 U-Boot platform has a different platform init file
41 from the platform specific bd_info file. The platform
42 specific cuImage platform init code can be found in
44 cuImage init code for a specific board can be found in
55 dtbImages have platform specific code for extracting
[all …]
|
| /Documentation/devicetree/bindings/pinctrl/ |
| D | pinctrl-sirf.txt | 4 - compatible : "sirf,prima2-pinctrl"
5 - reg : Address range of the pinctrl registers
6 - interrupts : Interrupts used by every GPIO group
7 - gpio-controller : Indicates this device is a GPIO controller
8 - interrupt-controller : Marks the device node as an interrupt controller
10 - sirf,pullups : if n-th bit of m-th bank is set, set a pullup on GPIO-n of bank m
11 - sirf,pulldowns : if n-th bit of m-th bank is set, set a pulldown on GPIO-n of bank m
13 Please refer to pinctrl-bindings.txt in this directory for details of the common
19 Required subnode-properties:
20 - sirf,pins : An array of strings. Each string contains the name of a group.
[all …]
|
| D | pinctrl-bindings.txt | 4 such as pull-up/down, tri-state, drive-strength etc are designated as pin
13 set up certain specific pin configurations. Some client devices need a
15 need to reconfigure pins at run-time, for example to tri-state pins when the
26 driver loads. This would allow representing a board's static pin configuration
29 individual board device tree files, and any requirements imposed by the
30 bindings for the individual client devices in use by that board, i.e. whether
31 they require certain specific named states for dynamic pin configuration.
47 pinctrl-0: List of phandles, each pointing at a pin configuration
65 pinctrl-1: List of phandles, each pointing at a pin configuration
68 pinctrl-n: List of phandles, each pointing at a pin configuration
[all …]
|
| /Documentation/fb/ |
| D | metronomefb.rst | 10 is from E-Ink Corporation. It is intended to be used to drive the E-Ink
11 Vizplex display media. E-Ink hosts some details of this controller and the
12 display media here http://www.e-ink.com/products/matrix/metronome.html .
16 which is then delivered to the AMLCD interface by a host specific method.
19 Metronomefb is platform independent and depends on a board specific driver
21 PXA board used in the AM-200 EPD devkit. This example is am200epd.c
|
| /Documentation/ABI/testing/ |
| D | sysfs-firmware-lefi-boardinfo | 12 requirement and specific for Loongson64, so only add a new
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/devicetree/bindings/arm/marvell/ |
| D | marvell,orion5x.txt | 2 ---------------------------------------------
9 In addition, the above compatible shall be extended with the specific
12 "marvell,orion5x-88f5181"
13 "marvell,orion5x-88f5182"
15 And in addition, the compatible shall be extended with the specific
16 board. Currently known boards are:
21 "lacie,ethernet-disk-mini-v2"
22 "lacie,d2-network"
23 "marvell,rd-88f5182-nas"
24 "maxtor,shared-storage-2"
|
| /Documentation/spi/ |
| D | spi-summary.rst | 5 02-Feb-2012
8 ------------
17 clocking modes through which data is exchanged; mode-0 and mode-3 are most
32 - SPI may be used for request/response style device protocols, as with
35 - It may also be used to stream data in either direction (half duplex),
38 - Some devices may use eight bit words. Others may use different word
39 lengths, such as streams of 12-bit or 20-bit digital samples.
41 - Words are usually sent with their most significant bit (MSB) first,
44 - Sometimes SPI is used to daisy-chain devices, like shift registers.
51 SPI is only one of the names used by such four-wire protocols, and
[all …]
|
| /Documentation/devicetree/bindings/leds/ |
| D | leds-el15203000.txt | 1 Crane Merchandising System - EL15203000 LED driver
2 --------------------------------------------------
4 This LED Board (aka RED LEDs board) is widely used in
6 The board manages 3 LEDs and supports predefined blinking patterns
7 for specific leds.
18 - cascade pattern
19 - inversed cascade pattern
20 - bounce pattern
21 - inversed bounce pattern
24 - compatible : "crane,el15203000"
[all …]
|
| /Documentation/devicetree/bindings/net/ |
| D | wiznet,w5x00.txt | 9 - 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,
20 see also generic and your platform specific pinctrl binding
24 - spi-max-frequency: Maximum frequency of the SPI bus when accessing the w5500.
26 board designs may need to limit this value.
[all …]
|
| D | microchip,enc28j60.txt | 9 - 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,
17 see also generic and your platform specific pinctrl binding
21 - spi-max-frequency: Maximum frequency of the SPI bus when accessing the ENC28J60.
23 board designs may need to limit this value.
[all …]
|
| /Documentation/gpu/ |
| D | automated_testing.rst | 1 .. SPDX-License-Identifier: GPL-2.0+
11 be very time-consuming when lots of different hardware configurations need to
29 drivers/gpu/drm/ci/gitlab-ci.yml
30 --------------------------------
33 bits, it specifies the specific version of the scripts to be used. There are
49 Revision of igt-gpu-tools being used, from
50 https://gitlab.freedesktop.org/drm/igt-gpu-tools
53 -------------------------------
55 IGT tests to be run on all drivers (unless mentioned in a driver's \*-skips.txt
58 drivers/gpu/drm/ci/${DRIVER_NAME}-${HW_REVISION}-fails.txt
[all …]
|
| /Documentation/devicetree/bindings/mmc/ |
| D | k3-dw-mshc.txt | 1 * Hisilicon specific extensions to the Synopsys Designware Mobile
4 Read synopsys-dw-mshc.txt for more details
9 by synopsys-dw-mshc.txt and the properties used by the Hisilicon specific
15 - "hisilicon,hi3660-dw-mshc": for controllers with hi3660 specific extensions.
16 - "hisilicon,hi3670-dw-mshc", "hisilicon,hi3660-dw-mshc": for controllers
17 with hi3670 specific extensions.
18 - "hisilicon,hi4511-dw-mshc": for controllers with hi4511 specific extensions.
19 - "hisilicon,hi6220-dw-mshc": for controllers with hi6220 specific extensions.
22 - hisilicon,peripheral-syscon: phandle of syscon used to control peripheral.
30 compatible = "hisilicon,hi4511-dw-mshc";
[all …]
|
| /Documentation/driver-api/mtd/ |
| D | spi-intel.rst | 2 Upgrading BIOS using spi-intel
6 controller which is used to hold BIOS and other platform specific data.
14 The spi-intel driver makes it possible to read and write the SPI serial
16 any of them set, the whole MTD device is made read-only to prevent
18 contents as read-only but it can be changed from kernel command line,
31 2) Install mtd-utils package [2]. We need this in order to erase the SPI
33 name "mtd-utils".
36 the board (you can also reload the driver passing "writeable=1" as
39 4) Once the board is up and running again, find the right MTD partition
64 board! Otherwise it will not start anymore::
[all …]
|
12345678