From: Hongzhan Chen <hongzhan.chen@intel.com>
To: xenomai@lists.linux.dev
Subject: [PATCH 1/2] pinctrl: intel: irq_pipeline: enable pipelined interrupt control for pintctrl-intel
Date: Mon, 4 Sep 2023 06:25:32 -0400 [thread overview]
Message-ID: <20230904102533.22448-1-hongzhan.chen@intel.com> (raw)
This is required to run the locking code from the pipeline
entry context and the out-of-band stage.
Signed-off-by: Hongzhan Chen <hongzhan.chen@intel.com>
diff --git a/drivers/pinctrl/intel/pinctrl-intel.c b/drivers/pinctrl/intel/pinctrl-intel.c
index 2ef9e2d8fd9c..7797618a899b 100644
--- a/drivers/pinctrl/intel/pinctrl-intel.c
+++ b/drivers/pinctrl/intel/pinctrl-intel.c
@@ -1322,7 +1322,8 @@ static int intel_gpio_probe(struct intel_pinctrl *pctrl, int irq)
pctrl->irqchip.irq_unmask = intel_gpio_irq_unmask;
pctrl->irqchip.irq_set_type = intel_gpio_irq_type;
pctrl->irqchip.irq_set_wake = intel_gpio_irq_wake;
- pctrl->irqchip.flags = IRQCHIP_MASK_ON_SUSPEND;
+ pctrl->irqchip.flags = IRQCHIP_MASK_ON_SUSPEND |
+ IRQCHIP_PIPELINE_SAFE;
/*
* On some platforms several GPIO controllers share the same interrupt
diff --git a/drivers/pinctrl/intel/pinctrl-intel.h b/drivers/pinctrl/intel/pinctrl-intel.h
index ad34b7a3f6ed..89ef4e37511f 100644
--- a/drivers/pinctrl/intel/pinctrl-intel.h
+++ b/drivers/pinctrl/intel/pinctrl-intel.h
@@ -228,7 +228,7 @@ struct intel_pinctrl_context {
*/
struct intel_pinctrl {
struct device *dev;
- raw_spinlock_t lock;
+ hard_spinlock_t lock;
struct pinctrl_desc pctldesc;
struct pinctrl_dev *pctldev;
struct gpio_chip chip;
--
2.17.1
next reply other threads:[~2023-09-04 10:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-04 10:25 Hongzhan Chen [this message]
2023-09-04 10:25 ` [PATCH 2/2] pinctrl: intel: irq_pipeline: enable pipelined interrupt control for pinctrl-baytrail Hongzhan Chen
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=20230904102533.22448-1-hongzhan.chen@intel.com \
--to=hongzhan.chen@intel.com \
--cc=xenomai@lists.linux.dev \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).