| 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
| ||
|
Message-ID: <1d0490fe-9fbe-8ca3-7a27-0bed9aa1eac8@ti.com>
Date: Mon, 29 Nov 2021 09:33:19 +0530
From: Kishon Vijay Abraham I <kishon@...com>
To: Rob Herring <robh@...nel.org>
CC: Krzysztof Wilczyński <kw@...ux.com>,
<linux-pci@...r.kernel.org>,
Lorenzo Pieralisi <lorenzo.pieralisi@....com>,
Bjorn Helgaas <bhelgaas@...gle.com>,
<devicetree@...r.kernel.org>, <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2 1/5] dt-bindings: PCI: ti,am65: Fix
"ti,syscon-pcie-id"/"ti,syscon-pcie-mode" to take argument
Hi Rob,
On 28/11/21 4:43 am, Rob Herring wrote:
> On Fri, 26 Nov 2021 14:01:15 +0530, Kishon Vijay Abraham I wrote:
>> Fix binding documentation of "ti,syscon-pcie-id" and "ti,syscon-pcie-mode"
>> to take phandle with argument. The argument is the register offset within
>> "syscon" used to configure PCIe controller. Similar change for j721e is
>> discussed in [1]
>>
>> [1] -> http://lore.kernel.org/r/CAL_JsqKiUcO76bo1GoepWM1TusJWoty_BRy2hFSgtEVMqtrvvQ@mail.gmail.com
>>
>> Signed-off-by: Kishon Vijay Abraham I <kishon@...com>
>> ---
>> .../devicetree/bindings/pci/ti,am65-pci-ep.yaml | 8 ++++++--
>> .../bindings/pci/ti,am65-pci-host.yaml | 16 ++++++++++++----
>> 2 files changed, 18 insertions(+), 6 deletions(-)
>>
>
> Running 'make dtbs_check' with the schema in this patch gives the
> following warnings. Consider if they are expected or the schema is
> incorrect. These may not be new warnings.
>
> Note that it is not yet a requirement to have 0 warnings for dtbs_check.
> This will change in the future.
Once this series is merged, I'll send an update to the device tree files.
Without the corresponding driver changes, update to DT will break functionality.
Thanks,
Kishon
>
> Full log is available here: https://patchwork.ozlabs.org/patch/1559994
>
>
> pcie@...20000: compatible: Additional items are not allowed ('snps,dw-pcie' was unexpected)
> arch/arm/boot/dts/keystone-k2e-evm.dt.yaml
>
> pcie@...20000: compatible: ['ti,keystone-pcie', 'snps,dw-pcie'] is too long
> arch/arm/boot/dts/keystone-k2e-evm.dt.yaml
>
> pcie@...20000: reg: [[553783296, 8192], [553779200, 4096], [39977256, 4]] is too short
> arch/arm/boot/dts/keystone-k2e-evm.dt.yaml
>
> pcie@...00000: compatible: Additional items are not allowed ('snps,dw-pcie' was unexpected)
> arch/arm/boot/dts/keystone-k2e-evm.dt.yaml
> arch/arm/boot/dts/keystone-k2hk-evm.dt.yaml
> arch/arm/boot/dts/keystone-k2l-evm.dt.yaml
>
> pcie@...00000: compatible: ['ti,keystone-pcie', 'snps,dw-pcie'] is too long
> arch/arm/boot/dts/keystone-k2e-evm.dt.yaml
> arch/arm/boot/dts/keystone-k2hk-evm.dt.yaml
> arch/arm/boot/dts/keystone-k2l-evm.dt.yaml
>
> pcie@...00000: reg: [[562040832, 8192], [562036736, 4096], [39977256, 4]] is too short
> arch/arm/boot/dts/keystone-k2e-evm.dt.yaml
> arch/arm/boot/dts/keystone-k2hk-evm.dt.yaml
> arch/arm/boot/dts/keystone-k2l-evm.dt.yaml
>
> pcie@...0000: ti,syscon-pcie-id:0: [52] is too short
> arch/arm64/boot/dts/ti/k3-am654-base-board.dt.yaml
>
> pcie@...0000: ti,syscon-pcie-id:0: [60] is too short
> arch/arm64/boot/dts/ti/k3-am6528-iot2050-basic.dt.yaml
> arch/arm64/boot/dts/ti/k3-am6548-iot2050-advanced.dt.yaml
>
> pcie@...0000: ti,syscon-pcie-id:0: [61] is too short
> arch/arm64/boot/dts/ti/k3-am6528-iot2050-basic-pg2.dt.yaml
> arch/arm64/boot/dts/ti/k3-am6548-iot2050-advanced-pg2.dt.yaml
>
> pcie@...0000: ti,syscon-pcie-mode:0: [53] is too short
> arch/arm64/boot/dts/ti/k3-am654-base-board.dt.yaml
>
> pcie@...0000: ti,syscon-pcie-mode:0: [61] is too short
> arch/arm64/boot/dts/ti/k3-am6528-iot2050-basic.dt.yaml
> arch/arm64/boot/dts/ti/k3-am6548-iot2050-advanced.dt.yaml
>
> pcie@...0000: ti,syscon-pcie-mode:0: [62] is too short
> arch/arm64/boot/dts/ti/k3-am6528-iot2050-basic-pg2.dt.yaml
> arch/arm64/boot/dts/ti/k3-am6548-iot2050-advanced-pg2.dt.yaml
>
> pcie@...0000: ti,syscon-pcie-id:0: [52] is too short
> arch/arm64/boot/dts/ti/k3-am654-base-board.dt.yaml
>
> pcie@...0000: ti,syscon-pcie-id:0: [60] is too short
> arch/arm64/boot/dts/ti/k3-am6528-iot2050-basic.dt.yaml
> arch/arm64/boot/dts/ti/k3-am6548-iot2050-advanced.dt.yaml
>
> pcie@...0000: ti,syscon-pcie-id:0: [61] is too short
> arch/arm64/boot/dts/ti/k3-am6528-iot2050-basic-pg2.dt.yaml
> arch/arm64/boot/dts/ti/k3-am6548-iot2050-advanced-pg2.dt.yaml
>
> pcie@...0000: ti,syscon-pcie-mode:0: [55] is too short
> arch/arm64/boot/dts/ti/k3-am654-base-board.dt.yaml
>
> pcie@...0000: ti,syscon-pcie-mode:0: [63] is too short
> arch/arm64/boot/dts/ti/k3-am6528-iot2050-basic.dt.yaml
> arch/arm64/boot/dts/ti/k3-am6548-iot2050-advanced.dt.yaml
>
> pcie@...0000: ti,syscon-pcie-mode:0: [64] is too short
> arch/arm64/boot/dts/ti/k3-am6528-iot2050-basic-pg2.dt.yaml
> arch/arm64/boot/dts/ti/k3-am6548-iot2050-advanced-pg2.dt.yaml
>
> pcie-ep@...0000: ti,syscon-pcie-mode:0: [53] is too short
> arch/arm64/boot/dts/ti/k3-am654-base-board.dt.yaml
>
> pcie-ep@...0000: ti,syscon-pcie-mode:0: [61] is too short
> arch/arm64/boot/dts/ti/k3-am6528-iot2050-basic.dt.yaml
> arch/arm64/boot/dts/ti/k3-am6548-iot2050-advanced.dt.yaml
>
> pcie-ep@...0000: ti,syscon-pcie-mode:0: [62] is too short
> arch/arm64/boot/dts/ti/k3-am6528-iot2050-basic-pg2.dt.yaml
> arch/arm64/boot/dts/ti/k3-am6548-iot2050-advanced-pg2.dt.yaml
>
> pcie-ep@...0000: ti,syscon-pcie-mode:0: [55] is too short
> arch/arm64/boot/dts/ti/k3-am654-base-board.dt.yaml
>
> pcie-ep@...0000: ti,syscon-pcie-mode:0: [63] is too short
> arch/arm64/boot/dts/ti/k3-am6528-iot2050-basic.dt.yaml
> arch/arm64/boot/dts/ti/k3-am6548-iot2050-advanced.dt.yaml
>
> pcie-ep@...0000: ti,syscon-pcie-mode:0: [64] is too short
> arch/arm64/boot/dts/ti/k3-am6528-iot2050-basic-pg2.dt.yaml
> arch/arm64/boot/dts/ti/k3-am6548-iot2050-advanced-pg2.dt.yaml
>
Powered by blists - more mailing lists