On Wed, Feb 04, 2026 at 10:21:49AM -0500, Frank Li wrote:

On Wed, Feb 04, 2026 at 06:03:55PM +0530, Manivannan Sadhasivam wrote:

quoted

On Wed, Feb 04, 2026 at 06:44:07AM +0000, Sherry Sun wrote:

quoted

quoted

On Tue, Feb 03, 2026 at 09:56:07AM +0800, Sherry Sun wrote:

quoted

Since describing the PCIe PERST# property under Host Bridge node is
now deprecated, it is recommended to add it to the Root Port node, so
creating the Root Port node and add the reset-gpios property in Root
Port.

Signed-off-by: Sherry Sun <redacted>
---
 arch/arm/boot/dts/nxp/imx/imx6qdl-sabresd.dtsi |  5 +++++
 arch/arm/boot/dts/nxp/imx/imx6qdl.dtsi         | 11 +++++++++++
 arch/arm/boot/dts/nxp/imx/imx6qp-sabreauto.dts |  5 +++++
 3 files changed, 21 insertions(+)

diff --git a/arch/arm/boot/dts/nxp/imx/imx6qdl-sabresd.dtsi

b/arch/arm/boot/dts/nxp/imx/imx6qdl-sabresd.dtsi
index ba29720e3f72..fe9046c03ddd 100644

--- a/arch/arm/boot/dts/nxp/imx/imx6qdl-sabresd.dtsi
+++ b/arch/arm/boot/dts/nxp/imx/imx6qdl-sabresd.dtsi

@@ -754,11 +754,16 @@ lvds0_out: endpoint {  &pcie {
 	pinctrl-names = "default";
 	pinctrl-0 = <&pinctrl_pcie>;
+	/* This property is deprecated, use reset-gpios from the Root Port
+node. */
 	reset-gpio = <&gpio7 12 GPIO_ACTIVE_LOW>;

You should just remove this property.

Hi Manivannan,

Actually I have discussed with Frank about this in V1, Frank suggested add
comments here instead of removing the old property, just in case the dts
used by old kernel to avoid function break. Or maybe we can at least keep it
for some kernel release, then remove it later.

If the new DT breaks the old kernel, then the kernel needs to be upgraded. But
typically, one would update both kernel + DT or just the kernel, not just DT.

But it should not impact bisect. Driver and dts is not in branch. If driver
applied ahead of dts patch, it should be fine to remove it. But default
linux-next can't guaratee the merge order.

There is no need to worry about the bisectability in linux-next. You should only
worry about mainline. So if you ensure that both the driver and DTS gets into
the same release or even if the driver gets in first and DTS later, you are
good.
 

To avoid merge complex, keep it for a whole, then clean up it later.

There is no complexity. We do this all the time. If you add a comment like this,
then you need to remember to delete it later, which unfortunately won't happen
all the time for us humans :)

- Mani

-- 
மணிவண்ணன் சதாசிவம்