diff options
| author | Rich Felker <dalias@libc.org> | 2016-01-23 00:45:41 (GMT) |
|---|---|---|
| committer | Rich Felker <dalias@libc.org> | 2016-03-17 19:46:11 (GMT) |
| commit | 7480e0aabd5f9e6c3e3b72ed206e89284e90f11f (patch) | |
| tree | afcdb346dbec13ea4be79f062e9f849caedceaae /arch/sh/boards/Kconfig | |
| parent | 45624ac38926c8c2f1a63b4a39e7b1997743e1b3 (diff) | |
| download | linux-7480e0aabd5f9e6c3e3b72ed206e89284e90f11f.tar.xz | |
sh: add device tree support and generic board using device tree
Add a new pseudo-board, within the existing SH boards/machine-vectors
framework, which does not represent any actual hardware but instead
requires all hardware to be described by the device tree blob provided
by the boot loader. Changes made are thus non-invasive and do not risk
breaking support for legacy boards.
New hardware, including the open-hardware J2 and associated SoC
devices, will use device free from the outset. Legacy SH boards can
transition to device tree once all their hardware has device tree
bindings, driver support for device tree, and a dts file for the
board.
It is intented that, once all boards are supported in the new
framework, the existing machine-vectors framework should be removed
and the new device tree setup code integrated directly.
Signed-off-by: Rich Felker <dalias@libc.org>
Diffstat (limited to 'arch/sh/boards/Kconfig')
| -rw-r--r-- | arch/sh/boards/Kconfig | 15 |
1 files changed, 15 insertions, 0 deletions
diff --git a/arch/sh/boards/Kconfig b/arch/sh/boards/Kconfig index 89963d13..5e52d53 100644 --- a/arch/sh/boards/Kconfig +++ b/arch/sh/boards/Kconfig @@ -6,6 +6,21 @@ config SOLUTION_ENGINE config SH_ALPHA_BOARD bool +config SH_DEVICE_TREE + bool "Board Described by Device Tree" + select OF + select OF_EARLY_FLATTREE + select CLKSRC_OF + select GENERIC_CALIBRATE_DELAY + help + Select Board Described by Device Tree to build a kernel that + does not hard-code any board-specific knowledge but instead uses + a device tree blob provided by the boot-loader. You must enable + drivers for any hardware you want to use separately. At this + time, only boards based on the open-hardware J-Core processors + have sufficient driver coverage to use this option; do not + select it if you are using original SuperH hardware. + config SH_SOLUTION_ENGINE bool "SolutionEngine" select SOLUTION_ENGINE |