linux-kernel - Re: [PATCH] arm64: arch

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <4bbdfff6-8fba-0568-b243-5da9ee6e29b6@ti.com>
Date:   Wed, 1 Jul 2020 13:18:24 +0300
From:   Grygorii Strashko <grygorii.strashko@...com>
To:     Tero Kristo <t-kristo@...com>, Nishanth Menon <nm@...com>,
        Will Deacon <will@...nel.org>,
        Catalin Marinas <catalin.marinas@....com>
CC:     Santosh Shilimkar <ssantosh@...nel.org>,
        <linux-kernel@...r.kernel.org>,
        <linux-arm-kernel@...ts.infradead.org>,
        Dave Gerlach <d-gerlach@...com>,
        Peter Ujfalusi <peter.ujfalusi@...com>,
        Lokesh Vutla <lokeshvutla@...com>
Subject: Re: [PATCH] arm64: arch_k3: enable chipid driver

hi All,

On 19/06/2020 19:25, Grygorii Strashko wrote:
> Select TI chip id driver for TI's SoCs based on K3 architecture to provide
> this information to user space and Kernel as it is required by other
> drivers to determine SoC revision to function properly.
> 
> Signed-off-by: Grygorii Strashko <grygorii.strashko@...com>
> Reviewed-by: Lokesh Vutla <lokeshvutla@...com>
> ---
>   arch/arm64/Kconfig.platforms | 1 +
>   1 file changed, 1 insertion(+)
> 
> diff --git a/arch/arm64/Kconfig.platforms b/arch/arm64/Kconfig.platforms
> index 8dd05b2a925c..1d3710e3626a 100644
> --- a/arch/arm64/Kconfig.platforms
> +++ b/arch/arm64/Kconfig.platforms
> @@ -98,6 +98,7 @@ config ARCH_K3
>   	select TI_SCI_PROTOCOL
>   	select TI_SCI_INTR_IRQCHIP
>   	select TI_SCI_INTA_IRQCHIP
> +	select TI_K3_SOCINFO
>   	help
>   	  This enables support for Texas Instruments' K3 multicore SoC
>   	  architecture.
> 

Are there any comments?

The driver and dt changes were merged [1][2] and for adding new am654x SoC
revision SR2.0 we need this driver to be enabled always as other drivers are
going to use SOC Bus API intensively.

No dependencies.

[1] https://lore.kernel.org/lkml/20200512123449.16517-1-grygorii.strashko@ti.com/
[2] https://lore.kernel.org/lkml/20200613164346.28852-1-grygorii.strashko@ti.com/


-- 
Best regards,
grygorii