Lines Matching full:soc

4 SoC Subsystem
10 The SoC subsystem is a place of aggregation for SoC-specific code.
16 * SoC-specific drivers across architectures, in particular for 32- & 64-bit
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
25 The SoC subsystem also serves as an intermediate location for changes to
27 of new platforms, or the removal of existing ones, often go through the SoC
30 The main SoC tree is housed on git.kernel.org:
31   https://git.kernel.org/pub/scm/linux/kernel/git/soc/soc.git/
37 small group of people are capable of maintaining.  Instead, the SoC subsystem
48 sending pull requests to the main SoC tree.  These trees are usually, but not
51 What the SoC tree is not, however, is a location for architecture-specific code
55 Submitting Patches for Given SoC
58 All typical platform related patches should be sent via SoC submaintainers
63 Submitting Patches to the Main SoC Maintainers
66 The main SoC maintainers can be reached via the alias soc@kernel.org only in
73 3. Introducing a completely new SoC platform.  Such new SoC work should be sent
76    soc@kernel.org in one patchset containing new arch/foo/Kconfig entry, DTS
82 Note that the soc@kernel.org is usually not the place to discuss the patches,
144 platform that are set at the SoC level, like CPU cores, are contained in a file
145 named $soc.dtsi, for example, jh7100.dtsi.  Integration details, that will vary
146 from board to board, are described in $soc-$board.dts.  An example of this is
149 between the $soc.dtsi and $soc-$board.dts files, containing the descriptions of
152 Some platforms also have System on Modules, containing an SoC, which are then
153 integrated into several different boards. For these platforms, $soc-$som.dtsi
154 and $soc-$som-$board.dts are typical.
156 Directories are usually named after the vendor of the SoC at the time of its
168 add any new warnings.  For RISC-V and Samsung SoC, ``make dtbs_check W=1`` is
176 Just as the main SoC tree has several branches, it is expected that
179 SoC maintainers.  Each branch should be usable by itself and avoid
182 Small sets of patches can also be sent as separate emails to soc@kernel.org,
186 top-level branches, e.g. for a treewide rework, or the addition of new SoC
191 SoC tree.  An example here would be one branch for devicetree warning fixes, one