From: Jeremy Kerr <jk@codeconstruct.com.au>
To: Joel Stanley <joel@jms.id.au>
Cc: linux-aspeed@lists.ozlabs.org, linux-clk@vger.kernel.org,
devicetree@vger.kernel.org,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Michael Turquette <mturquette@baylibre.com>,
Rob Herring <robh+dt@kernel.org>, Stephen Boyd <sboyd@kernel.org>,
Dylan Hung <dylan_hung@aspeedtech.com>,
Andrew Jeffery <andrew@aj.id.au>
Subject: Re: [PATCH v4 5/5] dt-bindings: clock: ast2600: Add reset config for I3C
Date: Wed, 01 Mar 2023 14:54:50 +0800 [thread overview]
Message-ID: <51803a244c28c53b5adb384effc09df1909dd1e8.camel@codeconstruct.com.au> (raw)
In-Reply-To: <CACPK8XfRg9vHYjC0rco4dr9pNY03vXTrmXaopOGBgdCq09LybQ@mail.gmail.com>
Hi Joel,
> > So I'm not sure what that comment is supposed to signify as to what
> > qualifies as a "gate" in the context of a reset...
>
> This is poor documentation from the author of the clock driver,
Hah, not that guy again!
> which is me.
oh.
> We only expose the reset lines in the device tree for resets that are
> not associated with a clock line.
>
> This is done because the aspeed docs specify we do a dance when
> enabling an IP:
>
> 1. Place IP in reset
> 2. Enable clock
> 3. Delay
> 4. Release reset
>
> So we do this with the aspeed_g6_gates array. The rule is: any gate
> with a number in the rst column doesn't have that reset line exposed.
> That's what this cryptic comment in the header is warning about.
That makes sense, and means I can drop the explicit reset control from
the DTS, and then we don't need these definitions.
> This was documented to some extent in the original commit message for
> the 2400/2500 driver:
>
> https://git.kernel.org/torvalds/c/15ed8ce5f84e2b
>
> We could hoist that out and put it in the source file(s).
Awesome, thanks for the explanation - I'll add a patch to do so.
Cheers,
Jeremy
prev parent reply other threads:[~2023-03-01 6:54 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-28 9:16 [PATCH v4 0/5] Add definitions for AST2600 i3c clocks and resets Jeremy Kerr
2023-02-28 9:16 ` [PATCH v4 1/5] clk: ast2600: allow empty entries in aspeed_g6_gates Jeremy Kerr
2023-03-01 0:50 ` Joel Stanley
2023-02-28 9:16 ` [PATCH v4 2/5] dt-bindings: clock: ast2600: Add top-level I3C clock Jeremy Kerr
2023-02-28 10:07 ` Krzysztof Kozlowski
2023-03-01 0:51 ` Joel Stanley
2023-02-28 9:16 ` [PATCH v4 3/5] clk: ast2600: Add full configs for I3C clocks Jeremy Kerr
2023-03-01 0:48 ` Joel Stanley
2023-03-01 0:58 ` Jeremy Kerr
2023-03-01 1:06 ` Joel Stanley
2023-03-01 8:17 ` Jeremy Kerr
2023-02-28 9:16 ` [PATCH v4 4/5] dt-bindings: clock: ast2600: remove IC36 & I3C7 clock definitions Jeremy Kerr
2023-03-01 0:48 ` Joel Stanley
2023-02-28 9:16 ` [PATCH v4 5/5] dt-bindings: clock: ast2600: Add reset config for I3C Jeremy Kerr
2023-03-01 0:49 ` Joel Stanley
2023-03-01 6:28 ` Jeremy Kerr
2023-03-01 6:48 ` Joel Stanley
2023-03-01 6:54 ` Jeremy Kerr [this message]
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=51803a244c28c53b5adb384effc09df1909dd1e8.camel@codeconstruct.com.au \
--to=jk@codeconstruct.com.au \
--cc=andrew@aj.id.au \
--cc=devicetree@vger.kernel.org \
--cc=dylan_hung@aspeedtech.com \
--cc=joel@jms.id.au \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-clk@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=robh+dt@kernel.org \
--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