| /kernel/linux/linux-6.6/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 …]
|
| /kernel/linux/linux-5.10/Documentation/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 …]
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/board/ |
| D | fsl-board.txt | 1 Freescale Reference Board Bindings
6 * Board Control and Status (BCSR)
10 - compatible : Should be "fsl,<board>-bcsr"
11 - reg : Offset and length of the register set for the device
16 compatible = "fsl,mpc8360mds-bcsr";
20 * Freescale on-board FPGA
22 This is the memory-mapped registers for on board FPGA.
25 - compatible: should be a board-specific string followed by a string
27 "fsl,<board>-fpga", "fsl,fpga-pixis", or
28 "fsl,<board>-fpga", "fsl,fpga-qixis"
[all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/board/ |
| D | fsl-board.txt | 1 Freescale Reference Board Bindings
6 * Board Control and Status (BCSR)
10 - compatible : Should be "fsl,<board>-bcsr"
11 - reg : Offset and length of the register set for the device
16 compatible = "fsl,mpc8360mds-bcsr";
20 * Freescale on-board FPGA
22 This is the memory-mapped registers for on board FPGA.
25 - compatible: should be a board-specific string followed by a string
27 "fsl,<board>-fpga", "fsl,fpga-pixis", or
28 "fsl,<board>-fpga", "fsl,fpga-qixis"
[all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/arm/ |
| D | ste-u300.txt | 1 ST-Ericsson U300 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
5 or board power regulator supplies.
13 - compatible: must be "stericsson,u300-syscon".
14 - reg: the base address and size of the system controller.
18 S365 "Small Board U365":
21 This contains the board-specific information.
22 - compatible: must be "stericsson,s365".
23 - vana15-supply: the regulator supplying the 1.5V to drive the
[all …]
|
| 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 …]
|
| /kernel/linux/linux-6.6/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 …]
|
| /kernel/linux/linux-5.10/Documentation/admin-guide/media/ |
| D | davinci-vpbe.rst | 1 .. SPDX-License-Identifier: GPL-2.0
7 -----------------------
29 board specific settings (specified in board-xxx-evm.c). This allows
32 API to set timings in VENC for a specific display resolution. As of this
41 is connected, the timings for a specific standard/preset is retrieved from
42 the board specific table and the values are used to set the timings in
43 venc using non-standard timing mode.
48 add the available outputs as a board specific entry (i.e add the "LogicPD"
49 output name to board-xxx-evm.c). A table of timings for various LCDs
50 supported can be maintained in the board specific setup file to support
[all …]
|
| /kernel/linux/linux-5.10/arch/arm/mach-mmp/ |
| D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
19 bool "Marvell's PXA168 Aspenite Development Board"
23 Say 'Y' here if you want to support the Marvell PXA168-based
24 Aspenite Development Board.
27 bool "Marvell's PXA168 Zylonite2 Development Board"
31 Say 'Y' here if you want to support the Marvell PXA168-based
32 Zylonite2 Development Board.
35 bool "Marvell's PXA168 Avengers Lite Development Board"
39 Say 'Y' here if you want to support the Marvell PXA168-based
40 Avengers Lite Development Board.
[all …]
|
| /kernel/linux/linux-6.6/drivers/video/fbdev/ |
| D | hecubafb.c | 2 * linux/drivers/video/hecubafb.c -- FB driver for Hecuba/Apollo controller
12 * This work was possible because of apollo display code from E-Ink's website
15 * available by E-Ink on its support site. Some commands such as 0xA4
24 * It is intended to be architecture independent. A board specific driver
46 /* Display specific information */
75 par->board->set_data(par, data); in apollo_send_data()
78 par->board->set_ctl(par, HCB_DS_BIT, 0); in apollo_send_data()
81 par->board->wait_for_ack(par, 0); in apollo_send_data()
84 par->board->set_ctl(par, HCB_DS_BIT, 1); in apollo_send_data()
87 par->board->wait_for_ack(par, 1); in apollo_send_data()
[all …]
|
| /kernel/linux/linux-5.10/include/video/ |
| D | hecubafb.h | 2 * hecubafb.h - definitions for the hecuba framebuffer driver
15 /* Apollo controller specific defines */
22 /* Hecuba interface specific defines */
29 /* struct used by hecuba. board specific stuff comes from *board */
32 struct hecuba_board *board; member
37 /* board specific routines
38 board drivers can implement wait_for_ack with interrupts if desired. if
|
| D | broadsheetfb.h | 2 * broadsheetfb.h - definitions for the broadsheet framebuffer driver
36 /* Broadsheet pin interface specific defines */
41 /* Broadsheet IO interface specific defines */
45 /* struct used by broadsheet. board specific stuff comes from *board */
48 struct broadsheet_board *board; member
56 /* board specific routines */
|
| /kernel/linux/linux-6.6/include/video/ |
| D | hecubafb.h | 2 * hecubafb.h - definitions for the hecuba framebuffer driver
15 /* Apollo controller specific defines */
22 /* Hecuba interface specific defines */
29 /* struct used by hecuba. board specific stuff comes from *board */
32 struct hecuba_board *board; member
37 /* board specific routines
38 board drivers can implement wait_for_ack with interrupts if desired. if
|
| D | broadsheetfb.h | 2 * broadsheetfb.h - definitions for the broadsheet framebuffer driver
36 /* Broadsheet pin interface specific defines */
41 /* Broadsheet IO interface specific defines */
45 /* struct used by broadsheet. board specific stuff comes from *board */
48 struct broadsheet_board *board; member
56 /* board specific routines */
|
| /kernel/linux/linux-6.6/arch/mips/include/asm/octeon/ |
| D | cvmx-helper-board.h | 7 * Copyright (c) 2003-2008 Cavium Networks
14 * AS-IS and WITHOUT ANY WARRANTY; without even the implied warranty
21 * Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA
30 * Helper functions to abstract board specific data about
31 * network ports from the rest of the cvmx-helper files.
37 #include <asm/octeon/cvmx-helper.h>
58 #define CVMX_HELPER_BOARD_MGMT_IPD_PORT -10
62 * port. A result of -1 means there isn't a MII capable PHY
66 * This function must be modified for every new Octeon board.
68 * data to determine board types and revisions. It relies on the
[all …]
|
| /kernel/linux/linux-5.10/arch/mips/include/asm/octeon/ |
| D | cvmx-helper-board.h | 7 * Copyright (c) 2003-2008 Cavium Networks
14 * AS-IS and WITHOUT ANY WARRANTY; without even the implied warranty
21 * Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA
30 * Helper functions to abstract board specific data about
31 * network ports from the rest of the cvmx-helper files.
37 #include <asm/octeon/cvmx-helper.h>
58 #define CVMX_HELPER_BOARD_MGMT_IPD_PORT -10
62 * port. A result of -1 means there isn't a MII capable PHY
66 * This function must be modifed for every new Octeon board.
68 * data to determine board types and revisions. It relys on the
[all …]
|
| /kernel/linux/linux-6.6/Documentation/driver-api/gpio/ |
| D | legacy.rst | 13 A "General Purpose Input/Output" (GPIO) is a flexible software-controlled
17 (BGA) packages. Board schematics show which external hardware connects to
18 which GPIOs. Drivers can be written generically, so that board setup code
21 System-on-Chip (SOC) processors heavily rely on GPIOs. In some cases, every
22 non-dedicated pin can be configured as a GPIO; and most chips have at least
27 Most PC southbridges have a few dozen GPIO-capable pins (with only the BIOS
32 - Output values are writable (high=1, low=0). Some chips also have
34 value might be driven ... supporting "wire-OR" and similar schemes
37 - Input values are likewise readable (1, 0). Some chips support readback
38 of pins configured as "output", which is very useful in such "wire-OR"
[all …]
|
| /kernel/linux/linux-5.10/arch/arm/mach-davinci/ |
| D | Makefile | 1 # SPDX-License-Identifier: GPL-2.0
7 ccflags-$(CONFIG_ARCH_MULTIPLATFORM) := -I$(srctree)/$(src)/include
10 obj-y := serial.o usb.o common.o sram.o
12 obj-$(CONFIG_DAVINCI_MUX) += mux.o
14 # Chip specific
15 obj-$(CONFIG_ARCH_DAVINCI_DM644x) += dm644x.o devices.o
16 obj-$(CONFIG_ARCH_DAVINCI_DM355) += dm355.o devices.o
17 obj-$(CONFIG_ARCH_DAVINCI_DM646x) += dm646x.o devices.o
18 obj-$(CONFIG_ARCH_DAVINCI_DM365) += dm365.o devices.o
19 obj-$(CONFIG_ARCH_DAVINCI_DA830) += da830.o devices-da8xx.o usb-da8xx.o
[all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/mmc/ |
| D | samsung-sdhci.txt | 8 Required SoC Specific Properties:
9 - compatible: should be one of the following
10 - "samsung,s3c6410-sdhci": For controllers compatible with s3c6410 sdhci
12 - "samsung,exynos4210-sdhci": For controllers compatible with Exynos4 sdhci
15 Required Board Specific Properties:
16 - pinctrl-0: Should specify pin control groups used for this controller.
17 - pinctrl-names: Should contain only one value - "default".
21 compatible = "samsung,exynos4210-sdhci";
24 bus-width = <4>;
25 cd-gpios = <&gpk2 2 0>;
[all …]
|
| /kernel/linux/linux-5.10/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 …]
|
| /kernel/linux/linux-6.6/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 …]
|
| /kernel/linux/linux-5.10/Documentation/driver-api/gpio/ |
| D | legacy.rst | 13 A "General Purpose Input/Output" (GPIO) is a flexible software-controlled
17 (BGA) packages. Board schematics show which external hardware connects to
18 which GPIOs. Drivers can be written generically, so that board setup code
21 System-on-Chip (SOC) processors heavily rely on GPIOs. In some cases, every
22 non-dedicated pin can be configured as a GPIO; and most chips have at least
27 Most PC southbridges have a few dozen GPIO-capable pins (with only the BIOS
32 - Output values are writable (high=1, low=0). Some chips also have
34 value might be driven ... supporting "wire-OR" and similar schemes
37 - Input values are likewise readable (1, 0). Some chips support readback
38 of pins configured as "output", which is very useful in such "wire-OR"
[all …]
|
| /kernel/linux/linux-5.10/drivers/video/fbdev/ |
| D | hecubafb.c | 2 * linux/drivers/video/hecubafb.c -- FB driver for Hecuba/Apollo controller
12 * This work was possible because of apollo display code from E-Ink's website
15 * available by E-Ink on its support site. Some commands such as 0xA4
24 * It is intended to be architecture independent. A board specific driver
46 /* Display specific information */
75 par->board->set_data(par, data); in apollo_send_data()
78 par->board->set_ctl(par, HCB_DS_BIT, 0); in apollo_send_data()
81 par->board->wait_for_ack(par, 0); in apollo_send_data()
84 par->board->set_ctl(par, HCB_DS_BIT, 1); in apollo_send_data()
87 par->board->wait_for_ack(par, 1); in apollo_send_data()
[all …]
|
| /kernel/linux/linux-6.6/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 …]
|
| /kernel/linux/linux-6.6/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 …]
|