[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200819223031.GA2077542@bogus>
Date: Wed, 19 Aug 2020 16:30:31 -0600
From: Rob Herring <robh@...nel.org>
To: Marc Zyngier <maz@...nel.org>
Cc: Bjorn Helgaas <bhelgaas@...gle.com>,
Jiaxun Yang <jiaxun.yang@...goat.com>, kernel-team@...roid.com,
Heiko Stuebner <heiko@...ech.de>,
Frank Rowand <frowand.list@...il.com>,
Rob Herring <robh+dt@...nel.org>, devicetree@...r.kernel.org,
Shawn Lin <shawn.lin@...k-chips.com>,
linux-rockchip@...ts.infradead.org,
Lorenzo Pieralisi <lorenzo.pieralisi@....com>,
linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-pci@...r.kernel.org
Subject: Re: [PATCH v2] of: address: Work around missing device_type property
in pcie nodes
On Wed, 19 Aug 2020 10:42:55 +0100, Marc Zyngier wrote:
> Recent changes to the DT PCI bus parsing made it mandatory for
> device tree nodes describing a PCI controller to have the
> 'device_type = "pci"' property for the node to be matched.
>
> Although this follows the letter of the specification, it
> breaks existing device-trees that have been working fine
> for years. Rockchip rk3399-based systems are a prime example
> of such collateral damage, and have stopped discovering their
> PCI bus.
>
> In order to paper over it, let's add a workaround to the code
> matching the device type, and accept as PCI any node that is
> named "pcie",
>
> A warning will hopefully nudge the user into updating their
> DT to a fixed version if they can, but the incentive is
> obviously pretty small.
>
> Fixes: 2f96593ecc37 ("of_address: Add bus type match for pci ranges parser")
> Suggested-by: Rob Herring <robh+dt@...nel.org>
> Signed-off-by: Marc Zyngier <maz@...nel.org>
> ---
> drivers/of/address.c | 16 +++++++++++++++-
> 1 file changed, 15 insertions(+), 1 deletion(-)
>
Applied, thanks!
Powered by blists - more mailing lists