From patchwork Fri Dec 29 13:31:41 2017 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Ulf Hansson X-Patchwork-Id: 853917 Return-Path: X-Original-To: incoming@patchwork.ozlabs.org Delivered-To: patchwork-incoming@bilbo.ozlabs.org Authentication-Results: ozlabs.org; spf=none (mailfrom) smtp.mailfrom=vger.kernel.org (client-ip=209.132.180.67; helo=vger.kernel.org; envelope-from=linux-gpio-owner@vger.kernel.org; receiver=) Authentication-Results: ozlabs.org; dkim=fail reason="signature verification failed" (1024-bit key; unprotected) header.d=linaro.org header.i=@linaro.org header.b="BNHm8qC7"; dkim-atps=neutral Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by ozlabs.org (Postfix) with ESMTP id 3z7SFd4XBBz9s7g for ; Sat, 30 Dec 2017 00:32:53 +1100 (AEDT) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1750905AbdL2Nb5 (ORCPT ); Fri, 29 Dec 2017 08:31:57 -0500 Received: from mail-lf0-f68.google.com ([209.85.215.68]:33245 "EHLO mail-lf0-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750831AbdL2Nbz (ORCPT ); Fri, 29 Dec 2017 08:31:55 -0500 Received: by mail-lf0-f68.google.com with SMTP id j143so2880943lfg.0 for ; Fri, 29 Dec 2017 05:31:55 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=from:to:cc:subject:date:message-id; bh=lojZXSfdhbNDet1sOf3QtDFmjpLWKpTirmu/AEYK9lU=; b=BNHm8qC7sueVL8M1Oc74a7Jg7+JFBM8r1ZRsZ6NfZMLOzbNJHlKDrnxykWSkRl8ZZW Zad+LWM/gdO8rybxC2k6JeuAizgHOscv6e6ZX5Q5Ve9YmXalvOGp23zeVrjPUw2qaO0u D8Z8XTOqx0xwrtp1sSvbkhN7wjWLkc8r4WrVg= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id; bh=lojZXSfdhbNDet1sOf3QtDFmjpLWKpTirmu/AEYK9lU=; b=Vv+Fo/XkN3+seCiMotzPrlVBTcxpvYI+xgcRJzeE2paQGqc8Y5tJZsJzLTWGbElhDM 6IuBHJBFl59zALnFr2YlaKl7oyPbauJutauT22uOcZXyB5N9+q1FsjxJ6qspdufLyKOb f1cQOe9wfPxK0mvKaxI9F3pQzARfcUY/PKlbGOmLvVNw5AWj0YOBhdKiyFpLezFyGVDj n+Sw8XfRADtdF+uTejpBfPEMO8cScIoa4xv1NDduAmGcx1KuKio9laHsS6ooqs5/yRdk oKRTOWA6Yo0qz1XAjqBH5y+X7+/NPPHQM8xCFaH3n3qnIGhr6xhB+Rre4aIN7hCmga1C zyTg== X-Gm-Message-State: AKGB3mLAHtz/19zHm4TKXkI07Z0S95wHawGai1Y4csZKq3Ts5xev1N93 XJ5KcrlXRQlcYJsrbgiRcLcfOw== X-Google-Smtp-Source: ACJfBougnEPsDzOfFAxeird5oYH1sWrrzGQmus512EqLyz0n0nl5FCqHQTSzCDH6fiiRVMo5J4MKJw== X-Received: by 10.46.88.77 with SMTP id x13mr20066948ljd.80.1514554314501; Fri, 29 Dec 2017 05:31:54 -0800 (PST) Received: from localhost.localdomain (h-158-174-22-67.NA.cust.bahnhof.se. [158.174.22.67]) by smtp.gmail.com with ESMTPSA id e72sm7521063lji.63.2017.12.29.05.31.53 (version=TLS1_2 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Fri, 29 Dec 2017 05:31:53 -0800 (PST) From: Ulf Hansson To: "Rafael J . Wysocki" , linux-pm@vger.kernel.org Cc: Thomas Gleixner , Jason Cooper , Marc Zyngier , Linus Walleij , Simon Horman , Niklas Soderlund , Geert Uytterhoeven , Ulf Hansson , linux-renesas-soc@vger.kernel.org, linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org Subject: [PATCH v2 0/3] renesas: irqchip: Use WAKEUP_PATH driver PM flag Date: Fri, 29 Dec 2017 14:31:41 +0100 Message-Id: <1514554304-18989-1-git-send-email-ulf.hansson@linaro.org> X-Mailer: git-send-email 2.7.4 Sender: linux-gpio-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-gpio@vger.kernel.org From: Geert Uytterhoeven Changes in v2: [By Ulf Hansson] - I have picked up the series from Geert [1] and converted it into use the WAKEUP_PATH driver PM flag. This includes some minor changes to each patch and updates to the changelogs. - An important note, the WAKEUP_PATH driver PM flag is introduced in a separate series [2], not yet applied, so @subject series depends on it. - One more note, two of the patches has a checkpatch error, however I did not fix them, becuase I think that should be done separate. [1] https://lkml.org/lkml/2017/11/9/382 [2] https://marc.info/?l=linux-pm&m=151454744124661&w=2 More information below, picked from Geert's previous cover letter. Kind regards Uffe Hi all, If an interrupt controller in a Renesas ARM SoC is part of a Clock Domain, and it is part of the wakeup path, it must be kept active during system suspend. Currently this is handled in all interrupt controller drivers by explicitly increasing the use count of the module clock when the device is part of the wakeup path. However, this explicit clock handling is merely a workaround for a failure to properly communicate wakeup information to the device core. Hence this series fixes the affected drivers by setting the devices' power.wakeup_path fields instead, to indicate they are part of the wakeup path. Depending on the PM Domain's active_wakeup configuration, the genpd core code will keep the device enabled (and the clock running) during system suspend when needed. Note that most of these patches depend on the series "[PATCH v2 0/3] PM / Domain: renesas: Fix active wakeup behavior", hence they should not be applied yet. This has been tested on r8a73a4/ape6evm, r8a7740/armadillo, r8a7791/koelsch, r8a7795/salvator-x and -xs, r8a7796/salvator-x, and sh73a0/kzm9g. Thanks for your comments! Geert Uytterhoeven (3): irqchip/renesas-intc-irqpin: Use WAKEUP_PATH driver PM flag irqchip/renesas-irqc: Use WAKEUP_PATH driver PM flag gpio: rcar: Use WAKEUP_PATH driver PM flag drivers/gpio/gpio-rcar.c | 40 +++++++++++------------------ drivers/irqchip/irq-renesas-intc-irqpin.c | 42 +++++++++++-------------------- drivers/irqchip/irq-renesas-irqc.c | 32 +++++++++++------------ 3 files changed, 45 insertions(+), 69 deletions(-)