From: Krzysztof Kozlowski <krzk@kernel.org>
To: Ryan Chen <ryan_chen@aspeedtech.com>,
mturquette@baylibre.com, sboyd@kernel.org, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org, joel@jms.id.au,
andrew@codeconstruct.com.au, p.zabel@pengutronix.de,
linux-kernel@vger.kernel.org, linux-clk@vger.kernel.org,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-aspeed@lists.ozlabs.org
Subject: Re: [PATCH v4 1/3] dt-bindings: mfd: aspeed: support for AST2700
Date: Mon, 23 Sep 2024 11:09:38 +0200 [thread overview]
Message-ID: <c02f84d2-1306-480b-b6b3-15d3ccae16ad@kernel.org> (raw)
In-Reply-To: <20240923075012.2264573-2-ryan_chen@aspeedtech.com>
On 23/09/2024 09:50, Ryan Chen wrote:
> Add reset, clk dt bindings headers, and update compatible
> support for AST2700 clk, silicon-id in yaml.
>
> Signed-off-by: Ryan Chen <ryan_chen@aspeedtech.com>
> ---
> .../bindings/mfd/aspeed,ast2x00-scu.yaml | 8 +-
> .../dt-bindings/clock/aspeed,ast2700-scu.h | 163 ++++++++++++++++++
> .../dt-bindings/reset/aspeed,ast2700-scu.h | 124 +++++++++++++
> 3 files changed, 294 insertions(+), 1 deletion(-)
> create mode 100644 include/dt-bindings/clock/aspeed,ast2700-scu.h
> create mode 100644 include/dt-bindings/reset/aspeed,ast2700-scu.h
>
> diff --git a/Documentation/devicetree/bindings/mfd/aspeed,ast2x00-scu.yaml b/Documentation/devicetree/bindings/mfd/aspeed,ast2x00-scu.yaml
> index 86ee69c0f45b..c800d5e53b65 100644
> --- a/Documentation/devicetree/bindings/mfd/aspeed,ast2x00-scu.yaml
> +++ b/Documentation/devicetree/bindings/mfd/aspeed,ast2x00-scu.yaml
> @@ -9,6 +9,8 @@ title: Aspeed System Control Unit
> description:
> The Aspeed System Control Unit manages the global behaviour of the SoC,
> configuring elements such as clocks, pinmux, and reset.
> + In AST2700 SOC which has two soc connection, each soc have its own scu
> + register control, ast2700-scu0 for soc0, ast2700-scu1 for soc1.
>
> maintainers:
> - Joel Stanley <joel@jms.id.au>
> @@ -21,6 +23,8 @@ properties:
> - aspeed,ast2400-scu
> - aspeed,ast2500-scu
> - aspeed,ast2600-scu
> + - aspeed,ast2700-scu0
> + - aspeed,ast2700-scu1
> - const: syscon
> - const: simple-mfd
>
> @@ -30,7 +34,8 @@ properties:
> ranges: true
>
> '#address-cells':
> - const: 1
> + minimum: 1
> + maximum: 2
I would still argue that children do not need full 64-bit addressing,
but fine, you can grow their space as much as possible.
Reviewed-by: Krzysztof Kozlowski <krzk@kernel.org>
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-09-23 9:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-23 7:50 [PATCH v4 0/3] Add support for AST2700 clk driver Ryan Chen
2024-09-23 7:50 ` [PATCH v4 1/3] dt-bindings: mfd: aspeed: support for AST2700 Ryan Chen
2024-09-23 9:09 ` Krzysztof Kozlowski [this message]
2024-09-23 7:50 ` [PATCH v4 2/3] reset: aspeed: register AST2700 reset auxiliary bus device Ryan Chen
2024-09-25 13:45 ` Philipp Zabel
2024-09-26 2:43 ` Ryan Chen
2024-09-23 7:50 ` [PATCH v4 3/3] clk: aspeed: add AST2700 clock driver Ryan Chen
2024-09-30 2:04 ` Ryan Chen
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=c02f84d2-1306-480b-b6b3-15d3ccae16ad@kernel.org \
--to=krzk@kernel.org \
--cc=andrew@codeconstruct.com.au \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=joel@jms.id.au \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=p.zabel@pengutronix.de \
--cc=robh@kernel.org \
--cc=ryan_chen@aspeedtech.com \
--cc=sboyd@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