linux-kernel - Re: [stable] [PATCH] cs5535-gpio: apply CS5536 errata workaround for GPIOs

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:	Mon, 29 Nov 2010 19:30:07 -0800
From:	Greg KH <greg@...ah.com>
To:	Andres Salomon <dilinger@...ued.net>
Cc:	akpm@...ux-foundation.org, dsd@...top.org, stable@...nel.org,
	cjb@...top.org, linux-kernel@...r.kernel.org,
	linux-geode@...ts.infradead.org
Subject: Re: [stable] [PATCH] cs5535-gpio: apply CS5536 errata workaround
 for GPIOs

On Mon, Nov 29, 2010 at 05:19:30PM -0800, Andres Salomon wrote:
> 
> The AMD Geode CS5536 Companion Device Silicon Revision B1 Specification Update
> mentions the follow as issue #36:
> 
> "Atomic write transactions to the atomic GPIO High Bank Feature Bit registers
> should only affect the bits selected [...]"
> "after Suspend, an atomic write transaction [...] will clear all non-selected
> bits of the accessed register."
> 
> In other words, writing to the high bank for a single GPIO bit will clear
> every other GPIO bit (but only sometimes after a suspend).  The workaround
> described is obvious and simple; do a read-modify-write.  This patch does
> that, and documents why we're doing it.
> 
> Signed-off-by: Andres Salomon <dilinger@...ued.net>

Please read Documentation/stable_kernel_rules.txt for how to get patches
into the stable kernel releases (hint, this wasn't the proper way...)

thanks,

greg k-h
--
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/