From patchwork Mon Nov 21 15:08:43 2022 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Michael Walle X-Patchwork-Id: 23892 Return-Path: Delivered-To: ouuuleilei@gmail.com Received: by 2002:adf:f944:0:0:0:0:0 with SMTP id q4csp1651193wrr; Mon, 21 Nov 2022 07:19:47 -0800 (PST) X-Google-Smtp-Source: AA0mqf5PF3GZhu5+zbGWO0Gos8tzSjA1LImEqwMFGEpMxl3f00kXrdfQCrfkqhbx8wjQ3PwsC3Fo X-Received: by 2002:a17:907:7784:b0:7ad:9ad7:e882 with SMTP id ky4-20020a170907778400b007ad9ad7e882mr3076631ejc.520.1669043987378; Mon, 21 Nov 2022 07:19:47 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1669043987; cv=none; d=google.com; s=arc-20160816; b=RBlKn0oJOi99DFBLNTMeyU4ke1pwAcypD+3/CvjtHyaJlJVhHVJw5+pnWL5Crtzbtn NUgfESVTWT/HL7NFabK8EpYc80NIaEebGnWHV83aggKgBCgVVROH/pTnVhh7FQ6bHgnm VRVDYB1ODppOtvu0P7q/0JlquNUIQfkfPYp6uS1qTjilgI+pDLEodqjs/be+oteYmSEK pGhTWxa4t8ApH2oF/0xULL1FD8YMivdwSpQonIUZUHSW/8Rsg+v+NOOi/3pVTkmF2jMP 0jdWO/H7hgkHGVSQPprMzWggZQAlWJtlLpX0pm05tU1owNh5SmERaTZiYEsribQd3iuC M9mw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :references:in-reply-to:message-id:date:subject:cc:to:from :dkim-signature; bh=leF0rqvNFin/1YVVB08bOiO69am1F2uIpeYktbX9kXM=; b=QFG8XF3c77JI8OTz2gsZI2zDLwSxN4qAHc1P2d9yM3DZoK2Frj0TC2s66rTWDXtZy9 dZVJSJYIym/M4+/876S1knFThb9FyKnwTGJdrbXi1GL1KIigGPLljSPNPLLMtXkphTik O6KUvCen23+1p4JAHIII2qdxKTetu2WBkiq4eF3uPR6OcreTIoA5mmwJtyVi9WQRIpxf lzPA2o65iI3rSrbIdkekIv1ozOH6iWc1MB7fXNEHUMJiPX1eFopAi9uEbMtM0fXDhY24 k77OCfhIh1PPYwOlyBczaV4cHIv8XgX7d0ovO/IqzH3I0nlB+8pR69ICTXQblelI6Ggs Ha6w== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@walle.cc header.s=mail2022082101 header.b=WLEMcral; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=QUARANTINE sp=QUARANTINE dis=NONE) header.from=walle.cc Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id g10-20020a170906538a00b00782539a0286si7915198ejo.142.2022.11.21.07.19.16; Mon, 21 Nov 2022 07:19:47 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@walle.cc header.s=mail2022082101 header.b=WLEMcral; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=QUARANTINE sp=QUARANTINE dis=NONE) header.from=walle.cc Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232192AbiKUPOv (ORCPT + 99 others); Mon, 21 Nov 2022 10:14:51 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:40476 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230396AbiKUPOJ (ORCPT ); Mon, 21 Nov 2022 10:14:09 -0500 Received: from mail.3ffe.de (0001.3ffe.de [159.69.201.130]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id CCB49CFA75; Mon, 21 Nov 2022 07:08:56 -0800 (PST) Received: from mwalle01.kontron.local. (unknown [213.135.10.150]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mail.3ffe.de (Postfix) with ESMTPSA id B1D1B2457; Mon, 21 Nov 2022 16:08:54 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=walle.cc; s=mail2022082101; t=1669043334; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=leF0rqvNFin/1YVVB08bOiO69am1F2uIpeYktbX9kXM=; b=WLEMcralFkvdQ3X3BkLNbp2YryPL/4UP92IPZzQe63g5lsLkTDdVyB/PZDU6+iX1oYE4sf BW6BPDDIMDmnXiv94s+4eWiuQfrXndaAc4zw0bxEh09RSNEZ+mg4IbCYyxYVvBkO81iKQo CavkrLVfelp58iAhn94ypzgH2cAs+Im0ldc3f14zbrlx/Xt6PGTvjJDVqTuZkqLo+y2Dbr CXH4Q40/vrQL/qVT5GrAZfPiOh0VB2z5MBfJ4nEFLD7C84jD4zZhpgMrqGKnvX/qxKD0jE 0EBkQclmUkxOczQS3T6OrQ2WxGOcG+7fYxasq30RgF52Vh3QZHUpHJq1yh+aTQ== From: Michael Walle To: Mark Brown , Greg Kroah-Hartman , "Rafael J . Wysocki" , Linus Walleij , Bartosz Golaszewski Cc: linux-kernel@vger.kernel.org, linux-gpio@vger.kernel.org, William Breathitt Gray , Michael Walle Subject: [PATCH 2/2] gpio: regmap: use new regmap_might_sleep() Date: Mon, 21 Nov 2022 16:08:43 +0100 Message-Id: <20221121150843.1562603-2-michael@walle.cc> X-Mailer: git-send-email 2.30.2 In-Reply-To: <20221121150843.1562603-1-michael@walle.cc> References: <20221121150843.1562603-1-michael@walle.cc> MIME-Version: 1.0 X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,SPF_HELO_NONE,SPF_PASS autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org X-getmail-retrieved-from-mailbox: =?utf-8?q?INBOX?= X-GMAIL-THRID: =?utf-8?q?1750119467666734792?= X-GMAIL-MSGID: =?utf-8?q?1750119467666734792?= Now that the regmap can be queried whether it might sleep, we can get rid of the conservative setting "can_sleep = true". New drivers which want to use gpio-regmap and can access the registers memory-mapped won't have the restriction that their consumers have to use the gpiod_*cansleep() variants anymore. Signed-off-by: Michael Walle --- drivers/gpio/gpio-regmap.c | 10 +--------- 1 file changed, 1 insertion(+), 9 deletions(-) diff --git a/drivers/gpio/gpio-regmap.c b/drivers/gpio/gpio-regmap.c index 6383136cbe59..16404ca6ac38 100644 --- a/drivers/gpio/gpio-regmap.c +++ b/drivers/gpio/gpio-regmap.c @@ -249,15 +249,7 @@ struct gpio_regmap *gpio_regmap_register(const struct gpio_regmap_config *config chip->ngpio = config->ngpio; chip->names = config->names; chip->label = config->label ?: dev_name(config->parent); - - /* - * If our regmap is fast_io we should probably set can_sleep to false. - * Right now, the regmap doesn't save this property, nor is there any - * access function for it. - * The only regmap type which uses fast_io is regmap-mmio. For now, - * assume a safe default of true here. - */ - chip->can_sleep = true; + chip->can_sleep = regmap_might_sleep(config->regmap); chip->get = gpio_regmap_get; if (gpio->reg_set_base && gpio->reg_clr_base)