linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: dillon.minfei@gmail.com
To: linus.walleij@linaro.org, lee.jones@linaro.org,
	bgolaszewski@baylibre.com
Cc: linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
	dillon min <dillon.minfei@gmail.com>
Subject: [PATCH: V2  0/2] Fix TC35894 gpio interrupt bug
Date: Thu,  3 Sep 2020 15:30:20 +0800	[thread overview]
Message-ID: <1599118222-18990-1-git-send-email-dillon.minfei@gmail.com> (raw)

From: dillon min <dillon.minfei@gmail.com>

This patchset intend to fix two bug on tc35894

V2:
1 change V1[1] patch's Fixes tag
2 add DIRECTx register configuration in tc3589x_gpio_irq_sync_unlock()
  to active general purpose gpio mode, else can't read correct
  GPIOMISx to identify which interrupt


V1:

1 offset counting is wrong in tc3589x_gpio_irq_sync_unlock()
2 disable Direct KBD interrupts in gpio-tc3589x's probe(),
  at least have to do this on tc35894, if not, after chip reset,
  IRQST(0x91) will always be 0x20, IRQN always low level,
  can't be cleared. need more test on other tc3589x.


dillon min (2):
  gpio: tc35894: fix up tc35894 interrupt configuration
  gpio: tc35894: Disable Direct KBD interrupts to enable gpio irq

 drivers/gpio/gpio-tc3589x.c | 20 +++++++++++++++++---
 include/linux/mfd/tc3589x.h |  6 ++++++
 2 files changed, 23 insertions(+), 3 deletions(-)

-- 


             reply	other threads:[~2020-09-03  7:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-03  7:30 dillon.minfei [this message]
2020-09-03  7:30 ` [PATCH: V2 1/2] gpio: tc35894: fix up tc35894 interrupt configuration dillon.minfei
2020-09-09  9:34   ` Bartosz Golaszewski
2020-09-03  7:30 ` [PATCH: V2 2/2] gpio: tc35894: Disable Direct KBD interrupts to enable gpio irq dillon.minfei
2020-09-08 14:04   ` Lee Jones
2020-09-09  9:33   ` Bartosz Golaszewski

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1599118222-18990-1-git-send-email-dillon.minfei@gmail.com \
    --to=dillon.minfei@gmail.com \
    --cc=bgolaszewski@baylibre.com \
    --cc=lee.jones@linaro.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).