On 08/07/2016 at 11:45:19 +0200, Arnd Bergmann wrote :
On Thursday, July 7, 2016 3:18:55 PM CEST Kevin Hilman wrote:
Well, by default, kernel CI will try to boot boards if it finds a DTB built for that build, but we do have support for blacklisting.
But...
IMO, the much better fix is for the kernel build not to build DTBs that can't possibly boot for that defconfig in the first place. That way other automated build infrastrucutre doesn't have to duplicate the kernelCI blacklisting.
I see mach-at91/Kconfig alrady has CONFIG_SOC_SAM_V7 and CONFIG_SOC_SAM_V4_V5, and those are already used in arch/arm/boot/dts/Makefile to select which DTs are actually compiled.
IMO, that approach should be expanded so that the DT files are not created for builds that can't possibly boot them.
Sounds good. Alexandre, does the change below look right to you?
Yes, that is what I had. Still, I was wondering whether we should split SOC_SAM_V7 using SOC_SAMA5D2, SOC_SAMA5D3 and SOC_SAMA5D4. We don't have any configuration enabling one without the others yet and I don't expect we will.
Signed-off-by: Arnd Bergmann arnd@arndb.de
diff --git a/arch/arm/boot/dts/Makefile b/arch/arm/boot/dts/Makefile index edbd32571e07..f091a4c39d73 100644 --- a/arch/arm/boot/dts/Makefile +++ b/arch/arm/boot/dts/Makefile @@ -7,9 +7,10 @@ dtb-$(CONFIG_MACH_ARTPEC6) += \ dtb-$(CONFIG_MACH_ASM9260) += \ alphascale-asm9260-devkit.dtb # Keep at91 dtb files sorted alphabetically for each SoC -dtb-$(CONFIG_SOC_SAM_V4_V5) += \ +dtb-$(CONFIG_SOC_AT91RM9200) += \ at91rm9200ek.dtb \
- mpa1600.dtb \
- mpa1600.dtb
+dtb-$(CONFIG_SOC_AT91SAM9) += \ animeo_ip.dtb \ at91-qil_a9260.dtb \ aks-cdu.dtb \