Received: by 2002:a25:e7d8:0:0:0:0:0 with SMTP id e207csp1563549ybh; Sun, 15 Mar 2020 05:55:43 -0700 (PDT) X-Google-Smtp-Source: ADFU+vvQTP7aNcFX7Hbtv4vRNxLt0JrsoExayEieo9fad6KDfmbZ1ijLyCbQMiRkA8AW72L6EvuU X-Received: by 2002:a9d:82a:: with SMTP id 39mr10614986oty.82.1584276943173; Sun, 15 Mar 2020 05:55:43 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1584276943; cv=none; d=google.com; s=arc-20160816; b=IquUGzM4LphIs5TFpP2oPiGZG3uri5mC2hDIHcLGkpdVYJzPP2Rb7gkux/6CDiDaOJ 0rr+7YiKnwC/lrSqAdVnLPUpSB1heIdeciu4vf9w3KOUzMsjG4fo9qUiX//DuDZT1G8y zbDTZg+ftQn+8BjdGYVi4loTql9Bj0biXYeAlEDiH/8vTudfcq3LaO9pUOLEGweJk+xL 9uQGZhqHZu4KCN1oeiKttRf8p7eNhWxC8772mafRGrQp/Gbj1BZ/PXMps8ra+sfYZP34 dzLf/2dxyPtcIntgBfpuzPNHQCPwiMpXGIciyDoVnW4zOMyX8cduWYHhVWWn6x8spk3A 3wZg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-disposition:mime-version:user-agent:in-reply-to:subject:cc :to:from:message-id:date:dkim-signature:dkim-filter; bh=Is7T8gsczbAflMtpH86ZF4mhjtkMOqN5/wzv7KlnGtc=; b=pcGrnZLGjMm9waejAafue5q4npkmcanftf1OM86UfpIC08VVNnWshtq4Y09dYZywEG 4aXI7cDCAe5T4htKn1yL9LFjAcBwCNO+RbD/VKeEjRmi5RkA1cbpMWh3Hfz/XfUSA2l9 DzF/FGscnfZn9obLksqo7tCfN2gw4QXPpcmNcZRh4v2QT+QwOgRmHmuqjeraNYRSQwMa +6IycLSBew7MekeaKnSNl1EmXuslww3jV26oPoIh4EUXwCDd270saFA69LCkTQ6Zq9Mk 0c+dE+Hwqa6SgP1Io8lR6qzQPeqcIOjWQOV7CSIuZGFjSjhAHQgK8aLjUtHlr11ThGXL m6rA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@vdorst.com header.s=default header.b=kOzIRY1m; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=REJECT sp=REJECT dis=NONE) header.from=vdorst.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id q5si7140171otn.181.2020.03.15.05.55.30; Sun, 15 Mar 2020 05:55:43 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@vdorst.com header.s=default header.b=kOzIRY1m; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=REJECT sp=REJECT dis=NONE) header.from=vdorst.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728548AbgCOMye (ORCPT + 99 others); Sun, 15 Mar 2020 08:54:34 -0400 Received: from mx.0dd.nl ([5.2.79.48]:52546 "EHLO mx.0dd.nl" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728522AbgCOMye (ORCPT ); Sun, 15 Mar 2020 08:54:34 -0400 X-Greylist: delayed 335 seconds by postgrey-1.27 at vger.kernel.org; Sun, 15 Mar 2020 08:54:33 EDT Received: from mail.vdorst.com (mail.vdorst.com [IPv6:fd01::250]) (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 mx.0dd.nl (Postfix) with ESMTPS id 32AD15FB19; Sun, 15 Mar 2020 13:48:57 +0100 (CET) Authentication-Results: mx.0dd.nl; dkim=pass (2048-bit key; secure) header.d=vdorst.com header.i=@vdorst.com header.b="kOzIRY1m"; dkim-atps=neutral Received: from www (www.vdorst.com [192.168.2.222]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.vdorst.com (Postfix) with ESMTPSA id CF07623728F; Sun, 15 Mar 2020 13:48:56 +0100 (CET) DKIM-Filter: OpenDKIM Filter v2.11.0 mail.vdorst.com CF07623728F DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=vdorst.com; s=default; t=1584276536; bh=Is7T8gsczbAflMtpH86ZF4mhjtkMOqN5/wzv7KlnGtc=; h=Date:From:To:Cc:Subject:In-Reply-To:From; b=kOzIRY1mr32lMxMDQcEn9401DmXj1RngdTgPhdC+quRwdtSfJ4U9O8lOjpq7cE/2p 3V43c43Hpew1vvNU0ooQIx5MDF7VELEPayVuSnXqjBLjRtpHy/9N+nlKPDUh9VVRgk eZPdhvkogRf2Hjz6awee9vdt7z6RJ/KGoezDN1ZijC2tHT8c8zRdxTRzc7d5R9K8YY EhhEMi9vHxETmH647fVSacigU5IL+PU6QCUbctesRtssqCY0IzWriFcibaVS+X2E28 ghyEbNG5m1BKMQWjDRu7bG+199F5/HTim2CqP/t6UP3IwVwdhP/iEGEcM0YTxAOnyY or8/9Rj35zovA== Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by www.vdorst.com (Horde Framework) with HTTPS; Sun, 15 Mar 2020 12:48:56 +0000 Date: Sun, 15 Mar 2020 12:48:56 +0000 Message-ID: <20200315124856.Horde.FggCAOBKhyXcJ0kuGBpqX_l@www.vdorst.com> From: =?utf-8?b?UmVuw6k=?= van Dorst To: Chuanhong Guo Cc: linux-gpio@vger.kernel.org, Linus Walleij , Bartosz Golaszewski , Sergio Paracuellos , linux-kernel@vger.kernel.org Subject: Re: [PATCH 0/2] gpio: mmio: introduce BGPIOF_NO_SET_ON_INPUT In-Reply-To: <20200315121338.251362-1-gch981213@gmail.com> User-Agent: Horde Application Framework 5 Content-Type: text/plain; charset=utf-8; format=flowed; DelSp=Yes MIME-Version: 1.0 Content-Disposition: inline Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Quoting Chuanhong Guo : > Currently gpio-hog doesn't work on gpio-mt7621 driver. On further > debugging, I noticed that set/clear register on this controller > only works on output pins. We need to setup pin direction before > writing values in bgpio_dir_out for a correct gpio-hog behavior. > This patchset introduces a new flag BGPIOF_NO_SET_ON_INPUT for > these kind of controller and set this flag for gpio-mt7621. > > Chuanhong Guo (2): > gpio: mmio: introduce BGPIOF_NO_SET_ON_INPUT > gpio: mt7621: add BGPIOF_NO_SET_ON_INPUT flag > > drivers/gpio/gpio-mmio.c | 23 +++++++++++++++++++---- > drivers/gpio/gpio-mt7621.c | 4 ++-- > include/linux/gpio/driver.h | 1 + > 3 files changed, 22 insertions(+), 6 deletions(-) > > -- > 2.24.1 Thanks Chuanhong for debugging the problem! With this patch gpio-hog works again. For the series: Tested-by: René van Dorst Greats, René