From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753716AbdBUQhQ (ORCPT ); Tue, 21 Feb 2017 11:37:16 -0500 Received: from mail-it0-f68.google.com ([209.85.214.68]:36178 "EHLO mail-it0-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753926AbdBUQgp (ORCPT ); Tue, 21 Feb 2017 11:36:45 -0500 MIME-Version: 1.0 In-Reply-To: <20170221110730.GF5021@amd> References: <1487622809-25127-1-git-send-email-geert+renesas@glider.be> <1487622809-25127-5-git-send-email-geert+renesas@glider.be> <20170221110730.GF5021@amd> From: Geert Uytterhoeven Date: Tue, 21 Feb 2017 17:36:38 +0100 X-Google-Sender-Auth: 2mKIlyarFt-8M9NLhKiM5x1Dm4I Message-ID: Subject: Re: [PATCH/RFC 4/6] drivers: firmware: psci: Fix non-PMIC wake-up if SYSTEM_SUSPEND cuts power To: Pavel Machek Cc: Geert Uytterhoeven , Lorenzo Pieralisi , Mark Rutland , Sudeep Holla , Lina Iyer , John Stultz , Thomas Gleixner , "Rafael J . Wysocki" , Len Brown , Rob Herring , Magnus Damm , "devicetree@vger.kernel.org" , "linux-arm-kernel@lists.infradead.org" , Linux-Renesas , Linux PM list , "linux-kernel@vger.kernel.org" Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Pavel, On Tue, Feb 21, 2017 at 12:07 PM, Pavel Machek wrote: > On Mon 2017-02-20 21:33:27, Geert Uytterhoeven wrote: >> Nothing in the PSCI specification requires the SoC to remain powered and >> to support wake-up sources when suspended using SYSTEM_SUSPEND. >> If the firmware implements the PSCI SYSTEM_SUSPEND operation by cutting >> power to the SoC, the only possibly wake-up sources are thus the ones >> connected to the PMIC. >> >> Document and add support for an "arm,psci-system-suspend-is-power-down" >> DT property, so Linux uses a different suspend method when other wake-up >> sources (e.g. wake on LAN, UART or GPIO) are enabled. > > Should we make PSCI return that information? (At least in next > specification version?) That's a possible solution. Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds From mboxrd@z Thu Jan 1 00:00:00 1970 From: Geert Uytterhoeven Subject: Re: [PATCH/RFC 4/6] drivers: firmware: psci: Fix non-PMIC wake-up if SYSTEM_SUSPEND cuts power Date: Tue, 21 Feb 2017 17:36:38 +0100 Message-ID: References: <1487622809-25127-1-git-send-email-geert+renesas@glider.be> <1487622809-25127-5-git-send-email-geert+renesas@glider.be> <20170221110730.GF5021@amd> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Return-path: In-Reply-To: <20170221110730.GF5021@amd> Sender: linux-renesas-soc-owner@vger.kernel.org To: Pavel Machek Cc: Geert Uytterhoeven , Lorenzo Pieralisi , Mark Rutland , Sudeep Holla , Lina Iyer , John Stultz , Thomas Gleixner , "Rafael J . Wysocki" , Len Brown , Rob Herring , Magnus Damm , "devicetree@vger.kernel.org" , "linux-arm-kernel@lists.infradead.org" , Linux-Renesas , Linux PM list , "linux-kernel@vger.kernel.org" List-Id: devicetree@vger.kernel.org Hi Pavel, On Tue, Feb 21, 2017 at 12:07 PM, Pavel Machek wrote: > On Mon 2017-02-20 21:33:27, Geert Uytterhoeven wrote: >> Nothing in the PSCI specification requires the SoC to remain powered and >> to support wake-up sources when suspended using SYSTEM_SUSPEND. >> If the firmware implements the PSCI SYSTEM_SUSPEND operation by cutting >> power to the SoC, the only possibly wake-up sources are thus the ones >> connected to the PMIC. >> >> Document and add support for an "arm,psci-system-suspend-is-power-down" >> DT property, so Linux uses a different suspend method when other wake-up >> sources (e.g. wake on LAN, UART or GPIO) are enabled. > > Should we make PSCI return that information? (At least in next > specification version?) That's a possible solution. Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds From mboxrd@z Thu Jan 1 00:00:00 1970 From: geert@linux-m68k.org (Geert Uytterhoeven) Date: Tue, 21 Feb 2017 17:36:38 +0100 Subject: [PATCH/RFC 4/6] drivers: firmware: psci: Fix non-PMIC wake-up if SYSTEM_SUSPEND cuts power In-Reply-To: <20170221110730.GF5021@amd> References: <1487622809-25127-1-git-send-email-geert+renesas@glider.be> <1487622809-25127-5-git-send-email-geert+renesas@glider.be> <20170221110730.GF5021@amd> Message-ID: To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org Hi Pavel, On Tue, Feb 21, 2017 at 12:07 PM, Pavel Machek wrote: > On Mon 2017-02-20 21:33:27, Geert Uytterhoeven wrote: >> Nothing in the PSCI specification requires the SoC to remain powered and >> to support wake-up sources when suspended using SYSTEM_SUSPEND. >> If the firmware implements the PSCI SYSTEM_SUSPEND operation by cutting >> power to the SoC, the only possibly wake-up sources are thus the ones >> connected to the PMIC. >> >> Document and add support for an "arm,psci-system-suspend-is-power-down" >> DT property, so Linux uses a different suspend method when other wake-up >> sources (e.g. wake on LAN, UART or GPIO) are enabled. > > Should we make PSCI return that information? (At least in next > specification version?) That's a possible solution. Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert at linux-m68k.org In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds