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]
Date:   Mon, 11 Jul 2022 14:39:51 -0700
From:   Randy Dunlap <rdunlap@...radead.org>
To:     Serge Semin <Sergey.Semin@...kalelectronics.ru>,
        Stephen Boyd <sboyd@...nel.org>,
        Philipp Zabel <p.zabel@...gutronix.de>,
        Michael Turquette <mturquette@...libre.com>
Cc:     Serge Semin <fancer.lancer@...il.com>,
        Alexey Malahov <Alexey.Malahov@...kalelectronics.ru>,
        Pavel Parkhomenko <Pavel.Parkhomenko@...kalelectronics.ru>,
        Thomas Bogendoerfer <tsbogend@...ha.franken.de>,
        linux-clk@...r.kernel.org, linux-mips@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH v7 5/7] clk: baikal-t1: Move reset-controls code into a
 dedicated module



On 7/11/22 08:44, Serge Semin wrote:
> diff --git a/drivers/clk/baikal-t1/Kconfig b/drivers/clk/baikal-t1/Kconfig
> index 03102f1094bc..56a4ff1d8bf0 100644
> --- a/drivers/clk/baikal-t1/Kconfig
> +++ b/drivers/clk/baikal-t1/Kconfig
> @@ -29,7 +29,6 @@ config CLK_BT1_CCU_PLL
>  
>  config CLK_BT1_CCU_DIV
>  	bool "Baikal-T1 CCU Dividers support"
> -	select RESET_CONTROLLER
>  	select MFD_SYSCON
>  	default MIPS_BAIKAL_T1
>  	help
> @@ -39,4 +38,15 @@ config CLK_BT1_CCU_DIV
>  	  either gateable or ungateable. Some of the CCU dividers can be as well
>  	  used to reset the domains they're supplying clock to.
>  
> +config CLK_BT1_CCU_RST
> +	bool "Baikal-T1 CCU Resets support"
> +	select RESET_CONTROLLER
> +	select MFD_SYSCON
> +	default MIPS_BAIKAL_T1
> +	help
> +	  Enable this to support the CCU reset blocks responsible for the
> +	  AXI-bus and some subsystems reset. These are mainly the
> +	  sef-deasserted reset controls but there are several lines which

	  self-deasserted
?

> +	  can be directly asserted/de-asserted (PCIe and DDR sub-domains).

-- 
~Randy

Powered by blists - more mailing lists