linux-kernel - RE: [PATCH 1/7] dt-bindings: pci: cadence: Extend compatible for new platform configurations

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID:
 <DS0PR07MB1049293A9CDEBA2B3BCCED34DA2A02@DS0PR07MB10492.namprd07.prod.outlook.com>
Date: Fri, 28 Mar 2025 05:07:32 +0000
From: Manikandan Karunakaran Pillai <mpillai@...ence.com>
To: Krzysztof Kozlowski <krzk@...nel.org>,
        "bhelgaas@...gle.com"
	<bhelgaas@...gle.com>,
        "lpieralisi@...nel.org" <lpieralisi@...nel.org>,
        "kw@...ux.com" <kw@...ux.com>,
        "manivannan.sadhasivam@...aro.org"
	<manivannan.sadhasivam@...aro.org>,
        "robh@...nel.org" <robh@...nel.org>,
        "krzk+dt@...nel.org" <krzk+dt@...nel.org>,
        "conor+dt@...nel.org"
	<conor+dt@...nel.org>,
        Milind Parab <mparab@...ence.com>
CC: "linux-pci@...r.kernel.org" <linux-pci@...r.kernel.org>,
        "devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH 1/7] dt-bindings: pci: cadence: Extend compatible for new
 platform configurations

>EXTERNAL MAIL
>
>
>On 27/03/2025 12:19, Manikandan Karunakaran Pillai wrote:
>> Document the compatible property for the newly added values for PCIe EP
>and
>> RP configurations. Fix the compilation issues that came up for the existing
>> Cadence bindings
>
>These are two different commits.

Ok

>
>>
>> Signed-off-by: Manikandan K Pillai <mpillai@...ence.com>
>> ---
>>  .../bindings/pci/cdns,cdns-pcie-ep.yaml       |  12 +-
>>  .../bindings/pci/cdns,cdns-pcie-host.yaml     | 119 +++++++++++++++---
>>  2 files changed, 110 insertions(+), 21 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..aa4ad69a9b71 100644
>> --- a/Documentation/devicetree/bindings/pci/cdns,cdns-pcie-ep.yaml
>> +++ b/Documentation/devicetree/bindings/pci/cdns,cdns-pcie-ep.yaml
>> @@ -7,14 +7,22 @@ $schema:
>https://urldefense.com/v3/__http://devicetree.org/meta-
>schemas/core.yaml*__;Iw!!EHscmS1ygiU1lA!CB5lvkvRUKSEDPSjpW7GJoPNyXZ
>xMge5SyndD4Z-VVLCZvzLIPDP-BMRjhKZ2UTxi6a18vaodaU$
>>  title: Cadence PCIe EP Controller
>>
>>  maintainers:
>> -  - Tom Joseph <tjoseph@...ence.com>
>> +  - Manikandan K Pillai <mpillai@...ence.com>
>>
>>  allOf:
>>    - $ref: cdns-pcie-ep.yaml#
>>
>>  properties:
>>    compatible:
>> -    const: cdns,cdns-pcie-ep
>> +    oneOf:
>> +      - const: cdns,cdns-pcie-ep
>> +      - const: cdns,cdns-pcie-hpa-ep
>
>What is hpa? Which soc is that?
>
>I don't think this should keep growing, but instead use SoC based
>compatibles.
>
>Anyway, that's enum.
>

HPA is high performance architecture based controllers. The major difference here in PCIe controllers is that
the address map changes. Each of the compatibles defined here have different address maps that allow the driver
to support them from the driver using compable property that provides the info from related data "struct of_device_id" in the driver.

>> +      - const: cdns,cdns-cix-pcie-hpa-ep
>
>What is cix? If you want to stuff here soc in the middle, then no, no
>no. Please read devicetree spec and writing bindings how the compatibles
>are created.
>

As mentioned in the earlier sections, cix is another implementation of the PCIe controller where 
the address map is changed by our customer

>> +      - description: PCIe EP controller from cadence
>> +        items:
>> +          - const: cdns,cdns-pcie-ep
>> +          - const: cdns,cdns-pcie-hpa-ep
>> +          - const: cdns,cdns-cix-pcie-hpa-ep
>
>This makes no sense.
>
Only one of the above compatible is valid for PCIe controllers, which will be defined in the SoC related binding.

>>
>>    reg:
>> diff --git a/Documentation/devicetree/bindings/pci/cdns,cdns-pcie-host.yaml
>b/Documentation/devicetree/bindings/pci/cdns,cdns-pcie-host.yaml
>> index a8190d9b100f..bb7ffb9ddaf9 100644
>> --- a/Documentation/devicetree/bindings/pci/cdns,cdns-pcie-host.yaml
>> +++ b/Documentation/devicetree/bindings/pci/cdns,cdns-pcie-host.yaml
>>
>>  maintainers:
>> -  - Tom Joseph <tjoseph@...ence.com>
>> +  - Manikandan K Pillai <mpillai@...ence.com>
>>
>>  allOf:
>> -  - $ref: cdns-pcie-host.yaml#
>> +  - $ref: cdns-pcie.yaml#
>
>Why?
>

The existing yaml files were throwing out errors and the changes in these files are for fixing them.

>>
>>  properties:
>> +  "#size-cells":
>> +    const: 2
>> +  "#address-cells":
>> +    const: 3
>
>Huh? Why? Nothing here makes sense.
>
>
Compilation error related fixes.

>Best regards,
>Krzysztof