public inbox for linux-i3c@lists.infradead.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Stanley Chu <stanley.chuys@gmail.com>,
	alexandre.belloni@bootlin.com, robh@kernel.org,
	krzk+dt@kernel.org, linux-i3c@lists.infradead.org
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	openbmc@lists.ozlabs.org, tomer.maimon@nuvoton.com,
	kwliu@nuvoton.com, yschu@nuvoton.com, cpchiang1@nuvoton.com
Subject: Re: [PATCH v1 1/2] dt-bindings: i3c: Add NPCM845 i3c controller
Date: Thu, 1 Aug 2024 16:57:48 +0200	[thread overview]
Message-ID: <1590bd20-0140-4960-8af4-f1c1d55cda27@kernel.org> (raw)
In-Reply-To: <20240801071946.43266-2-yschu@nuvoton.com>

On 01/08/2024 09:19, Stanley Chu wrote:
> The npcm845 i3c devicetree binding follows the basic i3c bindings
> and add the properties for allowing to adjust the SDA/SCL timing
> to meet different requirements.
> 
> Signed-off-by: Stanley Chu <yschu@nuvoton.com>
> Signed-off-by: James Chiang <cpchiang1@nuvoton.com>

:
> +    description: |
> +      The i3c open drain frequency is 1MHz by default.
> +      If need to use different frequency, specify the clock high/low period directly.
> +      i3c-od-scl-hi-perios-ns specifies the high period ns of the SCL clock cycle in open drain mode.
> +      When i3c-od-scl-hi-period-ns and i3c-od-scl-lo-period-ns are specified, the i3c od frequency is
> +      decided by these two properties.
> +      i3c-od-scl-hi-period-ns should be equal to i3c-pp-scl-hi-period-ns or i3c-od-scl-lo-period-ns.
> +
> +  i3c-od-scl-lo-period-ns:
> +    description: |
> +      The low period ns of the SCL clock cycle in open drain mode. i3c-od-scl-lo-period-ns should be
> +      multiple of i3c-pp-scl-hi-period-ns.
> +
> +  enable-hj:

Missing vendor prefix.


Best regards,
Krzysztof


-- 
linux-i3c mailing list
linux-i3c@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-i3c

  parent reply	other threads:[~2024-08-01 14:57 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-01  7:19 [PATCH v1 0/2] Add Nuvoton NPCM845 i3c master driver Stanley Chu
2024-08-01  7:19 ` [PATCH v1 1/2] dt-bindings: i3c: Add NPCM845 i3c controller Stanley Chu
2024-08-01 14:53   ` Krzysztof Kozlowski
2024-08-01 23:06     ` Alexandre Belloni
2024-08-05  5:37       ` Stanley Chu
2024-08-05  6:04     ` Stanley Chu
2024-08-01 14:57   ` Krzysztof Kozlowski [this message]
2024-08-01  7:19 ` [PATCH v1 2/2] i3c: master: Add Nuvoton npcm845 i3c master driver Stanley Chu
2024-08-01  8:42   ` [PATCH " Markus Elfring
2024-08-01 15:02     ` Krzysztof Kozlowski
2024-08-01  9:06   ` Markus Elfring
2024-08-01 15:02   ` [PATCH v1 " Krzysztof Kozlowski
2024-08-05  6:27     ` Stanley Chu
2024-08-02 16:16   ` Frank Li
2024-08-05  7:19     ` Stanley Chu
2024-08-05 15:17       ` Frank Li
2024-08-06  0:47         ` Stanley Chu
2024-08-06  3:08           ` Frank Li
2024-08-02 21:53   ` kernel test robot
2024-08-02 23:25   ` kernel test robot
2024-08-03  2:12   ` kernel test robot

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=1590bd20-0140-4960-8af4-f1c1d55cda27@kernel.org \
    --to=krzk@kernel.org \
    --cc=alexandre.belloni@bootlin.com \
    --cc=cpchiang1@nuvoton.com \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=kwliu@nuvoton.com \
    --cc=linux-i3c@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=openbmc@lists.ozlabs.org \
    --cc=robh@kernel.org \
    --cc=stanley.chuys@gmail.com \
    --cc=tomer.maimon@nuvoton.com \
    --cc=yschu@nuvoton.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