linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Linus Walleij <linus.walleij@linaro.org>,
	linux-gpio@vger.kernel.org,
	Mika Westerberg <mika.westerberg@linux.intel.com>
Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Subject: [PATCH v1 6/8] pinctrl: denverton: Provide Interrupt Status register offset
Date: Tue, 23 Jul 2019 18:56:31 +0300	[thread overview]
Message-ID: <20190723155633.65232-6-andriy.shevchenko@linux.intel.com> (raw)
In-Reply-To: <20190723155633.65232-1-andriy.shevchenko@linux.intel.com>

Since some of the GPIO controllers use different Interrupt Status offset,
it make sense to provide it explicitly in the driver.

Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
---
 drivers/pinctrl/intel/pinctrl-denverton.c | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/drivers/pinctrl/intel/pinctrl-denverton.c b/drivers/pinctrl/intel/pinctrl-denverton.c
index 3a4932b557b4..fde83cd4aac5 100644
--- a/drivers/pinctrl/intel/pinctrl-denverton.c
+++ b/drivers/pinctrl/intel/pinctrl-denverton.c
@@ -15,8 +15,9 @@
 #include "pinctrl-intel.h"
 
 #define DNV_PAD_OWN	0x020
-#define DNV_HOSTSW_OWN	0x0C0
 #define DNV_PADCFGLOCK	0x090
+#define DNV_HOSTSW_OWN	0x0C0
+#define DNV_GPI_IS	0x100
 #define DNV_GPI_IE	0x120
 
 #define DNV_GPP(n, s, e)				\
@@ -32,6 +33,7 @@
 		.padown_offset = DNV_PAD_OWN,		\
 		.padcfglock_offset = DNV_PADCFGLOCK,	\
 		.hostown_offset = DNV_HOSTSW_OWN,	\
+		.is_offset = DNV_GPI_IS,		\
 		.ie_offset = DNV_GPI_IE,		\
 		.pin_base = (s),			\
 		.npins = ((e) - (s) + 1),		\
-- 
2.20.1


  parent reply	other threads:[~2019-07-23 15:56 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-23 15:56 [PATCH v1 1/8] pinctrl: broxton: Provide Interrupt Status register offset Andy Shevchenko
2019-07-23 15:56 ` [PATCH v1 2/8] pinctrl: cannonlake: " Andy Shevchenko
2019-07-23 15:56 ` [PATCH v1 3/8] pinctrl: geminilake: " Andy Shevchenko
2019-07-23 15:56 ` [PATCH v1 4/8] pinctrl: icelake: " Andy Shevchenko
2019-07-23 15:56 ` [PATCH v1 5/8] pinctrl: sunrisepoint: " Andy Shevchenko
2019-07-23 15:56 ` Andy Shevchenko [this message]
2019-07-23 15:56 ` [PATCH v1 7/8] pinctrl: lewisburg: " Andy Shevchenko
2019-07-23 15:56 ` [PATCH v1 8/8] pinctrl: intel: Remove default Interrupt Status offset Andy Shevchenko
2019-08-06 10:30 ` [PATCH v1 1/8] pinctrl: broxton: Provide Interrupt Status register offset Mika Westerberg

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=20190723155633.65232-6-andriy.shevchenko@linux.intel.com \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=mika.westerberg@linux.intel.com \
    /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).