From: Rob Herring <robh@kernel.org>
To: Serge Semin <Sergey.Semin@baikalelectronics.ru>
Cc: Alexey Malahov <Alexey.Malahov@baikalelectronics.ru>,
Philipp Zabel <p.zabel@pengutronix.de>,
Serge Semin <fancer.lancer@gmail.com>,
Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
linux-kernel@vger.kernel.org,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Michael Turquette <mturquette@baylibre.com>,
Pavel Parkhomenko <Pavel.Parkhomenko@baikalelectronics.ru>,
linux-clk@vger.kernel.org, linux-mips@vger.kernel.org,
Stephen Boyd <sboyd@kernel.org>,
devicetree@vger.kernel.org,
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
Rob Herring <robh+dt@kernel.org>
Subject: Re: [PATCH RESEND v11 6/8] dt-bindings: clk: baikal-t1: Add DDR/PCIe reset IDs
Date: Tue, 13 Sep 2022 09:05:07 -0500 [thread overview]
Message-ID: <20220913140507.GA3590451-robh@kernel.org> (raw)
In-Reply-To: <20220909192616.16542-7-Sergey.Semin@baikalelectronics.ru>
On Fri, 09 Sep 2022 22:26:14 +0300, Serge Semin wrote:
> Aside with a set of the trigger-like resets Baikal-T1 CCU provides
> additional directly controlled reset signals for the DDR and PCIe
> controllers. As a preparation before adding these resets support to the
> kernel let's extent the Baikal-T1 CCU IDs list with the new IDs, which
> will be used to access the corresponding reset controls.
>
> Signed-off-by: Serge Semin <Sergey.Semin@baikalelectronics.ru>
> Reviewed-by: Philipp Zabel <p.zabel@pengutronix.de>
>
> ---
>
> Changelog v11:
> - This is a new patch created by detaching the DT-part from:
> [PATCH v10 6/7] clk: baikal-t1: Add DDR/PCIe directly controlled resets support
> (@Krzysztof)
> ---
> include/dt-bindings/reset/bt1-ccu.h | 9 +++++++++
> 1 file changed, 9 insertions(+)
>
Acked-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2022-09-13 14:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-09 19:26 [PATCH RESEND v11 0/8] clk/resets: baikal-t1: Add DDR/PCIe resets and xGMAC/SATA fixes Serge Semin
2022-09-09 19:26 ` [PATCH RESEND v11 1/8] clk: vc5: Fix 5P49V6901 outputs disabling when enabling FOD Serge Semin
2022-09-09 19:26 ` [PATCH RESEND v11 2/8] clk: baikal-t1: Fix invalid xGMAC PTP clock divider Serge Semin
2022-09-09 19:26 ` [PATCH RESEND v11 3/8] clk: baikal-t1: Add shared xGMAC ref/ptp clocks internal parent Serge Semin
2022-09-09 19:26 ` [PATCH RESEND v11 4/8] clk: baikal-t1: Add SATA internal ref clock buffer Serge Semin
2022-09-09 19:26 ` [PATCH RESEND v11 5/8] clk: baikal-t1: Move reset-controls code into a dedicated module Serge Semin
2022-09-09 19:26 ` [PATCH RESEND v11 6/8] dt-bindings: clk: baikal-t1: Add DDR/PCIe reset IDs Serge Semin
2022-09-13 14:05 ` Rob Herring [this message]
2022-09-09 19:26 ` [PATCH RESEND v11 7/8] clk: baikal-t1: Add DDR/PCIe directly controlled resets support Serge Semin
2022-09-09 19:26 ` [PATCH RESEND v11 8/8] 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=20220913140507.GA3590451-robh@kernel.org \
--to=robh@kernel.org \
--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=krzysztof.kozlowski@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=p.zabel@pengutronix.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.