LoongArch architecture development
 help / color / mirror / Atom feed
From: Conor Dooley <conor@kernel.org>
To: Hongliang Wang <wanghongliang@loongson.cn>
Cc: Binbin Zhou <zhoubinbin@loongson.cn>,
	Andi Shyti <andi.shyti@kernel.org>, Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Wolfram Sang <wsa+renesas@sang-engineering.com>,
	linux-i2c@vger.kernel.org, devicetree@vger.kernel.org,
	loongarch@lists.linux.dev
Subject: Re: [PATCH v2] dt-bindings: i2c: ls2x-i2c: Add clocks and clock-frequency properties
Date: Fri, 8 May 2026 15:56:29 +0100	[thread overview]
Message-ID: <20260508-jury-eclipse-9190a84cfa7e@spud> (raw)
In-Reply-To: <84c37ac1-3a9c-b0d2-f86a-90712b45b806@loongson.cn>

[-- Attachment #1: Type: text/plain, Size: 2500 bytes --]

On Fri, May 08, 2026 at 09:29:08AM +0800, Hongliang Wang wrote:
> 
> On 2026/5/8 上午1:29, Conor Dooley wrote:
> > On Thu, May 07, 2026 at 04:10:09PM +0800, Hongliang Wang wrote:
> > > From: wanghongliang <wanghongliang@loongson.cn>
> > > 
> > > clocks property describes the i2c bus reference clock from APB clock.
> > > clock-frequency property describes i2c bus speed.
> > > 
> > > Signed-off-by: wanghongliang <wanghongliang@loongson.cn>
> > > ---
> > >   Documentation/devicetree/bindings/i2c/loongson,ls2x-i2c.yaml | 3 +++
> > >   1 file changed, 3 insertions(+)
> > > 
> > > diff --git a/Documentation/devicetree/bindings/i2c/loongson,ls2x-i2c.yaml b/Documentation/devicetree/bindings/i2c/loongson,ls2x-i2c.yaml
> > > index ee09c6d9c5f0..4bf89bb97e7d 100644
> > > --- a/Documentation/devicetree/bindings/i2c/loongson,ls2x-i2c.yaml
> > > +++ b/Documentation/devicetree/bindings/i2c/loongson,ls2x-i2c.yaml
> > > @@ -38,10 +38,13 @@ unevaluatedProperties: false
> > >   examples:
> > >     - |
> > >       #include <dt-bindings/interrupt-controller/irq.h>
> > > +    #include <dt-bindings/clock/loongson,ls2k-clk.h>
> > >       i2c0: i2c@1fe21000 {
> > >           compatible = "loongson,ls2k-i2c";
> > >           reg = <0x1fe21000 0x8>;
> > > +        clock-frequency = <100000>;
> > > +        clocks = <&clk LOONGSON2_APB_CLK>;
> > /stuff/linux-dt/Documentation/devicetree/bindings/i2c/loongson,ls2x-i2c.example.dtb: i2c@1fe21000 (loongson,ls2k-i2c): Unevaluated properties are not allowed ('clocks' was unexpected)
> > 	from schema $id: http://devicetree.org/schemas/i2c/loongson,ls2x-i2c.yaml
> > 
> > 
> > Please test your patches before sending them.
> The error is becasue there is no clocks property in loongson,ls2x-i2c.yaml.
> The patch is based on the following repository and uses the i2c-host-next
> branch.
> I found the clocks property already exist in loongson,ls2x-i2c.yaml, so I
> didn't
> add it in my patch
> 
> git://git.kernel.org/pub/scm/linux/kernel/git/andi.shyti/linux.git

Ah, my bad then.

Acked-by: Conor Dooley <conor.dooley@microchip.com>
pw-bot: not-applicable

> > 
> > Does this device actually have a clock or not?
> Yes,  the clock actually exists.
> > 
> > Cheers,
> > Conor.
> > 
> > >           interrupt-parent = <&extioiic>;
> > >           interrupts = <22 IRQ_TYPE_LEVEL_LOW>;
> > >           #address-cells = <1>;
> > > -- 
> > > 2.47.2
> > > 
> Best regards,
> Hongliang Wang
> 
> 

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

      reply	other threads:[~2026-05-08 14:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-07  8:10 [PATCH v2] dt-bindings: i2c: ls2x-i2c: Add clocks and clock-frequency properties Hongliang Wang
2026-05-07  8:10 ` [PATCH v2] i2c: ls2x: Add clocks property parsing and adjust bus speed Hongliang Wang
2026-05-08  3:06   ` Huacai Chen
2026-05-09  3:06     ` Hongliang Wang
2026-05-07 17:29 ` [PATCH v2] dt-bindings: i2c: ls2x-i2c: Add clocks and clock-frequency properties Conor Dooley
2026-05-08  1:29   ` Hongliang Wang
2026-05-08 14:56     ` Conor Dooley [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=20260508-jury-eclipse-9190a84cfa7e@spud \
    --to=conor@kernel.org \
    --cc=andi.shyti@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=loongarch@lists.linux.dev \
    --cc=robh@kernel.org \
    --cc=wanghongliang@loongson.cn \
    --cc=wsa+renesas@sang-engineering.com \
    --cc=zhoubinbin@loongson.cn \
    /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