-----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.kulikowski@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