From: Conor Dooley <conor@kernel.org>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: "Minda Chen" <minda.chen@starfivetech.com>,
"Emil Renner Berthing" <emil.renner.berthing@canonical.com>,
"Rob Herring" <robh+dt@kernel.org>,
"Bjorn Helgaas" <bhelgaas@google.com>,
"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
"Lorenzo Pieralisi" <lpieralisi@kernel.org>,
"Krzysztof Wilczyński" <kw@linux.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-riscv@lists.infradead.org, linux-pci@vger.kernel.org,
"Paul Walmsley" <paul.walmsley@sifive.com>,
"Palmer Dabbelt" <palmer@dabbelt.com>,
"Albert Ou" <aou@eecs.berkeley.edu>,
"Philipp Zabel" <p.zabel@pengutronix.de>,
"Mason Huo" <mason.huo@starfivetech.com>,
"Leyfoon Tan" <leyfoon.tan@starfivetech.com>,
"Kevin Xie" <kevin.xie@starfivetech.com>
Subject: Re: [PATCH v1 1/3] dt-binding: pci: add JH7110 PCIe dt-binding documents.
Date: Thu, 6 Apr 2023 19:35:03 +0100 [thread overview]
Message-ID: <20230406-revisit-patchy-a0063d964070@spud> (raw)
In-Reply-To: <38bc48bf-7d8c-8ddd-861f-3b7f3d2edce6@linaro.org>
[-- Attachment #1: Type: text/plain, Size: 1525 bytes --]
On Thu, Apr 06, 2023 at 08:24:55PM +0200, Krzysztof Kozlowski wrote:
> On 06/04/2023 13:11, Minda Chen wrote:
> > +
> > + interrupt-controller:
> > + type: object
> > + properties:
> > + '#address-cells':
> > + const: 0
> > +
> > + '#interrupt-cells':
> > + const: 1
> > +
> > + interrupt-controller: true
> > +
> > + required:
> > + - '#address-cells'
> > + - '#interrupt-cells'
> > + - interrupt-controller
> > +
> > + additionalProperties: false
> > +
> > +required:
> > + - reg
> > + - reg-names
> > + - "#interrupt-cells"
>
> Keep consistent quotes - either ' or "
>
> Are you sure this is correct? You have interrupt controller as child node.
I know existing stuff in-tree is far from a guarantee that it'll be
right, but this does at least follow what we've got for PolarFire SoC:
Documentation/devicetree/bindings/pci/microchip,pcie-host.yaml
Both PLDA and both RISC-V w/ a PLIC as the interrupt controller, so in
similar waters.
This note existed in the original text form binding of the Microchip
PCI controller:
| +NOTE:
| +The core provides a single interrupt for both INTx/MSI messages. So,
| +create an interrupt controller node to support 'interrupt-map' DT
| +functionality. The driver will create an IRQ domain for this map, decode
| +the four INTx interrupts in ISR and route them to this domain.
Given the similarities, I figure the same requirement applies here too.
Minda?
Cheers,
Conor.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2023-04-06 18:35 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-06 11:11 [PATCH v1 0/3] Add JH7110 PCIe driver support Minda Chen
2023-04-06 11:11 ` [PATCH v1 1/3] dt-binding: pci: add JH7110 PCIe dt-binding documents Minda Chen
2023-04-06 18:24 ` Krzysztof Kozlowski
2023-04-06 18:35 ` Conor Dooley [this message]
2023-04-06 18:45 ` Conor Dooley
2023-04-06 18:52 ` Krzysztof Kozlowski
2023-04-07 3:45 ` Minda Chen
2023-04-10 9:05 ` Minda Chen
2023-04-10 15:21 ` Krzysztof Kozlowski
2023-04-11 7:45 ` Minda Chen
2023-04-12 10:17 ` Bin Meng
2023-04-06 11:11 ` [PATCH v1 2/3] pcie: starfive: add StarFive JH7110 PCIe driver Minda Chen
2023-04-06 11:11 ` [PATCH v1 3/3] riscv: dts: starfive: add PCIe dts configuration for JH7110 Minda Chen
2023-04-06 18:25 ` Krzysztof Kozlowski
2023-04-06 11:47 ` [PATCH v1 0/3] Add JH7110 PCIe driver support Conor Dooley
2023-04-06 11:54 ` Conor Dooley
2023-04-07 2:32 ` Minda Chen
2023-04-07 9:57 ` Conor Dooley
2023-04-10 8:58 ` Minda 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=20230406-revisit-patchy-a0063d964070@spud \
--to=conor@kernel.org \
--cc=aou@eecs.berkeley.edu \
--cc=bhelgaas@google.com \
--cc=devicetree@vger.kernel.org \
--cc=emil.renner.berthing@canonical.com \
--cc=kevin.xie@starfivetech.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=kw@linux.com \
--cc=leyfoon.tan@starfivetech.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=lpieralisi@kernel.org \
--cc=mason.huo@starfivetech.com \
--cc=minda.chen@starfivetech.com \
--cc=p.zabel@pengutronix.de \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).