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 5/6] pinctrl: intel: Allow drivers to define ACPI address space ID
Date: Tue, 9 Jun 2020 21:24:48 +0300 [thread overview]
Message-ID: <20200609182449.45813-5-andriy.shevchenko@linux.intel.com> (raw)
In-Reply-To: <20200609182449.45813-1-andriy.shevchenko@linux.intel.com>
Individual drivers may install ACPI OpRegion handlers based on
address space ID which differs from community to community.
Add special field in the struct intel_community for that purpose.
Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
---
drivers/pinctrl/intel/pinctrl-intel.h | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/pinctrl/intel/pinctrl-intel.h b/drivers/pinctrl/intel/pinctrl-intel.h
index 0f01ef3fdfdd..4e17308d33e9 100644
--- a/drivers/pinctrl/intel/pinctrl-intel.h
+++ b/drivers/pinctrl/intel/pinctrl-intel.h
@@ -104,6 +104,7 @@ enum {
* @ngpps: Number of pad groups in this community
* @pad_map: Optional non-linear mapping of the pads
* @nirqs: Optional total number of IRQs this community can generate
+ * @acpi_space_id: Optional address space ID for ACPI OpRegion handler
* @regs: Community specific common registers (reserved for core driver)
* @pad_regs: Community specific pad registers (reserved for core driver)
*
@@ -129,6 +130,7 @@ struct intel_community {
size_t ngpps;
const unsigned int *pad_map;
unsigned short nirqs;
+ unsigned short acpi_space_id;
/* Reserved for the core driver */
void __iomem *regs;
--
2.27.0.rc2
next prev parent reply other threads:[~2020-06-09 18:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-09 18:24 [PATCH v1 1/6] pinctrl: cherryview: Introduce chv_readl() helper Andy Shevchenko
2020-06-09 18:24 ` [PATCH v1 2/6] pinctrl: cherryview: Introduce helpers to IO with common registers Andy Shevchenko
2020-06-09 18:24 ` [PATCH v1 3/6] pinctrl: cherryview: Convert chv_writel() to use chv_padreg() Andy Shevchenko
2020-06-09 18:24 ` [PATCH v1 4/6] pinctrl: intel: Allow drivers to define total amount of IRQs per community Andy Shevchenko
2020-06-09 18:24 ` Andy Shevchenko [this message]
2020-06-09 18:24 ` [PATCH v1 6/6] pinctrl: cherryview: Re-use data structures from pinctrl-intel.h (part 3) Andy Shevchenko
2020-06-10 13:16 ` [PATCH v1 1/6] pinctrl: cherryview: Introduce chv_readl() helper Mika Westerberg
2020-06-15 10:28 ` Andy Shevchenko
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=20200609182449.45813-5-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).