Lines Matching +full:board +full:- +full:specific

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
21 for kernel-internal drivers that are used by other drivers to provide SoC-
22 specific functionality like identifying an SoC revision or interfacing with
34 -----------
51 What the SoC tree is not, however, is a location for architecture-specific code
59 (platform-specific maintainers).  This includes also changes to per-platform or
69 1. There are no platform-specific maintainers.
71 2. Platform-specific maintainers are unresponsive.
79    platform-specific maintainers, who are going to be responsible for handling
87 ------------------------------------
96 Perhaps one of the most important things to highlight is that dt-bindings
118 missing additions to a header file in include/dt-bindings/, it will fail the
123 * Avoid defining custom macros in include/dt-bindings/ for hardware constants
124   that can be derived from a datasheet -- binding macros in header files should
146 from board to board, are described in $soc-$board.dts.  An example of this is
147 jh7100-beaglev-starlight.dts.  Often many boards are variations on a theme, and
148 frequently there are intermediate files, such as jh7100-common.dtsi, which sit
149 between the $soc.dtsi and $soc-$board.dts files, containing the descriptions of
153 integrated into several different boards. For these platforms, $soc-$som.dtsi
154 and $soc-$som-$board.dts are typical.
163 with the dt-bindings that describe the ABI.  Please read the section
164 "Running checks" of Documentation/devicetree/bindings/writing-schema.rst for
168 add any new warnings.  For RISC-V and Samsung SoC, ``make dtbs_check W=1`` is
186 top-level branches, e.g. for a treewide rework, or the addition of new SoC
199 While there is no cut-off time for late pull requests, it helps to only send
209 requests, please see Documentation/maintainer/pull-requests.rst.