From: khalasa@piap.pl (Krzysztof Hałasa)
To: Lucas Stach <l.stach@pengutronix.de>
Cc: "Fabio Estevam" <festevam@gmail.com>,
"Petr Štetiar" <ynezz@true.cz>,
"Tim Harvey" <tharvey@gateworks.com>,
"Bjorn Helgaas" <bhelgaas@google.com>,
"Richard Zhu" <Richard.Zhu@freescale.com>,
"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: Fri, 01 Apr 2016 09:26:05 +0200 [thread overview]
Message-ID: <m3d1q9iycy.fsf@t19.piap.pl> (raw)
In-Reply-To: <1459420555.17926.6.camel@pengutronix.de> (Lucas Stach's message of "Thu, 31 Mar 2016 12:35:55 +0200")
Lucas Stach <l.stach@pengutronix.de> writes:
> I think you are referring to the GPC interrupt domain change with your
> above statement about DT stability breaking on 4.1/4.2. This is not the
> case. While I only catched the boot regression in the -rc phase of this
> kernel, the final released kernel will boot just fine with an old DTB.
It seems it was the other way around:
BIG FAT WARNING: because the DTs were so far lying by not
exposing the fact that the GPC block is actually the first
interrupt controller in the chain, kernels with this patch
applied wont have any suspend-resume facility when booted
with old DTs, and old kernels with updated DTs won't even boot.
... perhaps combined with something else. I don't remember.
Nevertheless, the ugly DTS entries are just this - ugly. We should have
a way to remove them eventually.
--
Krzysztof Halasa
Industrial Research Institute for Automation and Measurements PIAP
Al. Jerozolimskie 202, 02-486 Warsaw, Poland
next prev parent reply other threads:[~2016-04-01 7:26 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
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 [this message]
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=m3d1q9iycy.fsf@t19.piap.pl \
--to=khalasa@piap.pl \
--cc=Richard.Zhu@freescale.com \
--cc=bhelgaas@google.com \
--cc=fabio.estevam@nxp.com \
--cc=festevam@gmail.com \
--cc=l.stach@pengutronix.de \
--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 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.