From: Conor Dooley <conor@kernel.org>
To: hans.zhang@cixtech.com
Cc: bhelgaas@google.com, lpieralisi@kernel.org, kw@linux.com,
manivannan.sadhasivam@linaro.org, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org, peter.chen@cixtech.com,
linux-pci@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Manikandan K Pillai <mpillai@cadence.com>
Subject: Re: [PATCH v4 2/5] dt-bindings: pci: cadence: Extend compatible for new EP configurations
Date: Thu, 24 Apr 2025 16:30:37 +0100 [thread overview]
Message-ID: <20250424-proposal-decrease-ba384a37efa6@spud> (raw)
In-Reply-To: <20250424-elm-magma-b791798477ab@spud>
[-- Attachment #1: Type: text/plain, Size: 1807 bytes --]
On Thu, Apr 24, 2025 at 04:29:35PM +0100, Conor Dooley wrote:
> On Thu, Apr 24, 2025 at 09:04:41AM +0800, hans.zhang@cixtech.com wrote:
> > From: Manikandan K Pillai <mpillai@cadence.com>
> >
> > Document the compatible property for HPA (High Performance Architecture)
> > PCIe controller EP configuration.
>
> Please explain what makes the new architecture sufficiently different
> from the existing one such that a fallback compatible does not work.
>
> Same applies to the other binding patch.
Additionally, since this IP is likely in use on your sky1 SoC, why is a
soc-specific compatible for your integration not needed?
>
> Thanks,
> Conor.
>
> >
> > Signed-off-by: Manikandan K Pillai <mpillai@cadence.com>
> > Signed-off-by: Hans Zhang <hans.zhang@cixtech.com>
> > ---
> > .../devicetree/bindings/pci/cdns,cdns-pcie-ep.yaml | 6 ++++--
> > 1 file changed, 4 insertions(+), 2 deletions(-)
> >
> > diff --git a/Documentation/devicetree/bindings/pci/cdns,cdns-pcie-ep.yaml b/Documentation/devicetree/bindings/pci/cdns,cdns-pcie-ep.yaml
> > index 98651ab22103..a7e404e4f690 100644
> > --- a/Documentation/devicetree/bindings/pci/cdns,cdns-pcie-ep.yaml
> > +++ b/Documentation/devicetree/bindings/pci/cdns,cdns-pcie-ep.yaml
> > @@ -7,14 +7,16 @@ $schema: http://devicetree.org/meta-schemas/core.yaml#
> > title: Cadence PCIe EP Controller
> >
> > maintainers:
> > - - Tom Joseph <tjoseph@cadence.com>
> > + - Manikandan K Pillai <mpillai@cadence.com>
> >
> > allOf:
> > - $ref: cdns-pcie-ep.yaml#
> >
> > properties:
> > compatible:
> > - const: cdns,cdns-pcie-ep
> > + enum:
> > + - cdns,cdns-pcie-ep
> > + - cdns,cdns-pcie-hpa-ep
> >
> > reg:
> > maxItems: 2
> > --
> > 2.47.1
> >
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2025-04-24 15:30 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-24 1:04 [PATCH v4 0/5] Enhance the PCIe controller driver hans.zhang
2025-04-24 1:04 ` [PATCH v4 1/5] dt-bindings: pci: cadence: Extend compatible for new RP configuration hans.zhang
2025-04-24 1:04 ` [PATCH v4 2/5] dt-bindings: pci: cadence: Extend compatible for new EP configurations hans.zhang
2025-04-24 15:29 ` Conor Dooley
2025-04-24 15:30 ` Conor Dooley [this message]
2025-04-25 2:19 ` Manikandan Karunakaran Pillai
2025-04-25 14:48 ` Conor Dooley
2025-04-25 15:33 ` Hans Zhang
2025-04-25 16:21 ` Krzysztof Kozlowski
2025-04-25 16:47 ` Hans Zhang
2025-04-27 3:55 ` Manikandan Karunakaran Pillai
2025-04-27 19:08 ` Krzysztof Kozlowski
2025-04-25 2:17 ` Manikandan Karunakaran Pillai
2025-04-24 1:04 ` [PATCH v4 3/5] PCI: cadence: Add header support for PCIe HPA controller hans.zhang
2025-04-24 3:36 ` Peter Chen (CIX)
2025-04-25 4:18 ` kernel test robot
2025-04-24 1:04 ` [PATCH v4 4/5] PCI: cadence: Add support for PCIe Endpoint " hans.zhang
2025-04-24 1:04 ` [PATCH v4 5/5] PCI: cadence: Add callback functions for RP and EP controller hans.zhang
2025-04-25 6:01 ` kernel test robot
2025-04-25 16:27 ` Krzysztof Kozlowski
2025-04-25 16:51 ` Hans Zhang
2025-04-27 3:52 ` Manikandan Karunakaran Pillai
2025-06-01 14:40 ` manivannan.sadhasivam
2025-06-02 1:24 ` Manikandan Karunakaran Pillai
2025-04-25 16:24 ` [PATCH v4 0/5] Enhance the PCIe controller driver Krzysztof Kozlowski
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=20250424-proposal-decrease-ba384a37efa6@spud \
--to=conor@kernel.org \
--cc=bhelgaas@google.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=hans.zhang@cixtech.com \
--cc=krzk+dt@kernel.org \
--cc=kw@linux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=mpillai@cadence.com \
--cc=peter.chen@cixtech.com \
--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