On Wed, 2018-08-08 at 16:27 +0100, Lorenzo Pieralisi wrote:

On Wed, Aug 08, 2018 at 02:58:15PM +0000, Leonard Crestez wrote:

quoted

On Wed, 2018-08-08 at 15:19 +0100, Lorenzo Pieralisi wrote:

quoted

On Wed, Aug 08, 2018 at 11:37:14AM +0000, Leonard Crestez wrote:

quoted

On Wed, 2018-08-08 at 12:14 +0100, Lorenzo Pieralisi wrote:

quoted

On Wed, Aug 08, 2018 at 10:53:52AM +0000, Leonard Crestez wrote:

quoted

On Tue, 2018-07-24 at 19:14 +0300, Leonard Crestez wrote:

quoted

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.

This needs further clarification: without the reset patch this will
hang on imx7 suspend/resume but this is the current behavior anyway.

Both patches are required for imx7 pci suspend and including them out
of order shouldn't break unrelated functionality.

So it should actually be fine to just include the pci changes now,
right?