From: Philipp Zabel <p.zabel@pengutronix.de>
To: Serge Semin <Sergey.Semin@baikalelectronics.ru>
Cc: Stephen Boyd <sboyd@kernel.org>,
Michael Turquette <mturquette@baylibre.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
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, devicetree@vger.kernel.org
Subject: Re: [PATCH v6 6/7] clk: baikal-t1: Add DDR/PCIe directly controlled resets support
Date: Mon, 11 Jul 2022 15:23:48 +0200 [thread overview]
Message-ID: <20220711132348.GB3771@pengutronix.de> (raw)
In-Reply-To: <20220708192725.9501-7-Sergey.Semin@baikalelectronics.ru>
On Fri, Jul 08, 2022 at 10:27:24PM +0300, Serge Semin wrote:
> Aside with a set of the trigger-like resets Baikal-T1 CCU provides two
> additional blocks with directly controlled reset signals. In particular it
> concerns DDR full and initial resets and various PCIe sub-domains resets.
> Let's add the direct reset assertion/de-assertion of the corresponding
> flags support into the Baikal-T1 CCU driver then. It will be required at
> least for the PCIe platform driver. Obviously the DDR controller isn't
> supposed to be fully reset in the kernel, so the corresponding controls
> are added just for the sake of the interface implementation completeness.
>
> Signed-off-by: Serge Semin <Sergey.Semin@baikalelectronics.ru>
>
> ---
>
> Changelog v6:
> - Refactor the code to support the linear reset IDs only. (@Philipp)
> ---
> drivers/clk/baikal-t1/ccu-rst.c | 67 +++++++++++++++++++++++++++++
> drivers/clk/baikal-t1/ccu-rst.h | 10 +++++
> include/dt-bindings/reset/bt1-ccu.h | 9 ++++
> 3 files changed, 86 insertions(+)
>
> diff --git a/drivers/clk/baikal-t1/ccu-rst.c b/drivers/clk/baikal-t1/ccu-rst.c
> index 8fd40810d24e..c20aa3e07afb 100644
> --- a/drivers/clk/baikal-t1/ccu-rst.c
> +++ b/drivers/clk/baikal-t1/ccu-rst.c
> @@ -35,18 +35,29 @@
> #define CCU_AXI_HWA_BASE 0x054
> #define CCU_AXI_SRAM_BASE 0x058
>
> +#define CCU_SYS_DDR_BASE 0x02c
> #define CCU_SYS_SATA_REF_BASE 0x060
> #define CCU_SYS_APB_BASE 0x064
> +#define CCU_SYS_PCIE_BASE 0x144
>
> #define CCU_RST_DELAY_US 1
>
> #define CCU_RST_TRIG(_base, _ofs) \
> { \
> + .type = CCU_RST_TRIG, \
> + .base = _base, \
> + .mask = BIT(_ofs), \
> + }
> +
> +#define CCU_RST_DIR(_base, _ofs) \
> + { \
> + .type = CCU_RST_DIR, \
> .base = _base, \
> .mask = BIT(_ofs), \
> }
>
> struct ccu_rst_info {
> + enum ccu_rst_type type;
> unsigned int base;
> unsigned int mask;
> };
> @@ -77,8 +88,18 @@ static const struct ccu_rst_info axi_rst_info[] = {
> * well while the Linux kernel is working.
> */
> static const struct ccu_rst_info sys_rst_info[] = {
> +
Please drop this empty line. Otherwise,
Reviewed-by: Philipp Zabel <p.zabel@pengutronix.de>
regards
Philipp
next prev parent reply other threads:[~2022-07-11 13:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-08 19:27 [PATCH v6 0/7] clk/resets: baikal-t1: Add DDR/PCIe resets and xGMAC/SATA fixes Serge Semin
2022-07-08 19:27 ` [PATCH v6 1/7] clk: vc5: Fix 5P49V6901 outputs disabling when enabling FOD Serge Semin
2022-07-08 19:27 ` [PATCH v6 2/7] clk: baikal-t1: Fix invalid xGMAC PTP clock divider Serge Semin
2022-07-08 19:27 ` [PATCH v6 3/7] clk: baikal-t1: Add shared xGMAC ref/ptp clocks internal parent Serge Semin
2022-07-08 19:27 ` [PATCH v6 4/7] clk: baikal-t1: Add SATA internal ref clock buffer Serge Semin
2022-07-08 19:27 ` [PATCH v6 5/7] clk: baikal-t1: Move reset-controls code into a dedicated module Serge Semin
2022-07-11 13:23 ` Philipp Zabel
2022-07-11 15:08 ` Serge Semin
2022-07-08 19:27 ` [PATCH v6 6/7] clk: baikal-t1: Add DDR/PCIe directly controlled resets support Serge Semin
2022-07-11 13:23 ` Philipp Zabel [this message]
2022-07-11 15:12 ` Serge Semin
2022-07-08 19:27 ` [PATCH v6 7/7] clk: baikal-t1: Convert to platform device driver 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=20220711132348.GB3771@pengutronix.de \
--to=p.zabel@pengutronix.de \
--cc=Alexey.Malahov@baikalelectronics.ru \
--cc=Pavel.Parkhomenko@baikalelectronics.ru \
--cc=Sergey.Semin@baikalelectronics.ru \
--cc=devicetree@vger.kernel.org \
--cc=fancer.lancer@gmail.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=robh+dt@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).