From: <Conor.Dooley@microchip.com>
To: <jrtc27@jrtc27.com>
Cc: <Daire.McNamara@microchip.com>, <bhelgaas@google.com>,
<robh+dt@kernel.org>, <krzysztof.kozlowski+dt@linaro.org>,
<paul.walmsley@sifive.com>, <greentime.hu@sifive.com>,
<palmer@dabbelt.com>, <aou@eecs.berkeley.edu>,
<lpieralisi@kernel.org>, <Conor.Dooley@microchip.com>,
<linux-pci@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <linux-riscv@lists.infradead.org>
Subject: Re: [PATCH v2 1/6] dt-bindings: PCI: fu740-pci: fix missing clock-names
Date: Tue, 16 Aug 2022 21:32:01 +0000 [thread overview]
Message-ID: <30a33c28-1c80-8d2d-29d1-1e5aa5476af9@microchip.com> (raw)
In-Reply-To: <F62BE8A7-2023-497B-9BBC-AE54E7C5B08A@jrtc27.com>
On 16/08/2022 22:05, Jessica Clarke wrote:
> On 16 Aug 2022, at 19:25, Conor Dooley <mail@conchuod.ie> wrote:
>>
>> From: Conor Dooley <conor.dooley@microchip.com>
>>
>> The commit b92225b034c0 ("dt-bindings: PCI: designware: Fix
>> 'unevaluatedProperties' warnings") removed the clock-names property as
>> a requirement and from the example as it triggered unevaluatedProperty
>> warnings. dtbs_check was not able to pick up on this at the time, but
>> now can:
>>
>> arch/riscv/boot/dts/sifive/hifive-unmatched-a00.dtb: pcie@e00000000: Unevaluated properties are not allowed ('clock-names' was unexpected)
>> From schema: linux/Documentation/devicetree/bindings/pci/sifive,fu740-pcie.yaml
>>
>> The property was already in use by the FU740 DTS and the clock must be
>> enabled. The Linux driver does not use this property, but outside of
>> the kernel this property may have users. Re-add the property and its
>> "clocks" dependency.
>
> Are you sure about this? I see a devm_clk_get("pcie_aux") that surely
> won't without the property. FreeBSD’s similarly relies on the name,
I'm having a bit of a howler this week. I read that line of code and
for some reason came to the conclusion that it didn't match the one
in the dt. I even did it more than once given I re-wrote this commit
message. At least you're paying attention & my change is incomplete
rather than broken...
Since there's reliance on the property, it needs to become required.
> though it also has a fallback to the U-Boot pcieaux name (because the
> world is terrible and people can’t even agree on that) so it works
> with the U-Boot-provided FDT (it would be nice if Linux had this as a
> goal, and people worked with U-Boot devs to get everything needed for
> newly-exposed devices merged back there so I don’t have to be the one
> to notice and do it...).
For polarfire we are a little out of sync & plan on fixing that soonTM.
>
> Jess
>
>> Fixes: b92225b034c0 ("dt-bindings: PCI: designware: Fix 'unevaluatedProperties' warnings")
>> Fixes: 43cea116be0b ("dt-bindings: PCI: Add SiFive FU740 PCIe host controller")
>> Signed-off-by: Conor Dooley <conor.dooley@microchip.com>
>> ---
>> v2022.08 of dt-schema is required.
>> ---
>> .../devicetree/bindings/pci/sifive,fu740-pcie.yaml | 6 ++++++
>> 1 file changed, 6 insertions(+)
>>
>> diff --git a/Documentation/devicetree/bindings/pci/sifive,fu740-pcie.yaml b/Documentation/devicetree/bindings/pci/sifive,fu740-pcie.yaml
>> index 195e6afeb169..c7a9a2dc0fa6 100644
>> --- a/Documentation/devicetree/bindings/pci/sifive,fu740-pcie.yaml
>> +++ b/Documentation/devicetree/bindings/pci/sifive,fu740-pcie.yaml
>> @@ -51,6 +51,12 @@ properties:
>> description: A phandle to the PCIe power up reset line.
>> maxItems: 1
>>
>> + clocks:
>> + maxItems: 1
>> +
>> + clock-names:
>> + const: pcie_aux
>> +
>> pwren-gpios:
>> description: Should specify the GPIO for controlling the PCI bus device power on.
>> maxItems: 1
>> --
>> 2.37.1
>>
>>
>> _______________________________________________
>> linux-riscv mailing list
>> linux-riscv@lists.infradead.org
>> http://lists.infradead.org/mailman/listinfo/linux-riscv
>
next prev parent reply other threads:[~2022-08-16 21:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-16 18:25 [PATCH v2 0/6] Fix RISC-V/PCI dt-schema issues with dt-schema v2022.08 Conor Dooley
2022-08-16 18:25 ` [PATCH v2 1/6] dt-bindings: PCI: fu740-pci: fix missing clock-names Conor Dooley
2022-08-16 21:05 ` Jessica Clarke
2022-08-16 21:32 ` Conor.Dooley [this message]
2022-08-16 18:25 ` [PATCH v2 2/6] dt-bindings: PCI: microchip,pcie-host: fix missing clocks properties Conor Dooley
2022-08-18 15:06 ` Rob Herring
2022-08-18 15:34 ` Conor.Dooley
2022-08-16 18:25 ` [PATCH v2 3/6] riscv: dts: microchip: mpfs: fix incorrect pcie child node name Conor Dooley
2022-08-16 18:25 ` [PATCH v2 4/6] riscv: dts: microchip: mpfs: remove ti,fifo-depth property Conor Dooley
2022-08-16 18:25 ` [PATCH v2 5/6] riscv: dts: microchip: mpfs: remove bogus card-detect-delay Conor Dooley
2022-08-16 18:25 ` [PATCH v2 6/6] riscv: dts: microchip: mpfs: remove pci axi address translation property Conor Dooley
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=30a33c28-1c80-8d2d-29d1-1e5aa5476af9@microchip.com \
--to=conor.dooley@microchip.com \
--cc=Daire.McNamara@microchip.com \
--cc=aou@eecs.berkeley.edu \
--cc=bhelgaas@google.com \
--cc=devicetree@vger.kernel.org \
--cc=greentime.hu@sifive.com \
--cc=jrtc27@jrtc27.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=lpieralisi@kernel.org \
--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).