From: Yixun Lan <dlan@gentoo.org>
To: Troy Mitchell <troymitchell988@gmail.com>
Cc: Andi Shyti <andi.shyti@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-riscv@lists.infradead.org, linux-i2c@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
spacemit@lists.linux.dev,
Conor Dooley <conor.dooley@microchip.com>
Subject: Re: [PATCH RESEND v5 1/2] dt-bindings: i2c: spacemit: add support for K1 SoC
Date: Mon, 3 Mar 2025 09:35:06 +0000 [thread overview]
Message-ID: <20250303093506-GYA58937@gentoo> (raw)
In-Reply-To: <20250303-k1-i2c-master-v5-1-21dfc7adfe37@gmail.com>
On 13:30 Mon 03 Mar , Troy Mitchell wrote:
> The I2C of K1 supports fast-speed-mode and high-speed-mode,
> and supports FIFO transmission.
>
> Reviewed-by: Conor Dooley <conor.dooley@microchip.com>
> Signed-off-by: Troy Mitchell <troymitchell988@gmail.com>
> ---
> .../devicetree/bindings/i2c/spacemit,k1-i2c.yaml | 59 ++++++++++++++++++++++
> 1 file changed, 59 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/i2c/spacemit,k1-i2c.yaml b/Documentation/devicetree/bindings/i2c/spacemit,k1-i2c.yaml
> new file mode 100644
> index 0000000000000000000000000000000000000000..db49f1f473e6f166f534b276c86b3951d86341c3
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/i2c/spacemit,k1-i2c.yaml
> @@ -0,0 +1,59 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/i2c/spacemit,k1-i2c.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: I2C controller embedded in SpacemiT's K1 SoC
> +
> +maintainers:
> + - Troy Mitchell <troymitchell988@gmail.com>
> +
> +properties:
> + compatible:
> + const: spacemit,k1-i2c
> +
> + reg:
> + maxItems: 1
> +
> + interrupts:
> + maxItems: 1
> +
..
> + clocks:
> + minItems: 2
> + maxItems: 2
> +
> + clock-names:
> + minItems: 2
> + maxItems: 2
I'd suggest to give a brief description and explicit clock name here,
you can consult marvell,mv64xxx-i2c.yaml for example
> +
> + clock-frequency:
> + description: |
> + K1 support three different modes which running different frequencies
> + standard speed mode: up to 100000 (100Hz)
> + fast speed mode : up to 400000 (400Hz)
> + high speed mode : up to 3300000 (3.3Mhz)
> + default: 400000
> + maximum: 3300000
> +
> +required:
> + - compatible
> + - reg
> + - interrupts
> + - clocks
> +
> +unevaluatedProperties: false
> +
> +examples:
> + - |
> + i2c@d4010800 {
> + compatible = "spacemit,k1-i2c";
> + reg = <0xd4010800 0x38>;
> + interrupt-parent = <&plic>;
> + interrupts = <36>;
> + clocks = <&ccu 176>, <&ccu 90>;
> + clock-names = "apb", "twsi";
9.1.4.61 TWSI0 CLOCK RESET CONTROL REGISTER(APBC_TWSI0_CLK_RST)
https://developer.spacemit.com/documentation?token=LCrKwWDasiJuROkVNusc2pWTnEb#part594
from above docs, there are two clocks
bit[1] - FNCLK, TWSI0 Functional Clock Enable/Disable
bit[0] - APBCLK, TWSI0 APB Bus Clock Enable/Disable
I'd suggest to name it according to the functionality, thus 'func', 'bus'
clock, not its source.. which would make it more system wide consistent
> + clock-frequency = <100000>;
> + };
> +
> +...
>
> --
> 2.34.1
>
--
Yixun Lan (dlan)
Gentoo Linux Developer
GPG Key ID AABEFD55
next prev parent reply other threads:[~2025-03-03 9:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-03 5:30 [PATCH RESEND v5 0/2] riscv: spacemit: add i2c support to K1 SoC Troy Mitchell
2025-03-03 5:30 ` [PATCH RESEND v5 1/2] dt-bindings: i2c: spacemit: add support for " Troy Mitchell
2025-03-03 9:35 ` Yixun Lan [this message]
2025-03-05 2:11 ` Samuel Holland
2025-03-05 3:05 ` Yixun Lan
2025-03-05 4:01 ` Samuel Holland
2025-03-05 14:10 ` Yixun Lan
2025-03-03 5:30 ` [PATCH RESEND v5 2/2] i2c: spacemit: add support for SpacemiT " Troy Mitchell
2025-03-03 6:08 ` Wolfram Sang
2025-03-03 7:11 ` Yao Zi
2025-03-03 7:34 ` Wolfram Sang
2025-03-04 0:01 ` Alex Elder
2025-03-06 13:16 ` Troy Mitchell
2025-03-06 20:30 ` Alex Elder
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=20250303093506-GYA58937@gentoo \
--to=dlan@gentoo.org \
--cc=andi.shyti@kernel.org \
--cc=conor+dt@kernel.org \
--cc=conor.dooley@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=robh@kernel.org \
--cc=spacemit@lists.linux.dev \
--cc=troymitchell988@gmail.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