From: John Keeping <john@metanate.com>
To: Heiko Stuebner <heiko@sntech.de>
Cc: Julia Cartwright <julia@ni.com>,
Linus Walleij <linus.walleij@linaro.org>,
linux-gpio@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
John Keeping <john@metanate.com>
Subject: [PATCH v3 0/4] pinctrl: rockchip: PREEMPT_RT_FULL fixes
Date: Fri, 17 Mar 2017 18:24:26 +0000 [thread overview]
Message-ID: <20170317182430.27400-1-john@metanate.com> (raw)
The aim of the series is to make the Rockchip pinctrl irq_chip
implementation safe for use with RT_FULL which requires that raw
spinlocks are used to avoid sleeping in hardirq context.
This is the same as version 2 [1] with the 2.1 version of patch 1
included, but I'm rolling it up as a new version so it's simpler to
apply.
[1] https://www.spinics.net/lists/arm-kernel/msg568974.html
John Keeping (4):
pinctrl: rockchip: remove unnecessary locking
pinctrl: rockchip: convert to raw spinlock
pinctrl: rockchip: split out verification of mux settings
pinctrl: rockchip: avoid hardirq-unsafe functions in irq_chip
drivers/pinctrl/pinctrl-rockchip.c | 149 +++++++++++++++++++++----------------
1 file changed, 85 insertions(+), 64 deletions(-)
--
2.12.0.377.gf910686b23.dirty
next reply other threads:[~2017-03-17 18:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-17 18:24 John Keeping [this message]
2017-03-17 18:24 ` [PATCH v3 1/4] pinctrl: rockchip: remove unnecessary locking John Keeping
2017-03-17 18:24 ` [PATCH v3 2/4] pinctrl: rockchip: convert to raw spinlock John Keeping
2017-03-17 18:24 ` [PATCH v3 3/4] pinctrl: rockchip: split out verification of mux settings John Keeping
2017-03-17 18:24 ` [PATCH v3 4/4] pinctrl: rockchip: avoid hardirq-unsafe functions in irq_chip John Keeping
2017-03-23 9:20 ` [PATCH v3 0/4] pinctrl: rockchip: PREEMPT_RT_FULL fixes Linus Walleij
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=20170317182430.27400-1-john@metanate.com \
--to=john@metanate.com \
--cc=heiko@sntech.de \
--cc=julia@ni.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.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
all inboxes | Powered by JetHome®