2018-05-06 21:58:06 +00:00
|
|
|
# SPDX-License-Identifier: GPL-2.0+
|
2015-11-10 01:06:16 +00:00
|
|
|
|
2017-03-21 11:49:48 +00:00
|
|
|
dtb-$(CONFIG_TARGET_AXS101) += axs101.dtb
|
|
|
|
dtb-$(CONFIG_TARGET_AXS103) += axs103.dtb
|
2016-08-04 11:35:01 +00:00
|
|
|
dtb-$(CONFIG_TARGET_NSIM) += nsim.dtb
|
2015-03-27 10:24:35 +00:00
|
|
|
dtb-$(CONFIG_TARGET_TB100) += abilis_tb100.dtb
|
2018-10-18 06:54:58 +00:00
|
|
|
dtb-$(CONFIG_TARGET_EMSDP) += emsdp.dtb
|
2020-04-21 22:29:18 +00:00
|
|
|
dtb-$(CONFIG_TARGET_HSDK) += hsdk.dtb hsdk-4xd.dtb
|
arc: Add support for IoT development kit
The DesignWare ARC IoT Development Kit is a versatile platform
that includes the necessary hardware and software to accelerate
software development and debugging of sensor fusion,
voice recognition and face detection designs.
More information is avaialble here [1] and here [2].
The board is based on real silicon with
ARC EM9D-based Data Fusion IP Subsystem.
It sports a rich set of I/O including
* DW USB OTG
* DW MobileStorage (used for micro SD-card)
* GPIO
* multiple serial interface including DW APB UART
* ADC, PWM and eFlash, SRAM and SPI Flash memory
* Real-Time Clock (RTC)
* Bluetooth module with worldwide regulatory compliance
(FCC, IC, CE, ETSI, TELEC)
* On-board 9-axis sensor (gyro, accelerometer and compass)
Extensible with Arduino, Pmod, mikroBUS connectors and a 2x18
extension header.
One of the most interesting features for developers is built-in
Digilent USB JTAG probe so only micro-USB cable is needed!
[1] https://www.synopsys.com/dw/ipdir.php?ds=arc_iot_development_kit
[2] https://www.synopsys.com/dw/doc.php/ds/cc/iot_dev_kit.pdf
Signed-off-by: Alexey Brodkin <abrodkin@synopsys.com>
2018-01-24 18:37:14 +00:00
|
|
|
dtb-$(CONFIG_TARGET_IOT_DEVKIT) += iot_devkit.dtb
|
2015-03-17 11:55:14 +00:00
|
|
|
|
dts: automatically build necessary .dtb files
When building for a custom board, it is quite common to maintain a
private branch which include some defconfig and .dts files. But to
hook up those .dts files requires modifying a file "belonging" to
upstream U-Boot, the arch/*/dts/Makefile. Forward-porting that branch
to a newer upstream then often results in a conflict which, while it
is trivial to resolve by hand, makes it harder to have a CI do "try to
build our board against latest upstream".
The .config usually includes information on precisely what .dtb(s) are
needed, so to avoid having to modify the Makefile, simply add the
files in (SPL_)OF_LIST to dtb-y.
A technicality is that (SPL_)OF_LIST is not always defined, so rework
the Kconfig symbols so that (SPL_)OF_LIST is always defined (when
(SPL_)OF_CONTROL), but only prompted for in the cases which used to be
their "depends on".
nios2 and microblaze already have something like this in their
dts/Makefile, and the rationale in commit 41f59f68539 is similar to
the above. So this simply generalizes existing practice. Followup
patches could remove the logic in those two makefiles, just as there's
potential for moving some common boilerplate from all the
arch/*/dts/Makefile files to the new scripts/Makefile.dts.
Signed-off-by: Rasmus Villemoes <rasmus.villemoes@prevas.dk>
Reviewed-by: Simon Glass <sjg@chromium.org>
2022-01-10 13:34:41 +00:00
|
|
|
include $(srctree)/scripts/Makefile.dts
|
|
|
|
|
2015-03-17 11:55:14 +00:00
|
|
|
targets += $(dtb-y)
|
|
|
|
|
|
|
|
DTC_FLAGS += -R 4 -p 0x1000
|
|
|
|
|
|
|
|
PHONY += dtbs
|
|
|
|
dtbs: $(addprefix $(obj)/, $(dtb-y))
|
|
|
|
@:
|
|
|
|
|
|
|
|
clean-files := *.dtb
|