From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.3 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,USER_AGENT_SANE_2 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 69972C4CEC4 for ; Sat, 21 Sep 2019 09:23:25 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 473FE218AE for ; Sat, 21 Sep 2019 09:23:25 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2393032AbfIUJXY convert rfc822-to-8bit (ORCPT ); Sat, 21 Sep 2019 05:23:24 -0400 Received: from relay1-d.mail.gandi.net ([217.70.183.193]:34957 "EHLO relay1-d.mail.gandi.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2391840AbfIUJXY (ORCPT ); Sat, 21 Sep 2019 05:23:24 -0400 X-Originating-IP: 91.224.148.103 Received: from xps13 (unknown [91.224.148.103]) (Authenticated sender: miquel.raynal@bootlin.com) by relay1-d.mail.gandi.net (Postfix) with ESMTPSA id ABD2B240003; Sat, 21 Sep 2019 09:23:19 +0000 (UTC) Date: Sat, 21 Sep 2019 11:23:18 +0200 From: Miquel Raynal To: Stephen Boyd Cc: Mark Rutland , Michael Turquette , Rob Herring , linux-clk@vger.kernel.org, devicetree@vger.kernel.org, Thomas Petazzoni , Antoine Tenart , Gregory Clement , Maxime Chevallier , Nadav Haklai , Bjorn Helgaas , "Rafael J . Wysocki" , linux-pm@vger.kernel.org, Subject: Re: [PATCH v3 0/4] Prepare Armada 3700 PCIe suspend to RAM support Message-ID: <20190921112318.46d0372c@xps13> In-Reply-To: <20190920165402.4B5DB207FC@mail.kernel.org> References: <20190627125245.26788-1-miquel.raynal@bootlin.com> <20190917173154.722CB2171F@mail.kernel.org> <20190920100301.0674a5b6@xps13> <20190920165402.4B5DB207FC@mail.kernel.org> Organization: Bootlin X-Mailer: Claws Mail 3.17.3 (GTK+ 2.24.32; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8BIT Sender: linux-pm-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-pm@vger.kernel.org Hi Stephen, Stephen Boyd wrote on Fri, 20 Sep 2019 09:54:01 -0700: > Quoting Miquel Raynal (2019-09-20 01:03:01) > > Hi Stephen, > > > > Stephen Boyd wrote on Tue, 17 Sep 2019 10:31:53 > > -0700: > > > > > Quoting Miquel Raynal (2019-06-27 05:52:41) > > > > Hello, > > > > > > > > As part of an effort to bring suspend to RAM support to the Armada > > > > 3700 SoC (main target: ESPRESSObin board), there are small things to > > > > do in the Armada 3700 peripherals clock driver: > > > > > > > > * On this SoC, the PCIe controller gets fed by a gated clock in the > > > > south bridge. This clock is missing in the current driver, patch 1 > > > > adds it. > > > > > > > > * Because of a constraint in the PCI core, the resume function of a > > > > PCIe controller driver must be run at an early stage > > > > (->suspend/resume_noirq()), before the core tries to ->read/write() > > > > in the PCIe registers to do more configuration. Hence, the PCIe > > > > clock must be resumed before. This is enforced thanks to two > > > > changes: > > > > 1/ Add device links to the clock framework. This enforce order in > > > > the PM core: the clocks are resumed before the consumers. Series > > > > has been posted, see [1]. > > > > 2/ Even with the above feature, the clock's resume() callback is > > > > called after the PCI controller's resume_noirq() callback. The > > > > only way to fix this is to change the "priority" of the clock > > > > suspend/resume callbacks. This is done in patch 2. > > > > > > > > * The bindings are updated with the PCI clock in patch 4 while patch 3 > > > > is just a typo correction in the same file. > > > > > > > > If there is anything unclear please feel free to ask. > > > > > > > > > > Should I drop this patch series? > > > > > > > No, if it is right for you I would really prefer to have it merged > > (sorry for the delay in answering though) because it will be still > > needed, no matter how clock dependencies are handled. > > > > > > Ok. I'll apply it after the merge window. Let me know if it's more > urgent than that. > No it's not, 5.5 is fine. Thanks, Miquèl