From: Leonard Crestez <leonard.crestez@nxp.com> To: "l.stach@pengutronix.de" <l.stach@pengutronix.de>, "lorenzo.pieralisi@arm.com" <lorenzo.pieralisi@arm.com>, "andrew.smirnov@gmail.com" <andrew.smirnov@gmail.com> Cc: "mark.rutland@arm.com" <mark.rutland@arm.com>, "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>, "Joao.Pinto@synopsys.com" <Joao.Pinto@synopsys.com>, Richard Zhu <hongxing.zhu@nxp.com>, "kernel@pengutronix.de" <kernel@pengutronix.de>, Anson Huang <anson.huang@nxp.com>, "jingoohan1@gmail.com" <jingoohan1@gmail.com>, "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>, "robh+dt@kernel.org" <robh+dt@kernel.org>, dl-linux-imx <linux-imx@nxp.com>, "p.zabel@pengutronix.de" <p.zabel@pengutronix.de>, "linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>, "bhelgaas@google.com" <bhelgaas@google.com>, "shawnguo@kernel.org" <shawnguo@kernel.org>, "linux-arm-kernel@lists.infradead.org" <linux-arm-kernel@lists.infradead.org> Subject: Re: [PATCH v4 0/6] PCI: imx: Initial imx7d suspend/resume support Date: Mon, 17 Sep 2018 16:01:21 +0000 [thread overview] Message-ID: <16d68541fd499dfda88e79d4386be7ad6d0919d9.camel@nxp.com> (raw) In-Reply-To: <20180917150941.GH7239@e107981-ln.cambridge.arm.com> On Mon, 2018-09-17 at 16:09 +0100, Lorenzo Pieralisi wrote: > On Tue, Aug 14, 2018 at 07:50:14PM +0300, Leonard Crestez wrote: > > V4 adds 4 more patches with PME_Turn_Off support on top, using a new > > reset bit. I generally try to keep series short but in this case some > > planning might be needed to get patches into 4.20. > > > > Since the new reset is treated as optional with old DTB there should be > > again no problem if reset and pci are merged out of order. > > > > Shawn/Philipp/Lorenzo: Would it make sense to merge this series through a > > single specific tree, such as the one for imx? > > This series is a bit of a mixture of multiple things hard to discern > (actually I already merged patch 2 and patch 1 seems completely > unrelated). > > I would take the series through the PCI tree but I need an ACK for > patches 5 and 6, please let me know how you want to handle it. Patches 1 and 2 are already in, the rest need review. I can now just resend patches 3-6 as a separate series, unless somebody complains about spam. Multiple separate patches are required because it touches reset + dt + pci. I guess adding the include constant should be moved from the dts patch to dt-bindings though. Merging reset and pci out of order should be fine here and is required by DT compatibility rules anyway. -- Regards, Leonard _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Leonard Crestez <leonard.crestez@nxp.com> To: "l.stach@pengutronix.de" <l.stach@pengutronix.de>, "lorenzo.pieralisi@arm.com" <lorenzo.pieralisi@arm.com>, "andrew.smirnov@gmail.com" <andrew.smirnov@gmail.com> Cc: Richard Zhu <hongxing.zhu@nxp.com>, dl-linux-imx <linux-imx@nxp.com>, "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>, "robh+dt@kernel.org" <robh+dt@kernel.org>, "jingoohan1@gmail.com" <jingoohan1@gmail.com>, "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>, "p.zabel@pengutronix.de" <p.zabel@pengutronix.de>, "mark.rutland@arm.com" <mark.rutland@arm.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>, Anson Huang <anson.huang@nxp.com>, "bhelgaas@google.com" <bhelgaas@google.com>, "linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>, "kernel@pengutronix.de" <kernel@pengutronix.de> Subject: Re: [PATCH v4 0/6] PCI: imx: Initial imx7d suspend/resume support Date: Mon, 17 Sep 2018 16:01:21 +0000 [thread overview] Message-ID: <16d68541fd499dfda88e79d4386be7ad6d0919d9.camel@nxp.com> (raw) Message-ID: <20180917160121.1ebGKE7tBXReYYp90py67Cb0JXj_rXdvq8nkZtjITzc@z> (raw) In-Reply-To: <20180917150941.GH7239@e107981-ln.cambridge.arm.com> On Mon, 2018-09-17 at 16:09 +0100, Lorenzo Pieralisi wrote: > On Tue, Aug 14, 2018 at 07:50:14PM +0300, Leonard Crestez wrote: > > V4 adds 4 more patches with PME_Turn_Off support on top, using a new > > reset bit. I generally try to keep series short but in this case some > > planning might be needed to get patches into 4.20. > > > > Since the new reset is treated as optional with old DTB there should be > > again no problem if reset and pci are merged out of order. > > > > Shawn/Philipp/Lorenzo: Would it make sense to merge this series through a > > single specific tree, such as the one for imx? > > This series is a bit of a mixture of multiple things hard to discern > (actually I already merged patch 2 and patch 1 seems completely > unrelated). > > I would take the series through the PCI tree but I need an ACK for > patches 5 and 6, please let me know how you want to handle it. Patches 1 and 2 are already in, the rest need review. I can now just resend patches 3-6 as a separate series, unless somebody complains about spam. Multiple separate patches are required because it touches reset + dt + pci. I guess adding the include constant should be moved from the dts patch to dt-bindings though. Merging reset and pci out of order should be fine here and is required by DT compatibility rules anyway. -- Regards, Leonard
next prev parent reply other threads:[~2018-09-17 16:01 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-08-14 16:50 [PATCH v4 0/6] PCI: imx: Initial imx7d suspend/resume support Leonard Crestez 2018-08-14 16:50 ` [PATCH v4 1/6] Revert "ARM: dts: imx7d: Invert legacy PCI irq mapping" Leonard Crestez 2018-08-14 16:50 ` [PATCH v4 2/6] PCI: imx: Initial imx7d pm support Leonard Crestez 2018-08-14 16:50 ` [PATCH v4 3/6] reset: imx7: Add PCIE_CTRL_APPS_TURNOFF Leonard Crestez 2018-08-15 20:24 ` Rob Herring 2018-08-14 16:50 ` [PATCH v4 4/6] dt-bindings: imx6q-pcie: Add turnoff reset for imx7d Leonard Crestez 2018-08-15 20:26 ` Rob Herring 2018-08-14 16:50 ` [PATCH v4 5/6] ARM: dts: imx7d: Add turnoff reset Leonard Crestez 2018-09-25 9:20 ` Shawn Guo 2018-08-14 16:50 ` [PATCH v4 6/6] PCI: imx: Add PME_Turn_Off support Leonard Crestez 2018-09-17 15:09 ` [PATCH v4 0/6] PCI: imx: Initial imx7d suspend/resume support Lorenzo Pieralisi 2018-09-17 15:09 ` Lorenzo Pieralisi 2018-09-17 16:01 ` Leonard Crestez [this message] 2018-09-17 16:01 ` Leonard Crestez 2018-09-17 16:52 ` Lorenzo Pieralisi 2018-09-17 16:52 ` Lorenzo Pieralisi 2018-09-17 17:15 ` Leonard Crestez 2018-09-17 17:15 ` Leonard Crestez
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=16d68541fd499dfda88e79d4386be7ad6d0919d9.camel@nxp.com \ --to=leonard.crestez@nxp.com \ --cc=Joao.Pinto@synopsys.com \ --cc=andrew.smirnov@gmail.com \ --cc=anson.huang@nxp.com \ --cc=bhelgaas@google.com \ --cc=devicetree@vger.kernel.org \ --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=mark.rutland@arm.com \ --cc=p.zabel@pengutronix.de \ --cc=robh+dt@kernel.org \ --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: linkBe 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).