From: Leonard Crestez <leonard.crestez@nxp.com>
To: "p.zabel@pengutronix.de" <p.zabel@pengutronix.de>,
"lorenzo.pieralisi@arm.com" <lorenzo.pieralisi@arm.com>
Cc: dl-linux-imx <linux-imx@nxp.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Richard Zhu <hongxing.zhu@nxp.com>,
"jingoohan1@gmail.com" <jingoohan1@gmail.com>,
"A.s. Dong" <aisheng.dong@nxp.com>,
Fabio Estevam <fabio.estevam@nxp.com>,
"Joao.Pinto@synopsys.com" <Joao.Pinto@synopsys.com>,
"shawnguo@kernel.org" <shawnguo@kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"andrew.smirnov@gmail.com" <andrew.smirnov@gmail.com>,
Anson Huang <anson.huang@nxp.com>,
"bhelgaas@google.com" <bhelgaas@google.com>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
"l.stach@pengutronix.de" <l.stach@pengutronix.de>,
"kernel@pengutronix.de" <kernel@pengutronix.de>
Subject: Re: [PATCH v3 0/2] PCI: imx: Initial imx7d pm support
Date: Wed, 8 Aug 2018 14:58:15 +0000 [thread overview]
Message-ID: <efd9c1d560cae84e2a4ee7585a4c61d5d40ba755.camel@nxp.com> (raw)
In-Reply-To: <20180808141938.GA30428@e107981-ln.cambridge.arm.com>
On Wed, 2018-08-08 at 15:19 +0100, Lorenzo Pieralisi wrote:
> On Wed, Aug 08, 2018 at 11:37:14AM +0000, Leonard Crestez wrote:
> > On Wed, 2018-08-08 at 12:14 +0100, Lorenzo Pieralisi wrote:
> > > On Wed, Aug 08, 2018 at 10:53:52AM +0000, Leonard Crestez wrote:
> > > > On Tue, 2018-07-24 at 19:14 +0300, Leonard Crestez wrote:
> > > > > Changes since v2:
> > > > > * Print with dev_info if link fails on resume (Lucas)
> > > > > * Add a comment on imx7d pci irq mappings (Andrey)
> > > > > * Make imx6_pcie_ltssm_disable print an error on IMX6Q (Lucas)
> > > > >
> > > > > The ltssm_disable does not return an error because it can't be usefully
> > > > > handled, reversing partial suspend is a nightmare and unlikely to work.
> > > > >
> > > > > * Drop "reset: imx7: Fix always writing bits as 0 (accepted by Philipp)
> > > > >
> > > > > Series is against linux-next tag next-20180724 where the reset patch was
> > > > > already accepted. The imx7d.dtsi patch is also useful standalone.
> > > >
> > > > This is a gentle reminder that this series was reviewed by Lucas two
> > > > weeks ago but not yet included.
> > >
> > > Does this series have a functional dependency on the reset fix ? If yes
> > > we can have a bisection proplem depending on which tree gets merged
> > > first.
> >
> > Yes, without the reset fix I expect hangs.
> >
> > Maybe the reset fix should be pulled in the pci tree? I don't know how
> > these issues are sorted out.
>
> Well either I pull that fix into the PCI tree (but it is already -rc8
> and I can't guarantee v4.19 inclusion - I shall try) or I can ack these
> patches and Philippe will send them upstream on my behalf, atop the
> reset fix above.
>
> When will the reset fix will be sent to Linus ? Please let me know
> how you want to proceed.
I have some other unsent changes for imx pci+dts+reset standing by.
Since these changes qualify more as "pm features" than fixes I don't
really mind skipping 4.19.
Pulling pci features into the reset tree doesn't make much sense to me.
Maybe this kind of stuff could go through Shawn's tree? There shouldn't
be any interaction with non-imx stuff.
next prev parent reply other threads:[~2018-08-08 14:58 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-24 16:14 Leonard Crestez
2018-07-24 16:14 ` [PATCH v3 1/2] Revert "ARM: dts: imx7d: Invert legacy PCI irq mapping" Leonard Crestez
2018-07-24 16:52 ` Lucas Stach
2018-08-21 15:31 ` Shawn Guo
2018-07-24 16:14 ` [PATCH v3 2/2] PCI: imx: Initial imx7d pm support Leonard Crestez
2018-07-24 16:55 ` Lucas Stach
2018-08-08 10:53 ` [PATCH v3 0/2] " Leonard Crestez
2018-08-08 11:14 ` Lorenzo Pieralisi
2018-08-08 11:37 ` Leonard Crestez
2018-08-08 14:19 ` Lorenzo Pieralisi
2018-08-08 14:58 ` Leonard Crestez [this message]
2018-08-08 15:27 ` Lorenzo Pieralisi
2018-08-10 11:11 ` Leonard Crestez
2018-08-10 15:13 ` Lorenzo Pieralisi
2018-08-21 15:26 ` Shawn Guo
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=efd9c1d560cae84e2a4ee7585a4c61d5d40ba755.camel@nxp.com \
--to=leonard.crestez@nxp.com \
--cc=Joao.Pinto@synopsys.com \
--cc=aisheng.dong@nxp.com \
--cc=andrew.smirnov@gmail.com \
--cc=anson.huang@nxp.com \
--cc=bhelgaas@google.com \
--cc=fabio.estevam@nxp.com \
--cc=hongxing.zhu@nxp.com \
--cc=jingoohan1@gmail.com \
--cc=kernel@pengutronix.de \
--cc=l.stach@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=p.zabel@pengutronix.de \
--cc=shawnguo@kernel.org \
/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
all inboxes | Powered by JetHome®