linux-kernel - Re: [v2 2/4] platform: (TS-5500) add GPIO support

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20110830171203.3fc81588@v0nbox>
Date:	Tue, 30 Aug 2011 17:12:03 -0400
From:	Vivien Didelot <vivien.didelot@...oirfairelinux.com>
To:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
Cc:	x86@...nel.org,
	Jerome Oufella <jerome.oufella@...oirfairelinux.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	Ingo Molnar <mingo@...hat.com>,
	"H. Peter Anvin" <hpa@...or.com>, linux-kernel@...r.kernel.org
Subject: Re: [v2 2/4] platform: (TS-5500) add GPIO support

On Mon, 29 Aug 2011 23:11:33 +0100,
Mark Brown <broonie@...nsource.wolfsonmicro.com> wrote:

> On Fri, Aug 26, 2011 at 07:40:25PM -0400, Vivien Didelot wrote:
> > +	bitno = line_to_bit_map[offset];
> > +
> > +	mutex_lock(&drvdata->gpio_lock);
> > +	byte = inb(ioaddr);
> > +	mutex_unlock(&drvdata->gpio_lock);
> 
> Do you really need the lock to do a read?

Thanks for the explanation. I removed the mutex lock here as there's no
critical section except for the inb() call in this function.

	Vivien.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/