From: Jeremy Kerr <jk@codeconstruct.com.au>
To: linux-aspeed@lists.ozlabs.org, linux-clk@vger.kernel.org
Cc: 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>,
Joel Stanley <joel@jms.id.au>, Andrew Jeffery <andrew@aj.id.au>
Subject: [PATCH v2 0/3] Add definitions for AST2600 i3c clocks and resets
Date: Mon, 13 Feb 2023 14:02:05 +0800 [thread overview]
Message-ID: <cover.1676267865.git.jk@codeconstruct.com.au> (raw)
This series adds some base configuration for the i3c controllers on
ast2600 hardware. We'll use the reset and clock definitions in the
proposed dt binding example, hence sending these first.
v2:
* based on feedback from Joel Stanley: avoid adding RESERVED clock
definitions, allowing empty entries in aspeed_g6_gates instead.
Jeremy Kerr (3):
clk: ast2600: allow empty entries in aspeed_g6_gates
clk: aspeed: Add full configs for i3c clocks
dts: ast2600: Add reset config for I3C
drivers/clk/clk-ast2600.c | 41 ++++++++++++++++++-----
include/dt-bindings/clock/ast2600-clock.h | 9 +++--
2 files changed, 40 insertions(+), 10 deletions(-)
--
2.39.1
next reply other threads:[~2023-02-13 6:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-13 6:02 Jeremy Kerr [this message]
2023-02-13 6:02 ` [PATCH v2 1/3] clk: ast2600: allow empty entries in aspeed_g6_gates Jeremy Kerr
2023-02-13 6:02 ` [PATCH v2 2/3] clk: aspeed: Add full configs for i3c clocks Jeremy Kerr
2023-02-13 8:44 ` Krzysztof Kozlowski
2023-02-13 9:48 ` Krzysztof Kozlowski
2023-02-13 12:34 ` Jeremy Kerr
2023-02-13 6:02 ` [PATCH v2 3/3] dts: ast2600: Add reset config for I3C Jeremy Kerr
2023-02-13 8:44 ` Krzysztof Kozlowski
2023-02-13 9:02 ` Jeremy Kerr
2023-02-13 9:06 ` Krzysztof Kozlowski
2023-02-13 9:23 ` Jeremy Kerr
2023-02-13 9:31 ` Krzysztof Kozlowski
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=cover.1676267865.git.jk@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;
as well as URLs for NNTP newsgroup(s).