From: Florian Eckert <fe@dev.tdt.de>
To: Rob Herring <robh@kernel.org>
Cc: linux-pci@vger.kernel.org, Eckert.Florian@googlemail.com,
"Rahul Tanwar" <rtanwar@maxlinear.com>,
linux-kernel@vger.kernel.org,
"Lorenzo Pieralisi" <lpieralisi@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Sajid Dalvi" <sdalvi@google.com>,
"Bjorn Helgaas" <bhelgaas@google.com>,
"Manivannan Sadhasivam" <mani@kernel.org>,
"Ajay Agarwal" <ajayagarwal@google.com>,
devicetree@vger.kernel.org,
"Johan Hovold" <johan+linaro@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
ms@dev.tdt.de, "Krzysztof Wilczyński" <kwilczynski@kernel.org>
Subject: Re: [PATCH v3 7/7] dt-bindings: PCI: intel,lgm-pcie: Add atu resource
Date: Wed, 1 Apr 2026 15:49:37 +0200 (CEST) [thread overview]
Message-ID: <5dd6db90e7cd5b2e75dbb85dab202dde@dev.tdt.de> (raw)
In-Reply-To: <CAL_JsqL2JW6zecCJGhFiJYraSGRNJGRsZ+oWJ+=4JWY5GD9SPQ@mail.gmail.com>
On 2026-04-01 15:07, Rob Herring wrote:
> On Wed, Apr 1, 2026 at 5:37 AM Rob Herring (Arm) <robh@kernel.org>
> wrote:
>>
>>
>> On Wed, 01 Apr 2026 11:31:43 +0200, Florian Eckert wrote:
>> > The 'atu' information is already set in the dwc core, if it is specified
>> > in the devicetree. The driver uses its own default, if not set in the
>> > devicetree. This information is hardware specific and should therefore be
>> > maintained in the devicetree rather than in the source.
>> >
>> > To be backward compatibile, this field is not mandatory. If 'atu'
>> > resource is not specified in the devicetree, the driver’s default value
>> > is used.
>> >
>> > Old DTS entry for PCIe:
>> >
>> > reg = <0xd1000000 0x1000>,
>> > <0xd3000000 0x20000>,
>> > <0xd0c41000.0x1000>;
>> > reg-names = "dbi", "config", "app";
>> >
>> > New DTS entry for PCIe:
>> >
>> > reg = <0xd1000000 0x1000>,
>> > <0xd10c0000 0x1000>,
>> > <0xd3000000 0x20000>,
>> > <0xd0c41000.0x1000>;
>> > reg-names = "dbi", "atu", "config", "app";
>
> This is also wrong. But the diff of the example shows the old vs. new,
> so there's really no reason for any of this in the commit msg.
Got it. Thanks for pointing that out. I’ve already removed it for the
next cycle for the v4.
--
Florian
>> >
>> > Signed-off-by: Florian Eckert <fe@dev.tdt.de>
>> > ---
>> > Documentation/devicetree/bindings/pci/intel-gw-pcie.yaml | 6 +++++-
>> > 1 file changed, 5 insertions(+), 1 deletion(-)
>> >
>>
>> My bot found errors running 'make dt_binding_check' on your patch:
>>
>> yamllint warnings/errors:
>>
>> dtschema/dtc warnings/errors:
>> /builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/pci/intel-gw-pcie.example.dtb:
>> pcie@d0e00000 (intel,lgm-pcie): reg-names:1: 'config' was expected
>> from schema $id:
>> http://devicetree.org/schemas/pci/intel-gw-pcie.yaml
>> /builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/pci/intel-gw-pcie.example.dtb:
>> pcie@d0e00000 (intel,lgm-pcie): reg-names:2: 'app' was expected
>> from schema $id:
>> http://devicetree.org/schemas/pci/intel-gw-pcie.yaml
>> /builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/pci/intel-gw-pcie.example.dtb:
>> pcie@d0e00000 (intel,lgm-pcie): reg-names:3: 'atu' was expected
>> from schema $id:
>> http://devicetree.org/schemas/pci/intel-gw-pcie.yaml
>>
>> doc reference errors (make refcheckdocs):
>>
>> See
>> https://patchwork.kernel.org/project/devicetree/patch/20260401-pcie-intel-gw-v3-7-63b008c5b7b2@dev.tdt.de
>>
>> The base for the series is generally the latest rc1. A different
>> dependency
>> should be noted in *this* patch.
>>
>> If you already ran 'make dt_binding_check' and didn't see the above
>> error(s), then make sure 'yamllint' is installed and dt-schema is up
>> to
>> date:
>>
>> pip3 install dtschema --upgrade
>>
>> Please check and re-submit after running the above command yourself.
>> Note
>> that DT_SCHEMA_FILES can be set to your schema file to speed up
>> checking
>> your schema. However, it must be unset to test all examples with your
>> schema.
>>
>>
prev parent reply other threads:[~2026-04-01 13:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-01 9:31 [PATCH v3 0/7] PCI: intel-gw: Fixes to make the driver working again Florian Eckert
2026-04-01 9:31 ` [PATCH v3 1/7] MAINTAINERS: Remove bouncing intel-gw maintainer Florian Eckert
2026-04-01 9:31 ` [PATCH v3 2/7] PCI: intel-gw: Remove unused define Florian Eckert
2026-04-01 9:31 ` [PATCH v3 3/7] PCI: intel-gw: Move interrupt enable to own function Florian Eckert
2026-04-01 9:31 ` [PATCH v3 4/7] PCI: intel-gw: Enable clock before phy init Florian Eckert
2026-04-01 9:31 ` [PATCH v3 5/7] PCI: intel-gw: Add start_link callback function Florian Eckert
2026-04-01 9:31 ` [PATCH v3 6/7] PCI: intel-gw: Move driver atu base assignment to probe function Florian Eckert
2026-04-01 9:31 ` [PATCH v3 7/7] dt-bindings: PCI: intel,lgm-pcie: Add atu resource Florian Eckert
2026-04-01 10:37 ` Rob Herring (Arm)
2026-04-01 13:07 ` Rob Herring
2026-04-01 13:49 ` Florian Eckert [this message]
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=5dd6db90e7cd5b2e75dbb85dab202dde@dev.tdt.de \
--to=fe@dev.tdt.de \
--cc=Eckert.Florian@googlemail.com \
--cc=ajayagarwal@google.com \
--cc=bhelgaas@google.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=johan+linaro@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=kwilczynski@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=mani@kernel.org \
--cc=ms@dev.tdt.de \
--cc=robh@kernel.org \
--cc=rtanwar@maxlinear.com \
--cc=sdalvi@google.com \
/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