From: Randy Dunlap <rdunlap@infradead.org>
To: Serge Semin <Sergey.Semin@baikalelectronics.ru>,
Stephen Boyd <sboyd@kernel.org>,
Philipp Zabel <p.zabel@pengutronix.de>,
Michael Turquette <mturquette@baylibre.com>
Cc: Serge Semin <fancer.lancer@gmail.com>,
Alexey Malahov <Alexey.Malahov@baikalelectronics.ru>,
Pavel Parkhomenko <Pavel.Parkhomenko@baikalelectronics.ru>,
Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
linux-clk@vger.kernel.org, linux-mips@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v7 5/7] clk: baikal-t1: Move reset-controls code into a dedicated module
Date: Mon, 11 Jul 2022 14:39:51 -0700 [thread overview]
Message-ID: <af5f882f-e7f8-ca49-020d-0dab3f2cc145@infradead.org> (raw)
In-Reply-To: <20220711154433.15415-6-Sergey.Semin@baikalelectronics.ru>
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
next prev parent reply other threads:[~2022-07-11 21:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-11 15:44 [PATCH v7 0/7] clk/resets: baikal-t1: Add DDR/PCIe resets and xGMAC/SATA fixes Serge Semin
2022-07-11 15:44 ` [PATCH v7 1/7] clk: vc5: Fix 5P49V6901 outputs disabling when enabling FOD Serge Semin
2022-07-11 15:44 ` [PATCH v7 2/7] clk: baikal-t1: Fix invalid xGMAC PTP clock divider Serge Semin
2022-07-11 15:44 ` [PATCH v7 3/7] clk: baikal-t1: Add shared xGMAC ref/ptp clocks internal parent Serge Semin
2022-07-11 15:44 ` [PATCH v7 4/7] clk: baikal-t1: Add SATA internal ref clock buffer Serge Semin
2022-07-11 15:44 ` [PATCH v7 5/7] clk: baikal-t1: Move reset-controls code into a dedicated module Serge Semin
2022-07-11 21:39 ` Randy Dunlap [this message]
2022-07-12 11:59 ` Serge Semin
2022-07-11 15:44 ` [PATCH v7 6/7] clk: baikal-t1: Add DDR/PCIe directly controlled resets support Serge Semin
2022-07-11 15:44 ` [PATCH v7 7/7] clk: baikal-t1: Convert to platform device driver Serge Semin
2022-07-11 15:49 ` [PATCH v7 0/7] clk/resets: baikal-t1: Add DDR/PCIe resets and xGMAC/SATA fixes Serge Semin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=af5f882f-e7f8-ca49-020d-0dab3f2cc145@infradead.org \
--to=rdunlap@infradead.org \
--cc=Alexey.Malahov@baikalelectronics.ru \
--cc=Pavel.Parkhomenko@baikalelectronics.ru \
--cc=Sergey.Semin@baikalelectronics.ru \
--cc=fancer.lancer@gmail.com \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=p.zabel@pengutronix.de \
--cc=sboyd@kernel.org \
--cc=tsbogend@alpha.franken.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®