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;
From:   Chuanhong Guo <gch981213@gmail.com>
To:     linux-gpio@vger.kernel.org
Cc:     Chuanhong Guo <gch981213@gmail.com>,
        Linus Walleij <linus.walleij@linaro.org>,
        Bartosz Golaszewski <bgolaszewski@baylibre.com>,
        Sergio Paracuellos <sergio.paracuellos@gmail.com>,
        =?UTF-8?q?Ren=C3=A9=20van=20Dorst?= <opensource@vdorst.com>,
        linux-kernel@vger.kernel.org (open list)
Subject: [PATCH 0/2] gpio: mmio: introduce BGPIOF_NO_SET_ON_INPUT
Date:   Sun, 15 Mar 2020 20:13:36 +0800
Message-Id: <20200315121338.251362-1-gch981213@gmail.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

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