From: Kunihiko Hayashi <hayashi.kunihiko@socionext.com>
To: Rob Herring <robh@kernel.org>,
Bjorn Helgaas <bhelgaas@google.com>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Masami Hiramatsu <mhiramat@kernel.org>
Cc: linux-pci@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: PCI: socionext,uniphier-pcie: Add missing child interrupt controller
Date: Thu, 26 May 2022 18:01:49 +0900 [thread overview]
Message-ID: <35c700f6-ce67-89d5-0f29-426acd33efa9@socionext.com> (raw)
In-Reply-To: <20220525210117.2489333-1-robh@kernel.org>
Hi Rob,
On 2022/05/26 6:01, Rob Herring wrote:
> The Socionext interrupt controller internal to the the PCI block isn't
> documented which causes warnings when unevaluatedProperties check is
> also fixed. Add the 'interrupt-controller' child node and properties and
> fixup the example so that interrupt properties can be parsed.
Surely internal interrupt controller isn't described, and should be documented.
And the child node name "legacy-interrupt-controller" also should be fixed.
Reviewed-by: Kunihiko Hayashi <hayashi.kunihiko@socionext.com>
BTW I can't reproduce such warnings with my environment.
Can you show the command line to reproduce the warnings?
Thank you,
>
> Signed-off-by: Rob Herring <robh@kernel.org>
> ---
> .../bindings/pci/socionext,uniphier-pcie.yaml | 23 ++++++++++++++++++-
> 1 file changed, 22 insertions(+), 1 deletion(-)
>
> diff --git
> a/Documentation/devicetree/bindings/pci/socionext,uniphier-pcie.yaml
> b/Documentation/devicetree/bindings/pci/socionext,uniphier-pcie.yaml
> index f5926d0fb085..638b99db0433 100644
> --- a/Documentation/devicetree/bindings/pci/socionext,uniphier-pcie.yaml
> +++ b/Documentation/devicetree/bindings/pci/socionext,uniphier-pcie.yaml
> @@ -51,6 +51,19 @@ properties:
> phy-names:
> const: pcie-phy
>
> + interrupt-controller:
> + type: object
> + additionalProperties: false
> +
> + properties:
> + interrupt-controller: true
> +
> + '#interrupt-cells':
> + const: 1
> +
> + interrupts:
> + maxItems: 1
> +
> required:
> - compatible
> - reg
> @@ -62,6 +75,13 @@ unevaluatedProperties: false
>
> examples:
> - |
> + bus {
> + gic: interrupt-controller {
> + interrupt-controller;
> + #interrupt-cells = <3>;
> + };
> + };
> +
> pcie: pcie@66000000 {
> compatible = "socionext,uniphier-pcie";
> reg-names = "dbi", "link", "config";
> @@ -80,6 +100,7 @@ examples:
> phys = <&pcie_phy>;
> #interrupt-cells = <1>;
> interrupt-names = "dma", "msi";
> + interrupt-parent = <&gic>;
> interrupts = <0 224 4>, <0 225 4>;
> interrupt-map-mask = <0 0 0 7>;
> interrupt-map = <0 0 0 1 &pcie_intc 0>,
> @@ -87,7 +108,7 @@ examples:
> <0 0 0 3 &pcie_intc 2>,
> <0 0 0 4 &pcie_intc 3>;
>
> - pcie_intc: legacy-interrupt-controller {
> + pcie_intc: interrupt-controller {
> interrupt-controller;
> #interrupt-cells = <1>;
> interrupt-parent = <&gic>;
>
---
Best Regards
Kunihiko Hayashi
next prev parent reply other threads:[~2022-05-26 9:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-25 21:01 Rob Herring
2022-05-26 9:01 ` Kunihiko Hayashi [this message]
2022-05-26 12:46 ` Rob Herring
2022-05-27 9:27 ` Kunihiko Hayashi
2022-05-31 15:19 ` Rob Herring
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=35c700f6-ce67-89d5-0f29-426acd33efa9@socionext.com \
--to=hayashi.kunihiko@socionext.com \
--cc=bhelgaas@google.com \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=robh@kernel.org \
/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®