From: heiko@sntech.de (Heiko Stuebner)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 2/4] pinctrl: rockchip: convert to raw spinlock
Date: Wed, 15 Mar 2017 19:16:53 +0100 [thread overview]
Message-ID: <8564532.G8NNa9Oa4k@phil> (raw)
In-Reply-To: <20170315180806.3714af56.john@metanate.com>
Am Mittwoch, 15. M?rz 2017, 18:08:06 CET schrieb John Keeping:
> On Wed, 15 Mar 2017 13:01:37 -0500, Julia Cartwright wrote:
> > On Wed, Mar 15, 2017 at 05:46:52PM +0000, John Keeping wrote:
> > > This lock is used from rockchip_irq_set_type() which is part of the
> > > irq_chip implementation and thus must use raw_spinlock_t as documented
> > > in Documentation/gpio/driver.txt.
> > >
> > > Signed-off-by: John Keeping <john@metanate.com>
> > > Reviewed-by: Heiko Stuebner <heiko@sntech.de>
> > > Tested-by: Heiko Stuebner <heiko@sntech.de>
> > > ---
> > > v2: unchanged
> > > ---
> > >
> > > drivers/pinctrl/pinctrl-rockchip.c | 30 +++++++++++++++---------------
> > > 1 file changed, 15 insertions(+), 15 deletions(-)
> > >
> > > diff --git a/drivers/pinctrl/pinctrl-rockchip.c
> > > b/drivers/pinctrl/pinctrl-rockchip.c index 128c383ea7ba..8c1cae6d78d7
> > > 100644
> > > --- a/drivers/pinctrl/pinctrl-rockchip.c
> > > +++ b/drivers/pinctrl/pinctrl-rockchip.c
> > > @@ -163,7 +163,7 @@ struct rockchip_pin_bank {
> > >
> > > struct irq_domain *domain;
> > > struct gpio_chip gpio_chip;
> > > struct pinctrl_gpio_range grange;
> > >
> > > - spinlock_t slock;
> > > + raw_spinlock_t slock;
> > >
> > > u32 toggle_edge_mode;
> > >
> > > };
> > >
> > > @@ -1295,14 +1295,14 @@ static int rockchip_set_pull(struct
> > > rockchip_pin_bank *bank,> >
> > > switch (ctrl->type) {
> > >
> > > case RK2928:
> > > - spin_lock_irqsave(&bank->slock, flags);
> > > + raw_spin_lock_irqsave(&bank->slock, flags);
> > >
> > > data = BIT(bit + 16);
> > > if (pull == PIN_CONFIG_BIAS_DISABLE)
> > >
> > > data |= BIT(bit);
> >
> > This should be lifted out from under the lock.
> >
> > > ret = regmap_write(regmap, reg, data);
> >
> > How is this legal? The regmap_write() here is going to end up acquiring
> > the regmap mutex.
>
> It's not, the spinlock can be deleted here. I only have RK3288 hardware
> to test and I missed this when checking the uses of slock.
That part could very well also use regmap_update_bits like the other parts.
Not really sure, why we use regmap_write here, but I'm also not sure, if it
matters at all.
next prev parent reply other threads:[~2017-03-15 18:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-15 17:46 [PATCH v2 0/4] pinctrl: rockchip: PREEMPT_RT_FULL fixes John Keeping
2017-03-15 17:46 ` [PATCH v2 1/4] pinctrl: rockchip: remove unnecessary locking John Keeping
2017-03-15 18:51 ` [PATCH v2.1 " John Keeping
2017-03-23 9:03 ` [PATCH v2 " Linus Walleij
2017-03-15 17:46 ` [PATCH v2 2/4] pinctrl: rockchip: convert to raw spinlock John Keeping
2017-03-15 18:01 ` Julia Cartwright
2017-03-15 18:08 ` John Keeping
2017-03-15 18:16 ` Heiko Stuebner [this message]
2017-03-15 18:23 ` Julia Cartwright
2017-03-15 18:46 ` John Keeping
2017-03-15 17:46 ` [PATCH v2 3/4] pinctrl: rockchip: split out verification of mux settings John Keeping
2017-03-15 17:46 ` [PATCH v2 4/4] pinctrl: rockchip: avoid hardirq-unsafe functions in irq_chip John Keeping
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=8564532.G8NNa9Oa4k@phil \
--to=heiko@sntech.de \
--cc=linux-arm-kernel@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