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 v3 1/4] dt-bindings: mfd: aspeed: support for AST2700
Date: Mon, 16 Sep 2024 12:08:50 +0200 [thread overview]
Message-ID: <9b356379-907c-4112-8e24-1810cfa40ef6@kernel.org> (raw)
In-Reply-To: <20240916091039.3584505-2-ryan_chen@aspeedtech.com>
On 16/09/2024 11:10, Ryan Chen wrote:
> Add compatible support for AST2700 clk, reset, pinctrl, silicon-id for AST2700 scu.
Please wrap commit message according to Linux coding style / submission
process (neither too early nor over the limit):
https://elixir.bootlin.com/linux/v6.4-rc1/source/Documentation/process/submitting-patches.rst#L597
>
> Signed-off-by: Ryan Chen <ryan_chen@aspeedtech.com>
> ---
> .../devicetree/bindings/mfd/aspeed,ast2x00-scu.yaml | 13 +++++++++++--
> 1 file changed, 11 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/mfd/aspeed,ast2x00-scu.yaml b/Documentation/devicetree/bindings/mfd/aspeed,ast2x00-scu.yaml
> index 86ee69c0f45b..127a357051cd 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,10 +34,12 @@ properties:
> ranges: true
>
> '#address-cells':
> - const: 1
> + minimum: 1
> + maximum: 2
>
> '#size-cells':
> - const: 1
> + minimum: 1
> + maximum: 2
Why do the children have 64 bit addressing?
>
> '#clock-cells':
> const: 1
> @@ -56,6 +62,8 @@ patternProperties:
> - aspeed,ast2400-pinctrl
> - aspeed,ast2500-pinctrl
> - aspeed,ast2600-pinctrl
> + - aspeed,ast2700-soc0-pinctrl
> + - aspeed,ast2700-soc1-pinctrl
Are these devices different?
Where is this binding documented (fully)? Provide link to lore patch in
the changelog.
>
> required:
> - compatible
> @@ -76,6 +84,7 @@ patternProperties:
> - aspeed,ast2400-silicon-id
> - aspeed,ast2500-silicon-id
> - aspeed,ast2600-silicon-id
> + - aspeed,ast2700-silicon-id
This one is fine.
> - const: aspeed,silicon-id
>
> reg:
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-09-16 10:08 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-16 9:10 [PATCH v3 0/4] Add support for AST2700 clk driver Ryan Chen
2024-09-16 9:10 ` [PATCH v3 1/4] dt-bindings: mfd: aspeed: support for AST2700 Ryan Chen
2024-09-16 10:08 ` Krzysztof Kozlowski [this message]
2024-09-19 6:05 ` Ryan Chen
2024-09-19 6:57 ` Krzysztof Kozlowski
2024-09-19 7:13 ` Ryan Chen
2024-09-19 10:32 ` Krzysztof Kozlowski
2024-09-20 7:33 ` Ryan Chen
2024-09-16 9:10 ` [PATCH v3 2/4] dt-bindings: Add AST2700 bindings Ryan Chen
2024-09-16 10:06 ` Krzysztof Kozlowski
2024-09-19 6:01 ` Ryan Chen
2024-09-19 6:58 ` Krzysztof Kozlowski
2024-09-19 7:15 ` Ryan Chen
2024-09-19 10:30 ` Krzysztof Kozlowski
2024-09-20 7:31 ` Ryan Chen
2024-09-16 9:10 ` [PATCH v3 3/4] reset: aspeed: register AST2700 reset auxiliary bus device Ryan Chen
2024-09-16 18:41 ` Christophe JAILLET
2024-09-23 2:50 ` Ryan Chen
2024-09-16 9:10 ` [PATCH v3 4/4] clk: aspeed: add AST2700 clock driver 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=9b356379-907c-4112-8e24-1810cfa40ef6@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;
as well as URLs for NNTP newsgroup(s).