From: Frank Li <Frank.li@oss.nxp.com>
To: Billy Tsai <billy_tsai@aspeedtech.com>
Cc: Alexandre Belloni <alexandre.belloni@bootlin.com>,
Frank Li <Frank.Li@nxp.com>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>, Joel Stanley <joel@jms.id.au>,
Andrew Jeffery <andrew@codeconstruct.com.au>,
Philipp Zabel <p.zabel@pengutronix.de>,
Miquel Raynal <miquel.raynal@bootlin.com>,
Ryan Chen <ryan_chen@aspeedtech.com>,
tbevis@amazon.com, linux-i3c@lists.infradead.org,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-aspeed@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/9] dt-bindings: i3c: Document generic bus timing properties
Date: Wed, 11 Nov 2026 11:50:22 -0500 [thread overview]
Message-ID: <avSczhZGS9cCcNSu@lizhi-Precision-Tower-5810> (raw)
In-Reply-To: <20261111-b4-i3c-hci-ast2700-v2-1-4d8fff5c5196@aspeedtech.com>
On Wed, Nov 11, 2026 at 11:16:29AM +0800, Billy Tsai wrote:
> The push-pull and open-drain SCL periods, push-pull SDA output hold
> time, and the tCAS/tCBP periods around START and STOP conditions are
> normally derived from i3c-scl-hz, but board-level trace length,
> pull-up strength and capacitive loading can require different values
> than what that derivation produces for a given board.
>
> Document properties to override each of these independently, naming
> them after the MIPI I3C Basic Specification v1.1.1 timing parameters
> they adjust:
>
> - i3c-pp-scl-high-period-ns, i3c-pp-scl-low-period-ns
> tHIGH, tLOW: Table 87 (I3C Push-Pull Timing Parameters)
>
> - i3c-od-scl-high-period-ns, i3c-od-scl-low-period-ns
> tHIGH, tLOW_OD: Table 86 (I3C Open Drain Timing Parameters)
>
> - i3c-pp-sda-hold-ns
> tHD_PP: Table 87 (I3C Push-Pull Timing Parameters)
>
> - i3c-cas-period-ns, i3c-cbp-period-ns
> tCAS, tCBP: Table 86, Figures 144/145 (I3C Open Drain Timing
> Parameters). These carry the protocol minima as constraints.
>
> - i3c-sr-p-scl-low-period-ns
> The SCL low period held while a Controller stalls the clock in
> the T-Bit phase before a STOP or repeated START, per Section
> 5.1.2.5 "Controller Clock Stalling" (Figures 19 and 20). The
> specification describes this requirement qualitatively and does
> not assign it a dedicated timing symbol, unlike the other
> properties above.
>
> Any property left out keeps the derived default.
>
> Signed-off-by: Billy Tsai <billy_tsai@aspeedtech.com>
> ---
> Documentation/devicetree/bindings/i3c/i3c.yaml | 86 ++++++++++++++++++++++++++
> 1 file changed, 86 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/i3c/i3c.yaml b/Documentation/devicetree/bindings/i3c/i3c.yaml
> index 5603f2e7807d..30f65fd1afa7 100644
> --- a/Documentation/devicetree/bindings/i3c/i3c.yaml
> +++ b/Documentation/devicetree/bindings/i3c/i3c.yaml
> @@ -57,6 +57,82 @@ properties:
>
> May not be supported by all controllers.
>
> + i3c-pp-scl-high-period-ns:
> + description: |
Needn't |
> + Push-pull SCL high period override, in nanoseconds (tHIGH, MIPI
> + I3C Basic Specification v1.1.1 Table 87). When undefined, the
> + value is derived from i3c-scl-hz.
> +
> + May not be supported by all controllers.
Add
minimum:
maximum:
to restrict validate rang.
> +
...
> type: boolean
> description: |
> @@ -67,6 +143,16 @@ required:
> - "#address-cells"
> - "#size-cells"
>
> +dependencies:
> + i3c-pp-scl-high-period-ns:
> + - i3c-pp-scl-low-period-ns
> + i3c-pp-scl-low-period-ns:
> + - i3c-pp-scl-high-period-ns
> + i3c-od-scl-high-period-ns:
> + - i3c-od-scl-low-period-ns
> + i3c-od-scl-low-period-ns:
> + - i3c-od-scl-high-period-ns
> +
why need these dependencies? Suppose it should be default value if not
existing.
Frank
> patternProperties:
> "@[0-9a-f]+$":
> type: object
>
> --
> 2.34.1
>
next prev parent reply other threads:[~2026-11-11 16:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-11 3:16 [PATCH v2 0/9] i3c: mipi-i3c-hci: Add Aspeed AST2700 support Billy Tsai
2026-11-11 3:16 ` [PATCH v2 1/9] dt-bindings: i3c: Document generic bus timing properties Billy Tsai
2026-11-11 16:50 ` Frank Li [this message]
2026-11-11 3:16 ` [PATCH v2 2/9] dt-bindings: i3c: Document the AST2700 I3C controller Billy Tsai
2026-11-11 3:16 ` [PATCH v2 3/9] i3c: mipi-i3c-hci: Support address-indexed DAT slots Billy Tsai
2026-11-11 3:16 ` [PATCH v2 4/9] i3c: mipi-i3c-hci: Add a quirk for 64-bit DMA addressing Billy Tsai
2026-11-11 3:16 ` [PATCH v2 5/9] i3c: mipi-i3c-hci: Add a quirk to clear the TX start threshold Billy Tsai
2026-11-11 3:16 ` [PATCH v2 6/9] i3c: mipi-i3c-hci: Add support for the AST2700 I3C controller Billy Tsai
2026-11-11 17:11 ` Frank Li
2026-11-11 3:16 ` [PATCH v2 7/9] i3c: mipi-i3c-hci: Program AST2700 IBI termination threshold Billy Tsai
2026-11-11 17:21 ` Frank Li
2026-11-11 3:16 ` [PATCH v2 8/9] i3c: mipi-i3c-hci: Improve AST2700 PIO TX queue utilization Billy Tsai
2026-11-11 3:16 ` [PATCH v2 9/9] i3c: mipi-i3c-hci: Support the AST2700 internal pull-ups Billy Tsai
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=avSczhZGS9cCcNSu@lizhi-Precision-Tower-5810 \
--to=frank.li@oss.nxp.com \
--cc=Frank.Li@nxp.com \
--cc=alexandre.belloni@bootlin.com \
--cc=andrew@codeconstruct.com.au \
--cc=billy_tsai@aspeedtech.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=joel@jms.id.au \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-i3c@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miquel.raynal@bootlin.com \
--cc=p.zabel@pengutronix.de \
--cc=robh@kernel.org \
--cc=ryan_chen@aspeedtech.com \
--cc=tbevis@amazon.com \
/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
all inboxes | Powered by JetHome®