From: "Diederik de Haas" <didi.debian@cknow.org>
To: "Detlev Casanova" <detlev.casanova@collabora.com>,
<linux-kernel@vger.kernel.org>
Cc: "Michael Turquette" <mturquette@baylibre.com>,
"Stephen Boyd" <sboyd@kernel.org>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Heiko Stuebner" <heiko@sntech.de>,
"Philipp Zabel" <p.zabel@pengutronix.de>,
"Elaine Zhang" <zhangqing@rock-chips.com>,
<linux-clk@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-rockchip@lists.infradead.org>, <kernel@collabora.com>,
"Sugar Zhang" <sugar.zhang@rock-chips.com>
Subject: Re: [PATCH v4 1/3] dt-bindings: reset: Add rk3576 reset definitions
Date: Fri, 09 Aug 2024 18:15:26 +0200 [thread overview]
Message-ID: <D3BIJXIKYD7N.238B8AE16Y5AI@cknow.org> (raw)
In-Reply-To: <20240809125553.3889-2-detlev.casanova@collabora.com>
On Fri Aug 9, 2024 at 2:54 PM CEST, Detlev Casanova wrote:
> Add reset ID defines for rk3576.
>
> Compared to the downstream bindings this uses continous gapless
> reset IDs starting at 1 instead of register offsets as IDs, as
> introduced in the RK3588 bindings.
> ...
> ---
> .../dt-bindings/reset/rockchip,rk3576-cru.h | 564 ++++++++++++++++++
> 1 file changed, 564 insertions(+)
> create mode 100644 include/dt-bindings/reset/rockchip,rk3576-cru.h
>
> diff --git a/include/dt-bindings/reset/rockchip,rk3576-cru.h b/include/dt-bindings/reset/rockchip,rk3576-cru.h
> new file mode 100644
> index 0000000000000..8c968af4888d5
> --- /dev/null
> +++ b/include/dt-bindings/reset/rockchip,rk3576-cru.h
> @@ -0,0 +1,564 @@
> +/* SPDX-License-Identifier: (GPL-2.0 OR MIT) */
> + ...
> +
> +#ifndef _DT_BINDINGS_RESET_ROCKCHIP_RK3576_H
> +#define _DT_BINDINGS_RESET_ROCKCHIP_RK3576_H
> +
> +#define SRST_A_TOP_BIU 0
> +#define SRST_P_TOP_BIU 1
As requested you renumbered starting from '0', but the commit message
mentions "starting at 1". Same for patch 2 of this series.
next prev parent reply other threads:[~2024-08-09 16:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-09 12:54 [PATCH v4 0/3] Add CRU support for rk3576 SoC Detlev Casanova
2024-08-09 12:54 ` [PATCH v4 1/3] dt-bindings: reset: Add rk3576 reset definitions Detlev Casanova
2024-08-09 14:15 ` Conor Dooley
2024-08-09 14:49 ` Detlev Casanova
2024-08-09 15:11 ` Conor Dooley
2024-08-09 16:15 ` Diederik de Haas [this message]
2024-08-10 12:29 ` Krzysztof Kozlowski
2024-08-09 12:54 ` [PATCH v4 2/3] dt-bindings: clock: Add rk3576 clock definitions and documentation Detlev Casanova
2024-08-09 14:14 ` Conor Dooley
2024-08-09 12:54 ` [PATCH v4 3/3] clk: rockchip: Add clock controller for the RK3576 Detlev Casanova
2024-08-13 7:30 ` zhangqing
2024-08-13 7:46 ` Shawn Lin
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=D3BIJXIKYD7N.238B8AE16Y5AI@cknow.org \
--to=didi.debian@cknow.org \
--cc=conor+dt@kernel.org \
--cc=detlev.casanova@collabora.com \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=kernel@collabora.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=mturquette@baylibre.com \
--cc=p.zabel@pengutronix.de \
--cc=robh@kernel.org \
--cc=sboyd@kernel.org \
--cc=sugar.zhang@rock-chips.com \
--cc=zhangqing@rock-chips.com \
/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