From: Krzysztof Kozlowski <krzk@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>,
linux-i2c@vger.kernel.org, devicetree@vger.kernel.org,
loongarch@lists.linux.dev
Subject: Re: [PATCH v1 1/2] dt-bindings: i2c: ls2x-i2c: Add clock- related properties
Date: Thu, 26 Mar 2026 13:23:47 +0100 [thread overview]
Message-ID: <4516aba8-e776-41e1-ad26-c6f817b11b58@kernel.org> (raw)
In-Reply-To: <2d032399-d3fd-92b3-6dd4-28e0c78f199d@loongson.cn>
On 26/03/2026 12:48, Hongliang Wang wrote:
> Hi Krzysztof and Andi,
>
> Sorry, I didn't express myself clearly. The purpose of defining clock-input and
> clock-div properties is to use them in both acpi and dts. If these properties
> cannot be used in dts, can I first use them in acpi? and second, use clock
> framework in dts.
I already asked you:
1. Stop requesting read receipts on your email
2. Don't top post.
I already told you also why these cannot be in DTS. Respond to technical
arguments, not top-post of what you want.
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-03-26 12:23 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-25 1:18 [PATCH v2 0/2] i2c: ls2x: Add clock- related properties and parsing Hongliang Wang
2026-03-25 1:18 ` [PATCH v1 1/2] dt-bindings: i2c: ls2x-i2c: Add clock- related properties Hongliang Wang
2026-03-25 11:42 ` Krzysztof Kozlowski
2026-03-25 11:43 ` Krzysztof Kozlowski
2026-03-26 2:12 ` Hongliang Wang
2026-03-26 7:02 ` Krzysztof Kozlowski
2026-03-26 7:49 ` Krzysztof Kozlowski
2026-03-26 11:48 ` Hongliang Wang
2026-03-26 12:23 ` Krzysztof Kozlowski [this message]
2026-03-27 2:06 ` Hongliang Wang
2026-03-27 3:09 ` Hongliang Wang
2026-03-27 6:39 ` Krzysztof Kozlowski
2026-03-26 7:21 ` Andi Shyti
2026-03-27 2:08 ` Hongliang Wang
2026-03-25 1:18 ` [PATCH v1 2/2] i2c: ls2x: Add clock-input and clock-div properties parsing Hongliang Wang
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=4516aba8-e776-41e1-ad26-c6f817b11b58@kernel.org \
--to=krzk@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=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