linux-kernel - Re: [PATCH] arm64: Split out platform options to separate Kconfig

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20150715132014.GE20186@e104818-lin.cambridge.arm.com>
Date:	Wed, 15 Jul 2015 14:20:14 +0100
From:	Catalin Marinas <catalin.marinas@....com>
To:	Olof Johansson <olof@...om.net>
Cc:	will.deacon@....com, linux-kernel@...r.kernel.org,
	linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH] arm64: Split out platform options to separate Kconfig

On Wed, Jul 15, 2015 at 07:10:21AM -0400, Olof Johansson wrote:
> Let's move out the platform Kconfig entries to a separate file, since these
> changes usually get moved through arm-soc instead of the arm64 arch tree, and
> this will lead to fewer conflicts
> 
> Signed-off-by: Olof Johansson <olof@...om.net>
> ---
> 
> Will, Catalin, I'll merge this through arm-soc if I get your acks. Thanks!

That's fine by me.

Acked-by: Catalin Marinas <catalin.marinas@....com>

> +config ARCH_TEGRA
> +	bool "NVIDIA Tegra SoC Family"
> +	select ARCH_HAS_RESET_CONTROLLER
> +	select ARCH_REQUIRE_GPIOLIB
> +	select CLKDEV_LOOKUP
> +	select CLKSRC_MMIO
> +	select CLKSRC_OF
> +	select GENERIC_CLOCKEVENTS
> +	select HAVE_CLK
> +	select PINCTRL
> +	select RESET_CONTROLLER
> +	help
> +	  This enables support for the NVIDIA Tegra SoC family.
> +
> +config ARCH_TEGRA_132_SOC
> +	bool "NVIDIA Tegra132 SoC"
> +	depends on ARCH_TEGRA
> +	select PINCTRL_TEGRA124
> +	select USB_ULPI if USB_PHY
> +	select USB_ULPI_VIEWPORT if USB_PHY
> +	help
> +	  Enable support for NVIDIA Tegra132 SoC, based on the Denver
> +	  ARMv8 CPU.  The Tegra132 SoC is similar to the Tegra124 SoC,
> +	  but contains an NVIDIA Denver CPU complex in place of
> +	  Tegra124's "4+1" Cortex-A15 CPU complex.

Also, please make sure we won't get any more Kconfig entries for SoC
variations on arm64 (still waiting for the Tegra folk to remove
ARCH_TEGRA_132_SOC; this seems to be one of the very few SoCs that use
Makefile obj-y tricks to build clock, memory controller drivers instead
of dedicated driver Kconfig entries and they aren't even consistent:
PINCTRL_TEGRA124).

Thanks.

-- 
Catalin
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/