From: Binbin Zhou <zhoubb.aaron@gmail.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: Binbin Zhou <zhoubinbin@loongson.cn>,
Alessandro Zummo <a.zummo@towertech.it>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
Jiaxun Yang <jiaxun.yang@flygoat.com>,
Huacai Chen <chenhuacai@loongson.cn>,
WANG Xuerui <kernel@xen0n.name>,
linux-rtc@vger.kernel.org, linux-mips@vger.kernel.org,
loongarch@lists.linux.dev, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
devicetree@vger.kernel.org, Qing Zhang <zhangqing@loongson.cn>,
zhaoxiao <zhaoxiao@uniontech.com>,
keguang.zhang@gmail.com
Subject: Re: [PATCH V3 1/7] dt-bindings: rtc: Subdivision of LS2X RTC compatible
Date: Wed, 19 Apr 2023 15:12:34 +0800 [thread overview]
Message-ID: <CAMpQs4+XBQD9KB3XOPe4zp_vC5RxPaOZU0aJQZKTW=+9r5nmag@mail.gmail.com> (raw)
In-Reply-To: <b4b23751-a44c-2b38-0d55-a34711ad53c4@linaro.org>
On Mon, Apr 17, 2023 at 1:31 AM Krzysztof Kozlowski
<krzysztof.kozlowski@linaro.org> wrote:
>
> On 13/04/2023 09:57, Binbin Zhou wrote:
> > The LS2X RTC alarm depends on the associated registers in a separate
> > power management domain.
> >
> > In order to define the PM domain addresses of the different chips, a
> > more detailed description of compatible is required.
>
> This does not match your diff at all.
>
> >
> > Signed-off-by: Binbin Zhou <zhoubinbin@loongson.cn>
> > ---
> > Documentation/devicetree/bindings/rtc/trivial-rtc.yaml | 7 +++++--
> > 1 file changed, 5 insertions(+), 2 deletions(-)
> >
> > diff --git a/Documentation/devicetree/bindings/rtc/trivial-rtc.yaml b/Documentation/devicetree/bindings/rtc/trivial-rtc.yaml
> > index a3603e638c37..2928811b83a0 100644
> > --- a/Documentation/devicetree/bindings/rtc/trivial-rtc.yaml
> > +++ b/Documentation/devicetree/bindings/rtc/trivial-rtc.yaml
> > @@ -47,8 +47,11 @@ properties:
> > - isil,isl1218
> > # Intersil ISL12022 Real-time Clock
> > - isil,isl12022
> > - # Loongson-2K Socs/LS7A bridge Real-time Clock
> > - - loongson,ls2x-rtc
>
> Why removing it?
>
> > + # Loongson LS7A bridge Real-time Clock
> > + - loongson,ls7a-rtc
> > + # Loongson-2K Socs Real-time Clock
> > + - loongson,ls2k0500-rtc
> > + - loongson,ls2k1000-rtc
>
> That's even more surprising...
>
> I don't understand what you are doing here at all.
Hi Krzysztof:
Sorry, maybe my description was not accurate.
Looking back at my V2 patchset, the first patch was to add ls2x-rtc compatible.
(https://lore.kernel.org/linux-rtc/0288efeb4209e4a49af07de6399045aaa00a970c.1673227292.git.zhoubinbin@loongson.cn/)
In the process of modifying the V2 patchset, it was discovered that
the ACPI domain offset addresses on some of the socs (LS2K1000) were
different and I wanted to differentiate them by soc compatible. So I
was going to drop the ls2x-rtc compatible directly from the V3 patch
set.
However, when I rebased the V3 patchset, I found that the previous
ls2x-rtc compatible patch had been merged (commit 473a8ce756fd). So I
had to remove it and add soc compatible.
How about the following description:
Since commit 473a8ce756fd (dt-bindings: rtc: Add Loongson LS2X RTC
support), the ls2x-rtc compatible has been added. But the specific soc
compatible is needed to be used to define different ACPI domain offset
addresses.
Thanks.
Binbin
>
> Best regards,
> Krzysztof
>
>
next prev parent reply other threads:[~2023-04-19 7:12 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-13 7:57 [PATCH V3 0/7] rtc: ls2x: Add support for the Loongson-2K/LS7A RTC Binbin Zhou
2023-04-13 7:57 ` [PATCH V3 1/7] dt-bindings: rtc: Subdivision of LS2X RTC compatible Binbin Zhou
2023-04-16 17:31 ` Krzysztof Kozlowski
2023-04-19 7:12 ` Binbin Zhou [this message]
2023-04-19 8:52 ` Krzysztof Kozlowski
2023-04-19 9:38 ` Binbin Zhou
2023-04-13 7:57 ` [PATCH V3 2/7] rtc: Add support for the Loongson-2K/LS7A RTC Binbin Zhou
2023-04-13 18:35 ` kernel test robot
2023-04-16 19:49 ` Alexandre Belloni
2023-05-05 2:28 ` Binbin Zhou
2023-04-13 7:57 ` [PATCH V3 3/7] LoongArch: Enable LS2X RTC in loongson3_defconfig Binbin Zhou
2023-04-13 7:57 ` [PATCH V3 4/7] MIPS: Loongson64: DTS: Add RTC support to LS7A Binbin Zhou
2023-04-13 7:57 ` [PATCH V3 5/7] MIPS: Loongson: Enable LS2X RTC in loongson3_defconfig Binbin Zhou
2023-04-13 7:58 ` [PATCH V3 6/7] MIPS: Loongson64: DTS: Add RTC support to Loongson-2K Binbin Zhou
2023-04-13 7:58 ` [PATCH V3 7/7] MIPS: Loongson: Enable LS2X RTC in loongson2k_defconfig Binbin Zhou
2023-04-16 17:33 ` Krzysztof Kozlowski
2023-04-16 19:51 ` [PATCH V3 0/7] rtc: ls2x: Add support for the Loongson-2K/LS7A RTC Alexandre Belloni
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='CAMpQs4+XBQD9KB3XOPe4zp_vC5RxPaOZU0aJQZKTW=+9r5nmag@mail.gmail.com' \
--to=zhoubb.aaron@gmail.com \
--cc=a.zummo@towertech.it \
--cc=alexandre.belloni@bootlin.com \
--cc=chenhuacai@loongson.cn \
--cc=devicetree@vger.kernel.org \
--cc=jiaxun.yang@flygoat.com \
--cc=keguang.zhang@gmail.com \
--cc=kernel@xen0n.name \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux-rtc@vger.kernel.org \
--cc=loongarch@lists.linux.dev \
--cc=robh+dt@kernel.org \
--cc=tsbogend@alpha.franken.de \
--cc=zhangqing@loongson.cn \
--cc=zhaoxiao@uniontech.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;
as well as URLs for NNTP newsgroup(s).