From: Rob Herring <robh@kernel.org>
To: Jagan Teki <jagan@edgeble.ai>
Cc: Heiko Stuebner <heiko@sntech.de>,
linux-arm-kernel@lists.infradead.org,
Rob Herring <robh+dt@kernel.org>,
Kever Yang <kever.yang@rock-chips.com>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
linux-rockchip@lists.infradead.org, devicetree@vger.kernel.org,
Finley Xiao <finley.xiao@rock-chips.com>
Subject: Re: [PATCH v4 03/13] clk: rockchip: Add dt-binding header for RV1126
Date: Mon, 12 Sep 2022 15:56:14 -0500 [thread overview]
Message-ID: <20220912205614.GA1818666-robh@kernel.org> (raw)
In-Reply-To: <20220907160207.3845791-4-jagan@edgeble.ai>
On Wed, 07 Sep 2022 21:31:57 +0530, Jagan Teki wrote:
> Add the dt-bindings header for the Rockchip RV1126, that gets shared
> between the clock controller and the clock references in the dts.
>
> Signed-off-by: Finley Xiao <finley.xiao@rock-chips.com>
> Signed-off-by: Jagan Teki <jagan@edgeble.ai>
> ---
> Changes for v4:
> - update dual-license
> Changes for v3:
> - update the file name
> Changes for v2:
> - exclude from clk patch
>
> .../dt-bindings/clock/rockchip,rv1126-cru.h | 632 ++++++++++++++++++
> 1 file changed, 632 insertions(+)
> create mode 100644 include/dt-bindings/clock/rockchip,rv1126-cru.h
>
Acked-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2022-09-12 20:56 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-07 16:01 [PATCH v4 00/13] ARM: Add Rockchip RV1126 support Jagan Teki
2022-09-07 16:01 ` [PATCH v4 01/13] i2c: rk3x: Add rv1126 support Jagan Teki
2022-09-09 17:28 ` Heiko Stuebner
2022-09-12 19:22 ` Jagan Teki
2022-09-07 16:01 ` [PATCH v4 02/13] clk: rockchip: Add MUXTBL variant Jagan Teki
2022-09-07 16:01 ` [PATCH v4 03/13] clk: rockchip: Add dt-binding header for RV1126 Jagan Teki
2022-09-12 20:56 ` Rob Herring [this message]
2022-09-07 16:01 ` [PATCH v4 04/13] dt-bindings: clock: rockchip: Document RV1126 CRU Jagan Teki
2022-09-07 16:01 ` [PATCH v4 05/13] clk: rockchip: Add clock controller support for RV1126 SoC Jagan Teki
2022-09-13 10:13 ` Heiko Stuebner
2022-09-07 16:02 ` [PATCH v4 06/13] dt-bindings: soc: rockchip: Document RV1126 grf Jagan Teki
2022-09-07 16:02 ` [PATCH v4 07/13] dt-bindings: soc: rockchip: Document RV1126 pmugrf Jagan Teki
2022-09-07 16:02 ` [PATCH v4 08/13] ARM: dts: rockchip: Add Rockchip RV1126 pinctrl Jagan Teki
2022-09-07 16:02 ` [PATCH v4 09/13] ARM: dts: rockchip: Add Rockchip RV1126 SoC Jagan Teki
2022-09-07 16:02 ` [PATCH v4 10/13] dt-bindings: vendor-prefixes: Add Edgeble AI Technologies Pvt. Ltd Jagan Teki
2022-09-07 16:02 ` [PATCH v4 11/13] dt-bindings: arm: rockchip: Add Edgeble AI Edge Compute Module 0 Carrier Jagan Teki
2022-09-07 16:02 ` [PATCH v4 12/13] ARM: dts: rockchip: rv1126: Add Edgeble AI Edge Compute Module 0 Jagan Teki
2022-09-07 16:02 ` [PATCH v4 13/13] ARM: dts: rockchip: rv1126: Add Edgeble AI Edge Compute Module 0 Carrier Jagan Teki
2022-09-13 10:11 ` (subset) [PATCH v4 00/13] ARM: Add Rockchip RV1126 support Heiko Stuebner
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=20220912205614.GA1818666-robh@kernel.org \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=finley.xiao@rock-chips.com \
--cc=heiko@sntech.de \
--cc=jagan@edgeble.ai \
--cc=kever.yang@rock-chips.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=robh+dt@kernel.org \
/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).