From mboxrd@z Thu Jan 1 00:00:00 1970 From: Leonard Crestez Subject: Re: [PATCH v4 0/6] PCI: imx: Initial imx7d suspend/resume support Date: Mon, 17 Sep 2018 16:01:21 +0000 Message-ID: <16d68541fd499dfda88e79d4386be7ad6d0919d9.camel@nxp.com> References: <20180917150941.GH7239@e107981-ln.cambridge.arm.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20180917150941.GH7239@e107981-ln.cambridge.arm.com> Content-Language: en-US Content-ID: <1053A0F5F2F184499B4BED2BF7DB069A@eurprd04.prod.outlook.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=m.gmane.org@lists.infradead.org To: "l.stach@pengutronix.de" , "lorenzo.pieralisi@arm.com" , "andrew.smirnov@gmail.com" Cc: "mark.rutland@arm.com" , "devicetree@vger.kernel.org" , "Joao.Pinto@synopsys.com" , Richard Zhu , "kernel@pengutronix.de" , Anson Huang , "jingoohan1@gmail.com" , "linux-kernel@vger.kernel.org" , "robh+dt@kernel.org" , dl-linux-imx , "p.zabel@pengutronix.de" , "linux-pci@vger.kernel.org" , "bhelgaas@google.com" , "shawnguo@kernel.org" , "linux-arm-kernel@lists.infradead.org" List-Id: devicetree@vger.kernel.org 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