From: Andrew Jeffery <andrew@codeconstruct.com.au>
To: Ryan Chen <ryan_chen@aspeedtech.com>, Rob Herring <robh@kernel.org>
Cc: Krzysztof Kozlowski <krzk@kernel.org>, Lee Jones <lee@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>, Joel Stanley <joel@jms.id.au>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>,
Philipp Zabel <p.zabel@pengutronix.de>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-aspeed@lists.ozlabs.org" <linux-aspeed@lists.ozlabs.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-clk@vger.kernel.org" <linux-clk@vger.kernel.org>
Subject: Re: [PATCH 1/4] dt-bindings: mfd: aspeed: support for AST2700
Date: Thu, 15 Aug 2024 09:56:02 +0930 [thread overview]
Message-ID: <7e1dc98e0f69a095a8f7725b742df3c8d8436a67.camel@codeconstruct.com.au> (raw)
In-Reply-To: <OS8PR06MB7541BB03AEE90B090AB990B3F2872@OS8PR06MB7541.apcprd06.prod.outlook.com>
On Wed, 2024-08-14 at 06:35 +0000, Ryan Chen wrote:
> > Subject: Re: [PATCH 1/4] dt-bindings: mfd: aspeed: support for
> > AST2700
> >
> > On Fri, Aug 09, 2024 at 06:10:22AM +0000, Ryan Chen wrote:
> > > > Subject: Re: [PATCH 1/4] dt-bindings: mfd: aspeed: support for
> > > > AST2700
> > > >
> > > > On 09/08/2024 07:55, Ryan Chen wrote:
> > > > > > Subject: Re: [PATCH 1/4] dt-bindings: mfd: aspeed: support
> > > > > > for
> > > > > > AST2700
> > > > > >
> > > > > > On 08/08/2024 09:59, Ryan Chen wrote:
> > > > > > > Add compatible support for AST2700 clk, reset, pinctrl,
> > > > > > > silicon-id and example for AST2700 scu.
> > > > > > >
> > > > > > > Signed-off-by: Ryan Chen <ryan_chen@aspeedtech.com>
> > > > > > > ---
> > > > > > > .../bindings/mfd/aspeed,ast2x00-scu.yaml | 31
> > > > > > +++++++++++++++++--
> > > > > > > 1 file changed, 29 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..c0965f08ae8c 100644
> > > > > > > ---
> > > > > > > a/Documentation/devicetree/bindings/mfd/aspeed,ast2x00-
> > > > > > > scu.yaml
> > > > > > > +++
> > > > > > > b/Documentation/devicetree/bindings/mfd/aspeed,ast2x00-
> > > > > > > scu.y
> > > > > > > +++ aml
> > > > > > > @@ -21,6 +21,8 @@ properties:
> > > > > > > - aspeed,ast2400-scu
> > > > > > > - aspeed,ast2500-scu
> > > > > > > - aspeed,ast2600-scu
> > > > > > > + - aspeed,ast2700-scu0
> > > > > > > + - aspeed,ast2700-scu1
> > > > > >
> > > > > > What are the differences between these two?
> > > > >
> > > > > The next [PATCH 4/4] is scu driver that include ast2700-scu0
> > > > > and
> > > > > ast2700-scu1 CLK_OF_DECLARE_DRIVER(ast2700_soc0,
> > > > > "aspeed,ast2700-scu0", ast2700_soc0_clk_init);
> > > > > CLK_OF_DECLARE_DRIVER(ast2700_soc1, "aspeed,ast2700-scu1",
> > > > > ast2700_soc1_clk_init);
> > > >
> > > > What are hardware differences? Entirely different devices?
> > >
> > > AST2700 have two soc die connected each other.
> > > Each soc die have it own scu, so the naming is ast2700-scu0 for
> > > soc0,
> > another is ast2700-scu1 for soc1.
> >
> > Didn't I see in another patch one die is cpu and one is io? Use
> > those in the
> > compatible rather than 0 and 1 if so.
> >
> Sorry, I want to align with our datasheet description.
> It will but scu0 and scu1 register setting.
Can we document that relationship in the binding? Rob's suggestion
seems more descriptive.
Andrew
next prev parent reply other threads:[~2024-08-15 0:26 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-08 7:59 [PATCH 0/4] Add support for AST2700 clk driver Ryan Chen
2024-08-08 7:59 ` [PATCH 1/4] dt-bindings: mfd: aspeed: support for AST2700 Ryan Chen
2024-08-08 10:14 ` Krzysztof Kozlowski
2024-08-09 5:55 ` Ryan Chen
2024-08-09 6:02 ` Krzysztof Kozlowski
2024-08-09 6:10 ` Ryan Chen
2024-08-12 6:26 ` Ryan Chen
2024-08-12 6:34 ` Krzysztof Kozlowski
2024-08-13 19:14 ` Rob Herring
2024-08-14 6:35 ` Ryan Chen
2024-08-15 0:26 ` Andrew Jeffery [this message]
2024-08-15 1:43 ` Ryan Chen
2024-08-15 1:56 ` Andrew Jeffery
2024-08-19 3:05 ` Ryan Chen
2024-08-20 0:46 ` Andrew Jeffery
2024-08-20 1:52 ` Ryan Chen
2024-08-20 5:01 ` Andrew Jeffery
2024-08-20 6:51 ` Ryan Chen
2024-08-08 7:59 ` [PATCH 2/4] dt-bindings: reset Add AST2700 reset bindings Ryan Chen
2024-08-08 8:35 ` Christophe JAILLET
2024-08-09 5:42 ` Ryan Chen
2024-08-09 6:07 ` Krzysztof Kozlowski
2024-08-09 6:12 ` Ryan Chen
2024-08-08 10:16 ` Krzysztof Kozlowski
2024-08-09 6:06 ` Ryan Chen
2024-08-09 6:08 ` Krzysztof Kozlowski
2024-08-08 7:59 ` [PATCH 3/4] dt-bindings: clock: Add AST2700 clock bindings Ryan Chen
2024-08-08 8:39 ` Christophe JAILLET
2024-08-09 5:47 ` Ryan Chen
2024-08-09 6:06 ` Krzysztof Kozlowski
2024-08-09 6:25 ` Ryan Chen
2024-08-09 7:31 ` Krzysztof Kozlowski
2024-08-12 7:26 ` Ryan Chen
2024-08-12 8:16 ` Krzysztof Kozlowski
2024-08-12 8:22 ` Ryan Chen
2024-08-12 8:30 ` Krzysztof Kozlowski
2024-08-12 8:54 ` Ryan Chen
2024-08-12 9:39 ` Ryan Chen
2024-08-12 9:54 ` Krzysztof Kozlowski
2024-08-13 1:53 ` Ryan Chen
2024-08-13 5:55 ` Krzysztof Kozlowski
2024-08-19 5:55 ` Ryan Chen
2024-08-19 6:01 ` Krzysztof Kozlowski
2024-08-19 6:42 ` Ryan Chen
2024-08-19 8:45 ` Krzysztof Kozlowski
2024-08-19 9:31 ` Ryan Chen
2024-08-08 10:17 ` Krzysztof Kozlowski
2024-08-08 7:59 ` [PATCH 4/4] " Ryan Chen
2024-08-08 10:18 ` Krzysztof Kozlowski
2024-08-19 5:57 ` Ryan Chen
2024-08-19 6:01 ` Krzysztof Kozlowski
2024-08-19 7:12 ` 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=7e1dc98e0f69a095a8f7725b742df3c8d8436a67.camel@codeconstruct.com.au \
--to=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=krzk@kernel.org \
--cc=lee@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).