From: Lucas Stach <l.stach@pengutronix.de>
To: "Petr Štetiar" <ynezz@true.cz>
Cc: "Fabio Estevam" <festevam@gmail.com>,
"Tim Harvey" <tharvey@gateworks.com>,
"Bjorn Helgaas" <bhelgaas@google.com>,
"Richard Zhu" <Richard.Zhu@freescale.com>,
"Krzysztof Hałasa" <khalasa@piap.pl>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
"Fabio Estevam" <fabio.estevam@nxp.com>,
stable <stable@vger.kernel.org>
Subject: Re: [PATCH v2] Revert "PCI: imx6: Add support for active-low reset GPIO"
Date: Wed, 30 Mar 2016 15:20:50 +0200 [thread overview]
Message-ID: <1459344050.2565.41.camel@pengutronix.de> (raw)
In-Reply-To: <20160330131639.GO20367@ibawizard.net>
Am Mittwoch, den 30.03.2016, 15:16 +0200 schrieb Petr Štetiar:
> Fabio Estevam <festevam@gmail.com> [2016-03-30 10:07:16]:
>
> > If we apply Krzysztof's patch then we break PCI in imx6qdl-sabresd.
> >
> > In this board we have:
> >
> > reset-gpio = <&gpio7 12 0>;
> >
> > , which is wrong. Of course, we should fix this to be 'reset-gpio =
> > <&gpio7 12 GPIO_ACTIVE_LOW>;'
> >
> > However we should not break old dtb's. That's why reverting the patch
> > is the only solution we have so that old dtb's still work.
>
> But this only apply for stable right? I understand this and it's fine with me.
>
> > We have had this same problem for the FEC PHY reset. The solution
> > there was to add a new property to treat the active-high case.
>
> In next we should fix it correctly, apply Krzysztof's patch and fix broken
> DTBs, right?
>
We can and should fix broken DTs, but keeping DT stability means we need
to be able to support old (unfixed) DTs with future kernels.
So we can not just fix the DTs and move on, as kernel and DT are two
separate entities, even if they are currently distributed through the
same source tree.
Regards,
Lucas
next prev parent reply other threads:[~2016-03-30 13:20 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-28 21:45 [PATCH v2] Revert "PCI: imx6: Add support for active-low reset GPIO" Fabio Estevam
2016-03-29 13:43 ` Tim Harvey
2016-03-30 12:21 ` Petr Štetiar
2016-03-30 12:36 ` Fabio Estevam
2016-03-30 13:00 ` Petr Štetiar
2016-03-30 13:07 ` Fabio Estevam
2016-03-30 13:16 ` Petr Štetiar
2016-03-30 13:20 ` Lucas Stach [this message]
2016-03-30 13:25 ` Fabio Estevam
2016-03-31 5:07 ` Krzysztof Hałasa
2016-03-31 10:35 ` Lucas Stach
2016-04-01 7:26 ` Krzysztof Hałasa
2016-03-30 13:29 ` Lucas Stach
2016-04-05 19:10 ` Fabio Estevam
2016-04-05 21:31 ` Bjorn Helgaas
2016-04-05 22:07 ` Fabio Estevam
2016-04-18 2:41 ` Fabio Estevam
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=1459344050.2565.41.camel@pengutronix.de \
--to=l.stach@pengutronix.de \
--cc=Richard.Zhu@freescale.com \
--cc=bhelgaas@google.com \
--cc=fabio.estevam@nxp.com \
--cc=festevam@gmail.com \
--cc=khalasa@piap.pl \
--cc=linux-pci@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=tharvey@gateworks.com \
--cc=ynezz@true.cz \
/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;
as well as URLs for NNTP newsgroup(s).