From: Thierry Reding <thierry.reding@gmail.com>
To: Rob Herring <robh+dt@kernel.org>
Cc: Lorenzo Pieralisi <lpieralisi@kernel.org>,
Sergey Semin <Sergey.Semin@baikalelectronics.ru>,
Jon Hunter <jonathanh@nvidia.com>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
linux-pci@vger.kernel.org, devicetree@vger.kernel.org,
linux-tegra@vger.kernel.org, vidyas@nvidia.com,
mmaddireddy@nvidia.com
Subject: Re: [PATCH V3 1/2] dt-bindings: PCI: tegra234: Add ECAM support
Date: Tue, 6 Dec 2022 17:44:51 +0100 [thread overview]
Message-ID: <Y49xg7wptRweHd4I@orome> (raw)
In-Reply-To: <CAL_JsqKpyn=mWXv4tuS4U8AahNPkL6hpNQCfyRdf9bDY1EqSJg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2438 bytes --]
On Mon, Dec 05, 2022 at 05:41:55PM -0600, Rob Herring wrote:
> On Thu, Nov 17, 2022 at 3:38 PM Thierry Reding <thierry.reding@gmail.com> wrote:
> >
> > On Mon, Nov 14, 2022 at 03:53:32PM +0000, Jon Hunter wrote:
> > > From: Vidya Sagar <vidyas@nvidia.com>
> > >
> > > Add support for ECAM aperture that is only supported for Tegra234
> > > devices.
> > >
> > > Signed-off-by: Vidya Sagar <vidyas@nvidia.com>
> > > Co-developed-by: Jon Hunter <jonathanh@nvidia.com>
> > > Signed-off-by: Jon Hunter <jonathanh@nvidia.com>
> > > ---
> > > Changes since V2:
> > > - Avoid duplication of reg items and reg-names
> > > Changes since V1:
> > > - Restricted the ECAM aperture to only Tegra234 devices that support it.
> > >
> > > .../bindings/pci/nvidia,tegra194-pcie.yaml | 34 +++++++++++++++++--
> > > .../devicetree/bindings/pci/snps,dw-pcie.yaml | 2 +-
> > > 2 files changed, 33 insertions(+), 3 deletions(-)
> >
> > Both patches applied now.
>
> linux-next now fails with this. I suspect it is due to Sergey's
> changes to the DWC schema.
>
> /builds/robherring/linux-dt/Documentation/devicetree/bindings/pci/nvidia,tegra194-pcie.example.dtb:
> pcie@14160000: reg-names:4: 'oneOf' conditional failed, one must be
> fixed:
> 'dbi' was expected
> 'dbi2' was expected
> 'ecam' is not one of ['elbi', 'app']
> 'atu' was expected
> 'dma' was expected
> 'phy' was expected
> 'config' was expected
> /builds/robherring/linux-dt/Documentation/devicetree/bindings/pci/nvidia,tegra194-pcie.example.dtb:
> pcie@14160000: reg-names:4: 'oneOf' conditional failed, one must be
> fixed:
> 'ecam' is not one of ['apb', 'mgmt', 'link', 'ulreg', 'appl']
> 'ecam' is not one of ['atu_dma']
> 'ecam' is not one of ['smu', 'mpu']
> From schema:
> /builds/robherring/linux-dt/Documentation/devicetree/bindings/pci/nvidia,tegra194-pcie.yaml
Stephen reported the other day that he wasn't able to resolve this
conflict in linux-next, so he dropped the ECAM bits. The ECAM patch has
now propagated to ARM SoC so it can't be easily backed out, but I guess
we could revert on that tree and instead apply the patch to the DT tree
and resolve the conflict there.
I guess the better alternative would be to try and resolve the merge
properly and let Stephen (and Linus) know.
Thierry
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-12-06 16:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-14 15:53 [PATCH V3 0/2] Add ECAM aperture for Tegra234 Jon Hunter
2022-11-14 15:53 ` [PATCH V3 1/2] dt-bindings: PCI: tegra234: Add ECAM support Jon Hunter
2022-11-14 16:41 ` Krzysztof Kozlowski
2022-11-15 2:01 ` Rob Herring
2022-11-15 16:02 ` Jon Hunter
2022-11-15 18:00 ` Rob Herring
2022-11-17 21:38 ` Thierry Reding
2022-12-05 23:41 ` Rob Herring
2022-12-06 16:44 ` Thierry Reding [this message]
2022-12-06 21:14 ` Rob Herring
2022-12-07 10:21 ` Thierry Reding
2022-12-09 10:17 ` Serge Semin
2022-12-09 14:29 ` Rob Herring
2022-12-11 17:16 ` Serge Semin
2022-11-14 15:53 ` [PATCH V3 2/2] arm64: tegra: Add ECAM aperture info for all the PCIe controllers Jon Hunter
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=Y49xg7wptRweHd4I@orome \
--to=thierry.reding@gmail.com \
--cc=Sergey.Semin@baikalelectronics.ru \
--cc=devicetree@vger.kernel.org \
--cc=jonathanh@nvidia.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=mmaddireddy@nvidia.com \
--cc=robh+dt@kernel.org \
--cc=vidyas@nvidia.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.