-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 09.02.2016 22:51, Jagan Teki wrote: > On 8 February 2016 at 02:27, Mateusz Kulikowski > <mateusz.kulikow...@gmail.com> wrote: [..] >> 8 files changed, 352 insertions(+) >> create mode 100644 arch/arm/mach-snapdragon/Kconfig >> create mode 100644 arch/arm/mach-snapdragon/Makefile >> create mode 100644 arch/arm/mach-snapdragon/clock-apq8016.c >> create mode 100644 arch/arm/mach-snapdragon/include/mach/gpio.h >> create mode 100644 arch/arm/mach-snapdragon/include/mach/sysmap-apq8016.h >> create mode 100644 arch/arm/mach-snapdragon/reset.c > > I think mach-qcom looks readable, I understand snapdragon is an soc > name but why can't we place all qcom soc code to mach-qcom (I think > Linux also doing the same)?
I know Linux has mach-qcom, also it was the first name I used, but IMO it's wrong. This is Snapdragon-only code - it will not work with, say, wireless SoCs (previously Atheros).. And it will be in-line with other mach-* in U-Boot: We have mach-exynos, not mach-samsung; mach-at91 not mach-atmel etc. Regards, Mateusz -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJWyDKlAAoJELvtohmVtQzB8UQH/jF/DWJSRiWvdBtvXDf0AGLy 6/2MMjhhDJDyz2C8zlwv5FlpVVggrNyX3NJoFoIuO7JAwECTnmYAiOj41AyRAYEW vVeoK+rX4nlD3flYv4UevW+Np0HxYVPyjRX2ONsqWj1u0798Wu5sF4m7H1QC24Pi iEFSTEdyNCVLaAqK2ELxL72OTiA3Xc+BQq9rvcHe8Q2wIEiAvP5F9LaWCl0z3dK8 ossNUA76d/YYfkczCgDeeY6xR6pdSizaxW7CsKdDaWFLgDQhZUzhJSgCWIGfgdgJ nY+lVVV3FbJy1Xwe6pgs6vyIqzhb0/9m9d4DTIVZFF+voLzKzE8dREseNzpx+TQ= =hT5h -----END PGP SIGNATURE----- _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
