From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Binbin Zhou <zhoubb.aaron@gmail.com>
Cc: Binbin Zhou <zhoubinbin@loongson.cn>,
Huacai Chen <chenhuacai@kernel.org>,
Jiaxun Yang <jiaxun.yang@flygoat.com>,
Thomas Gleixner <tglx@linutronix.de>,
Marc Zyngier <maz@kernel.org>, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Jianmin Lv <lvjianmin@loongson.cn>,
Huacai Chen <chenhuacai@loongson.cn>,
linux-kernel@vger.kernel.org, linux-mips@vger.kernel.org,
loongarch@lists.linux.dev, devicetree@vger.kernel.org,
loongson-kernel@lists.loongnix.cn
Subject: Re: [PATCH V2 1/2] dt-bindings: interrupt-controller: Add Loongson EIOINTC
Date: Fri, 17 Feb 2023 09:40:50 +0100 [thread overview]
Message-ID: <4dcaaa70-11e0-fc9d-da03-224d34e36983@linaro.org> (raw)
In-Reply-To: <CAMpQs4KennWg60ccQ5NYOs=5a9gqTk_bKY26noQ3u0qLQSBg_w@mail.gmail.com>
On 17/02/2023 07:09, Binbin Zhou wrote:
>>> Hi Krzysztof:
>>>
>>> Allow me to give a brief overview of the current status of eiointc (DT-based):
>>> Loongson-3A series supports eiointc;
>>> Loongson-2K1000 does not support eiointc now;
>>> Loongson-2K0500 supports eiointc, with differences from
>>> Loongson-3, e.g. only up to 128 devices are supported;
>>> Loongson-2K2000 supports eiointc, similar to Loongson-3.
>>> ....
>>>
>>> As can be seen, there is now a bit of confusion in the chip's design of eiointc.
>>>
>>> The design of eiointc is probably refined step by step with the chip.
>>> The same version of eiointc can be used for multiple chips, and the
>>> same chip series may also use different versions of eiointc. Low-end
>>> chips may use eiointc-2.0, and high-end chips may use eiointc-1.0,
>>> depending on the time it's produced.
>>>
>>> So in the Loongson-2K series I have defined the current state as
>>> eiointc-1.0, using the dts property to indicate the maximum number of
>>> devices supported by eiointc that can be used directly in the driver.
>>>
>>> If there are new changes to the design later on, such as the
>>> definition of registers, we can call it eiointc-2.0, which can also
>>> cover more than one chip.
>>
>> Just go with SoC-based compatibles. If your version is not specific
>> enough, then it is not a good way to represent the hardware.
>>
>
> Hi Krzysztof:
>
> I have tried to write the following SoC-based compatibles, is it fine?
>
> compatible:
> enum:
> - loongson,ls3a-eiointc # For MIPS Loongson-3A if necessary.
> - loongson,ls2k0500-eiointc
> - loongson,ls2k200-eiointc
Looks good, but didn't you state these are compatible between each
other? I have impression there is a common set, so maybe one compatible
work on other device with reduced number of devices?
Best regards,
Krzysztof
next prev parent reply other threads:[~2023-02-17 8:40 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-13 12:15 [PATCH V2 0/2] Loongson: irqchip: Add loongson-eiointc DT init support Binbin Zhou
2023-02-13 12:15 ` [PATCH V2 1/2] dt-bindings: interrupt-controller: Add Loongson EIOINTC Binbin Zhou
2023-02-14 9:52 ` Krzysztof Kozlowski
2023-02-14 12:40 ` Binbin Zhou
2023-02-14 12:43 ` Krzysztof Kozlowski
2023-02-15 20:12 ` Krzysztof Kozlowski
2023-02-16 1:46 ` Binbin Zhou
2023-02-16 8:10 ` Krzysztof Kozlowski
2023-02-16 9:30 ` Huacai Chen
2023-02-16 9:34 ` Krzysztof Kozlowski
2023-02-17 6:09 ` Binbin Zhou
2023-02-17 8:40 ` Krzysztof Kozlowski [this message]
2023-02-17 10:12 ` Binbin Zhou
2023-02-21 11:18 ` Krzysztof Kozlowski
2023-02-15 19:49 ` Rob Herring
2023-02-13 12:15 ` [PATCH V2 2/2] irqchip/loongson-eiointc: Add DT init support Binbin Zhou
2023-02-13 14:28 ` [PATCH V2 0/2] Loongson: irqchip: Add loongson-eiointc " Huacai Chen
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=4dcaaa70-11e0-fc9d-da03-224d34e36983@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=chenhuacai@kernel.org \
--cc=chenhuacai@loongson.cn \
--cc=devicetree@vger.kernel.org \
--cc=jiaxun.yang@flygoat.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=loongarch@lists.linux.dev \
--cc=loongson-kernel@lists.loongnix.cn \
--cc=lvjianmin@loongson.cn \
--cc=maz@kernel.org \
--cc=robh+dt@kernel.org \
--cc=tglx@linutronix.de \
--cc=zhoubb.aaron@gmail.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).