linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Andreas Schwab <schwab@suse.de>
Cc: Atish Patra <atish.patra@wdc.com>,
	palmer@sifive.com, linux-riscv@lists.infradead.org,
	linux-pwm@vger.kernel.org, linux-gpio@vger.kernel.org,
	linus.walleij@linaro.org, robh+dt@kernel.org,
	thierry.reding@gmail.com, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, mark.rutland@arm.com,
	hch@infradead.org
Subject: Re: [RFC 4/4] gpio: sifive: Add GPIO driver for SiFive SoCs
Date: Wed, 10 Oct 2018 06:12:55 -0700	[thread overview]
Message-ID: <20181010131255.GB29142@infradead.org> (raw)
In-Reply-To: <mvmo9c22bx2.fsf@suse.de>

On Wed, Oct 10, 2018 at 03:01:29PM +0200, Andreas Schwab wrote:
> On Okt 09 2018, Atish Patra <atish.patra@wdc.com> wrote:
> 
> > +static void sifive_set_ie(struct sifive_gpio *chip, unsigned int offset)
> > +{
> > +	unsigned long flags;
> > +	unsigned int trigger;
> > +
> > +	raw_spin_lock_irqsave(&chip->lock, flags);
> > +	trigger = (chip->enabled & BIT(offset)) ? chip->trigger[offset] : 0;
> 
> This should use test_bit instead.

Given that this apparently needs the spinlock for atomciy with more than
just the bitmap test_bit would be rather pointless.

  reply	other threads:[~2018-10-10 13:12 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-09 18:51 [RFC 0/4] GPIO & PWM support for HiFive Unleashed Atish Patra
2018-10-09 18:51 ` [RFC 1/4] pwm: sifive: Add DT documentation for SiFive PWM Controller Atish Patra
2018-10-10 13:49   ` Thierry Reding
2018-10-15 22:57     ` Atish Patra
2018-10-15 23:19       ` Wesley Terpstra
2018-10-16 11:13         ` Thierry Reding
2018-10-16 11:01       ` Thierry Reding
2018-10-16 17:31         ` Paul Walmsley
2018-10-16 22:04           ` Thierry Reding
2018-10-16 22:20             ` Atish Patra
2018-10-17 15:58               ` Rob Herring
2018-10-17 21:45                 ` Atish Patra
2018-11-10  5:38             ` Paul Walmsley
2018-10-10 13:51   ` Thierry Reding
2018-10-15 22:45     ` Atish Patra
2018-10-16 10:51       ` Thierry Reding
2018-10-16 22:42         ` Atish Patra
2018-10-09 18:51 ` [RFC 2/4] pwm: sifive: Add a driver for SiFive SoC PWM Atish Patra
2018-10-10 13:11   ` Christoph Hellwig
2018-10-10 13:44     ` Thierry Reding
2018-10-16  6:28     ` Atish Patra
2018-10-10 14:13   ` Thierry Reding
2018-10-16  6:24     ` Atish Patra
2018-10-09 18:51 ` [RFC 3/4] gpio: sifive: Add DT documentation for SiFive GPIO Atish Patra
2018-10-09 18:51 ` [RFC 4/4] gpio: sifive: Add GPIO driver for SiFive SoCs Atish Patra
2018-10-10 12:35   ` Linus Walleij
2018-10-17  1:01     ` Atish Patra
2019-09-18  7:32       ` Bin Meng
2018-10-10 13:01   ` Andreas Schwab
2018-10-10 13:12     ` Christoph Hellwig [this message]
2018-10-10 13:28       ` Andreas Schwab

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=20181010131255.GB29142@infradead.org \
    --to=hch@infradead.org \
    --cc=atish.patra@wdc.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pwm@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=mark.rutland@arm.com \
    --cc=palmer@sifive.com \
    --cc=robh+dt@kernel.org \
    --cc=schwab@suse.de \
    --cc=thierry.reding@gmail.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).