From: Joel Stanley <joel@jms.id.au>
To: Jeremy Kerr <jk@codeconstruct.com.au>
Cc: linux-i3c@lists.infradead.org,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
Vitor Soares <ivitro@gmail.com>,
linux-aspeed@lists.ozlabs.org, devicetree@vger.kernel.org,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Dylan Hung <dylan_hung@aspeedtech.com>,
Andrew Jeffery <andrew@aj.id.au>
Subject: Re: [PATCH 0/4] i3c: Add support for ast2600 i3c controller
Date: Wed, 1 Mar 2023 01:04:15 +0000 [thread overview]
Message-ID: <CACPK8Xd0k8EKR1v4NVmgb6yp3Zh5hUyVyoxsyk0NTx9MF80oYQ@mail.gmail.com> (raw)
In-Reply-To: <cover.1676532146.git.jk@codeconstruct.com.au>
On Thu, 16 Feb 2023 at 07:42, Jeremy Kerr <jk@codeconstruct.com.au> wrote:
>
> The AST2600 SoC hardware includes a set of i3c controllers, based on the
> designware i3c core, plus some global registers for SoC integration.
>
> This series adds support for these i3c controllers, through the existing
> dw i3c master controller driver, by adding a set of platform-specific
> hooks to handle the global register configuration. This also gives us a
> way to add any future hardware-specific behaviours.
>
> We also need a DT binding to describe the ast2600-specific hardware.
> Since this involves new (mandatory) properties, I have added this as a
> separate binding rather than add a new compat string to the dw binding.
>
> The dt-binding example depends on a prior submission to the dt binding
> headers:
>
> https://lore.kernel.org/linux-devicetree/cover.1676294433.git.jk@codeconstruct.com.au/
>
> Full support for the global regmap will land with this queued mfd change:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/lee/mfd.git/commit/?id=cf2271843de835839e91c5c036492a87085af756
>
> Of course, any queries/comments/etc are most welcome.
Reviewed-by: Joel Stanley <joel@jms.id.au>
>
> Cheers,
>
>
> Jeremy
>
> Jeremy Kerr (4):
> dt-bindings: i3c: Add AST2600 i3c controller
> i3c: dw: Add platform operations
> i3c: dw: Add AST2600 platform ops
> i3c: dw: Add compatible string for ASPEED AST2600 BMC platform
>
> .../bindings/i3c/aspeed,ast2600-i3c.yaml | 73 ++++++++
> drivers/i3c/master/dw-i3c-master.c | 165 +++++++++++++++++-
> 2 files changed, 232 insertions(+), 6 deletions(-)
> create mode 100644 Documentation/devicetree/bindings/i3c/aspeed,ast2600-i3c.yaml
>
> --
> 2.39.1
>
--
linux-i3c mailing list
linux-i3c@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-i3c
prev parent reply other threads:[~2023-03-01 14:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-16 7:41 [PATCH 0/4] i3c: Add support for ast2600 i3c controller Jeremy Kerr
2023-02-16 7:41 ` [PATCH 1/4] dt-bindings: i3c: Add AST2600 " Jeremy Kerr
2023-02-16 8:24 ` Krzysztof Kozlowski
2023-02-16 13:58 ` Rob Herring
2023-02-16 7:41 ` [PATCH 2/4] i3c: dw: Add platform operations Jeremy Kerr
2023-02-16 15:04 ` Ben Dooks
2023-02-17 9:43 ` Jeremy Kerr
2023-02-16 7:41 ` [PATCH 3/4] i3c: dw: Add AST2600 platform ops Jeremy Kerr
2023-02-16 7:41 ` [PATCH 4/4] i3c: dw: Add compatible string for ASPEED AST2600 BMC platform Jeremy Kerr
2023-03-01 1:04 ` Joel Stanley [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=CACPK8Xd0k8EKR1v4NVmgb6yp3Zh5hUyVyoxsyk0NTx9MF80oYQ@mail.gmail.com \
--to=joel@jms.id.au \
--cc=alexandre.belloni@bootlin.com \
--cc=andrew@aj.id.au \
--cc=devicetree@vger.kernel.org \
--cc=dylan_hung@aspeedtech.com \
--cc=ivitro@gmail.com \
--cc=jk@codeconstruct.com.au \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-i3c@lists.infradead.org \
--cc=robh+dt@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).