From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Liu Peibao <liupeibao@loongson.cn>,
Thomas Gleixner <tglx@linutronix.de>,
Marc Zyngier <maz@kernel.org>, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Huacai Chen <chenhuacai@kernel.org>,
WANG Xuerui <kernel@xen0n.name>
Cc: Jianmin Lv <lvjianmin@loongson.cn>,
Yinbo Zhu <zhuyinbo@loongson.cn>,
linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] dt-bindings: interrupt-controller: add yaml for LoongArch CPU interrupt controller
Date: Mon, 7 Nov 2022 10:55:53 +0100 [thread overview]
Message-ID: <e92beaac-aa88-0336-cb30-7de438de67c9@linaro.org> (raw)
In-Reply-To: <196e80d8-f4fb-7393-81a5-bca757c805f5@loongson.cn>
On 07/11/2022 10:21, Liu Peibao wrote:
> On 11/7/22 4:28 PM, Krzysztof Kozlowski wrote:
>> On 07/11/2022 03:34, Liu Peibao wrote:
>>
>> Add commit msg explaining what you are doing here (e.g. the hardware).
>>
>
> I just add this yaml for what I did in patch 1/2 and the header seems enough
> to describe what I want to, so I did not add the commit log.
This should instead describe briefly the hardware here.
>
>>> Signed-off-by: Liu Peibao <liupeibao@loongson.cn>
>>> ---
>>> .../loongarch,cpu-interrupt-controller.yaml | 42 +++++++++++++++++++
>>> 1 file changed, 42 insertions(+)
>>> create mode 100644 Documentation/devicetree/bindings/interrupt-controller/loongarch,cpu-interrupt-controller.yaml
>>>
>>> diff --git a/Documentation/devicetree/bindings/interrupt-controller/loongarch,cpu-interrupt-controller.yaml b/Documentation/devicetree/bindings/interrupt-controller/loongarch,cpu-interrupt-controller.yaml
>>> new file mode 100644
>>> index 000000000000..30b742661a3f
>>> --- /dev/null
>>> +++ b/Documentation/devicetree/bindings/interrupt-controller/loongarch,cpu-interrupt-controller.yaml
>>> @@ -0,0 +1,42 @@
>>> +# SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
>>> +%YAML 1.2
>>> +---
>>> +$id: http://devicetree.org/schemas/interrupt-controller/loongarch,cpu-interrupt-controller.yaml#
>>> +$schema: http://devicetree.org/meta-schemas/core.yaml#
>>> +
>>> +title: LoongArch CPU Interrupt Controller
>>> +
>>> +description: >
>>> + On LoongArch the loongarch_cpu_irq_of_init() helper can be used to initialize
>>> + the 14 CPU IRQs from a devicetree file and create a irq_domain for this IRQ
>>> + controller.
>>> +
>>> + With the irq_domain in place we can describe how the 14 IRQs are wired to the
>>> + platforms internal interrupt controller cascade.
>>
>> This should be the description of hardware, not Linux drivers.
>>
>
> OK, I will remove this in the next version of this patch.
>
>>> +
>>> +maintainers:
>>> + - Liu Peibao <liupeibao@loongson.cn>
>>> +
>>> +properties:
>>> + compatible:
>>> + const: loongarch,cpu-interrupt-controller
>>
>> You have exactly one and only one type of CPU interrupt controller for
>> all your Loongarch designs? All current and all future? All?
>>
>
> It is sure of that "all current and recent designs". It is really hard to limit the
> design in the distant future.
>
> And if there is updating, maybe I will add additional things like this:
> "loongarch,cpu-interrupt-controller-2.0".
Unless you have a clear versioning of your hardware, adding 2.0 won't be
correct. Don't you have this for specific SoC?
Best regards,
Krzysztof
next prev parent reply other threads:[~2022-11-07 9:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-07 2:34 [PATCH 1/2] irqchip: loongarch-cpu: add DT support Liu Peibao
2022-11-07 2:34 ` [PATCH 2/2] dt-bindings: interrupt-controller: add yaml for LoongArch CPU interrupt controller Liu Peibao
2022-11-07 8:28 ` Krzysztof Kozlowski
2022-11-07 9:21 ` Liu Peibao
2022-11-07 9:55 ` Krzysztof Kozlowski [this message]
2022-11-07 11:20 ` Liu Peibao
2022-11-07 11:33 ` Krzysztof Kozlowski
2022-11-07 12:12 ` Liu Peibao
2022-11-07 7:04 ` [PATCH 1/2] irqchip: loongarch-cpu: add DT support 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=e92beaac-aa88-0336-cb30-7de438de67c9@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=chenhuacai@kernel.org \
--cc=kernel@xen0n.name \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=liupeibao@loongson.cn \
--cc=lvjianmin@loongson.cn \
--cc=maz@kernel.org \
--cc=robh+dt@kernel.org \
--cc=tglx@linutronix.de \
--cc=zhuyinbo@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
all inboxes | Powered by JetHome®