On Wed, Feb 22, 2017 at 05:22:17PM -0600, Andrew F. Davis wrote: > Hi all, > > The HS and non-HS versions of TI boards are very similar but > currently need separate defconfigs, these should be almost > identical outside of the security additions. When they > track out of sync it is normally not a problem, but a couple > of these changes are now important and so lets sync them up. > > Thanks, > Andrew > > Andrew F. Davis (3): > defconfigs: am43xx_hs_evm: Sync HS and non-HS defconfigs > defconfigs: am57xx_hs_evm: Sync HS and non-HS defconfigs > defconfigs: dra7xx_hs_evm: Sync HS and non-HS defconfigs > > configs/am43xx_hs_evm_defconfig | 4 +++- > configs/am57xx_hs_evm_defconfig | 7 +++++++ > configs/dra7xx_hs_evm_defconfig | 1 + > 3 files changed, 11 insertions(+), 1 deletion(-)
This feels like another area where we need to be implying things in arch/arm/mach-omap2/am33xx/Kconfig or arch/arm/Kconfig, depending on if it's board feature or SoC feature. And some of the DM_xxx we should be select'ing as it then comes down to imply'ing the driver that makes use of the framework as we should be discarding the unused framework at link time if there's no driver to it. Thanks! -- Tom
signature.asc
Description: Digital signature
_______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
