Re: [PATCH v2 2/9] dt-bindings: i3c: Document the AST2700 I3C controller

From: Rob Herring (Arm)

Date: Thu Nov 19 2026 - 18:21:53 EST



On Wed, 11 Nov 2026 11:16:30 +0800, Billy Tsai wrote:
> The AST2700 I3C controller implements the MIPI I3C HCI programming
> model, extended with an ASPEED in-house control block and a PHY
> programming window advertised through an HCI vendor extended
> capability.
>
> The controller takes a core clock for PHY timing and two resets,
> named in reset-names as the controller's own reset and its DMA engine
> reset.
>
> Boards without external I3C pull-up resistors can use the PHY's
> built-in pull-ups instead, selected with bias-pull-up; the achievable
> strength set depends on which pin group backs the bus, since that
> fixes the pin voltage domain. Reuse bias-pull-up (pincfg-node.yaml)
> for the strength in Ohms; it is declared on this node rather than a
> pin-config node since the pull-up switch is part of the I3C PHY, not
> the broader SoC pin control IPs.
>
> Signed-off-by: Billy Tsai <billy_tsai@xxxxxxxxxxxxxx>
>
> ---
> We considered expressing bias-pull-up's dependency on a pinctrl state
> in the schema, but couldn't find a clean way to say "depends on
> whichever pinctrl-N is active" without hard-coding pinctrl-0
> specifically, which would be wrong in general (a node's active pin
> state doesn't have to sit at index 0). We've added pinctrl-0 to the
> example to illustrate the typical usage instead, without a formal
> schema-level dependency.
> ---
> .../bindings/i3c/aspeed,ast2700-i3c-hci.yaml | 89 ++++++++++++++++++++++
> 1 file changed, 89 insertions(+)
>

Reviewed-by: Rob Herring (Arm) <robh@xxxxxxxxxx>