linux-kernel - Re: [PATCH] AMD Geode CS5535/5536 GPIO driver

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] [day] [month] [year] [list]

Date:	Sun, 15 Feb 2009 15:47:50 -0700
From:	Jordan Crouse <jordan@...micpenguin.net>
To:	Alessandro Zummo <azummo-lists@...ertech.it>
CC:	David Brownell <david-b@...bell.net>,
	linux-geode@...ts.infradead.org, dilinger@...ued.net,
	dsaxena@...top.org,
	Martin-Éric Racine <q-funk@....fi>,
	lkml <linux-kernel@...r.kernel.org>, rpurdie@...ys.net,
	Ingo Molnar <mingo@...e.hu>,
	Thomas Gleixner <tglx@...utronix.de>,
	"H. Peter Anvin" <hpa@...or.com>
Subject: Re: [PATCH] AMD Geode CS5535/5536 GPIO driver

Alessandro Zummo wrote:
> On Thu, 5 Feb 2009 16:12:20 -0800
> David Brownell <david-b@...bell.net> wrote:
> 
>> Unless this hardware misbehaves when both output and input
>> modes are enabled (e.g. in the window between those two calls),
>> I'd suggest just not clearing INPUT_ENABLE.  It's legit to
>> ask for the *actual* value of an output line, e.g. for when
>> it uses open drain mode.  (And didn't this hardware have an
>> option for open drain GPIO signaling?)
> 
>  seems reasonable,
>  I'll let the Geode people decide what to do here... 

Sorry, I'm just getting around to answering this. I don't recall any 
situation where the hardware would mis-behave, but you never know with 
this bit of silicon.

I say leave them both on, and revisit it if you get flamed.

Jordan




--
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/