From patchwork Thu Nov 2 23:15:49 2017 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Florian Fainelli X-Patchwork-Id: 833568 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" (2048-bit key; unprotected) header.d=gmail.com header.i=@gmail.com header.b="ETlmydkk"; dkim-atps=neutral Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by ozlabs.org (Postfix) with ESMTP id 3ySgvl5lJfz9s8J for ; Fri, 3 Nov 2017 10:16:51 +1100 (AEDT) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S934390AbdKBXQu (ORCPT ); Thu, 2 Nov 2017 19:16:50 -0400 Received: from mail-wr0-f194.google.com ([209.85.128.194]:50807 "EHLO mail-wr0-f194.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932201AbdKBXQt (ORCPT ); Thu, 2 Nov 2017 19:16:49 -0400 Received: by mail-wr0-f194.google.com with SMTP id p96so1024043wrb.7; Thu, 02 Nov 2017 16:16:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:cc:subject:date:message-id; bh=/ddcnHsGSJ2zaBFBt0WAN6A8wSKl6eZ5uC+moK1NYLk=; b=ETlmydkkaRw6Uky5OhHiFSMc0Kc9GEBWWwk56EM4OphT2FTSy7+EQziRkBpjQuQAvO FZavDGnFhI8Vg3JAE091+CEQ85Nchim7WsLBvuEpztnhFxpUfkVMwrzf8AmnbgQMyPg4 uxagIKoxCTn/jJS7ZLEN8lYr1TUQ/aiWdDaS1LJ/4Khe9K77zc252QZR36hnuWGnswzU WXhSAKYZol0FfLPer2R2jFqHRqykyehxKIN6DfnKdKnr5akJUCPdh9iVanFSXpl/i1AS Q1BpUGrBDLYB314JlgM3WOYlHYgxFfWEeqp71vTUSxE4fYu7j3mxMogsXXJozDDlX2Uj gePw== 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=/ddcnHsGSJ2zaBFBt0WAN6A8wSKl6eZ5uC+moK1NYLk=; b=SwNMRevYX8rUtcSGnPZl7EgR8S7ieoVIU6+Yxs0YWjiRcDUhpSRo0SrcHYvtvCfDhT 9G37/rfJUdUOre3rz4cmuHpRZgyP6FmWa19ljQXvlLoAmtSRthJh02uCGgiPeyxpmXF9 EDRpEVPOjplQV3idm1flwbdGsPtU6GDzSWFQUVer9ywlaP8KVWhqWg8eGKXbPhg4xQbW OkAXKxqEEwndznvNymgV+qplMIGMhU9j53lCnEz1naelWws0xfblIr6XXnfy87UgnQ1v Yzhu22WrUm9F0RnEQP6a9SKtghE98Ax5tpbs53FjoBTGm+NNvGlwN+dD9LZN6bBWCo2g FC4A== X-Gm-Message-State: AMCzsaVvto41fwVKXX7TcggiwpzVvH2sce0qChqNl3CQN8+8iTesoVnh QKW+j71eX6gjWaHM3xgGbiY0Q5Hi X-Google-Smtp-Source: ABhQp+QXsK7EBP6LVhphx7TkRZaN6gy46hIEJYR4VlsT0a1m4eTkYjEhxNw6gwmDTMc2UsflyOuE9A== X-Received: by 10.223.163.208 with SMTP id m16mr4747319wrb.63.1509664607528; Thu, 02 Nov 2017 16:16:47 -0700 (PDT) Received: from fainelli-desktop.broadcom.com ([192.19.255.250]) by smtp.gmail.com with ESMTPSA id o8sm2618177wrc.10.2017.11.02.16.16.43 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 02 Nov 2017 16:16:46 -0700 (PDT) From: Florian Fainelli To: linux-gpio@vger.kernel.org Cc: Florian Fainelli , Linus Walleij , Rob Herring , Mark Rutland , devicetree@vger.kernel.org (open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS), linux-kernel@vger.kernel.org (open list), ckeepax@opensource.cirrus.com, tony@atomide.com, ckeepax@opensource.wolfsonmicro.com, swarren@nvidia.com, andy.shevchenko@gmail.com, alcooperx@gmail.com, bcm-kernel-feedback-list@broadcom.com Subject: [PATCH v2 0/2] pinctrl: Allow indicating loss of state across suspend/resume Date: Thu, 2 Nov 2017 16:15:49 -0700 Message-Id: <20171102231551.16220-1-f.fainelli@gmail.com> X-Mailer: git-send-email 2.9.3 Sender: linux-gpio-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-gpio@vger.kernel.org Hello Linus, It's me again, so I have been thinking about the problem originally reported in: [PATCH fixes v3] pinctrl: Really force states during suspend/resume and other similar patches a while ago, and this new version allows a platform using pinctrl-single to specify whether its pins are going to lose their state during a system deep sleep. Note that this is still checked at the pinctrl_select_state() because consumers of the pinctrl API might be calling this from their suspend/resume functions and should not have to know whether the provider does lose its pin states. This is against your pinctrl/for-next branch. Thanks! Changes in v2: - make the property generic and not specific to pinctrl-single Florian Fainelli (2): pinctrl: Allow a device to indicate when to force a state pinctrl: Allow indicating loss of pin states during low-power .../devicetree/bindings/pinctrl/pinctrl-bindings.txt | 4 ++++ drivers/pinctrl/core.c | 17 ++++++++++++++++- drivers/pinctrl/core.h | 4 ++++ 3 files changed, 24 insertions(+), 1 deletion(-)