[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAOMZO5D+nMPDcQ3rPB+QC437tXYoa2VKdZtZzFdAnBkJEa=A6w@mail.gmail.com>
Date: Fri, 10 Apr 2020 09:57:25 -0300
From: Fabio Estevam <festevam@...il.com>
To: Ansuel Smith <ansuelsmth@...il.com>
Cc: "open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@...r.kernel.org>, Richard Zhu <hongxing.zhu@....com>,
Lucas Stach <l.stach@...gutronix.de>,
Bjorn Helgaas <bhelgaas@...gle.com>,
Rob Herring <robh+dt@...nel.org>,
Mark Rutland <mark.rutland@....com>,
Shawn Guo <shawnguo@...nel.org>,
Sascha Hauer <s.hauer@...gutronix.de>,
Pengutronix Kernel Team <kernel@...gutronix.de>,
NXP Linux Team <linux-imx@....com>,
Lorenzo Pieralisi <lorenzo.pieralisi@....com>,
Andrew Murray <amurray@...goodpenguin.co.uk>,
linux-pci@...r.kernel.org,
"moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE"
<linux-arm-kernel@...ts.infradead.org>,
linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 2/4] drivers: pci: dwc: pci-imx6: update binding to
generic name
On Fri, Apr 10, 2020 at 9:40 AM <ansuelsmth@...il.com> wrote:
> It's really to not have the same exact binding to 2 different driver.
> If this would cause problem I will use qcom,tx-deemph...... but still it looks
> wrong to me having this. How should I proceed?
You could make the imx6 PCI driver to accept both the new and old
binding versions.
This way we can keep compatibility with old dtb's.
Also, if you respin this, please state the motivation that you
explained here in the commit log.
Powered by blists - more mailing lists