linux-kernel - Re: [PATCH] ARM: imx: Fix GPIO_1_xx settings that are wrongly assumed

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]

Message-ID: <4CC9F8D7.4070802@eukrea.com>
Date:	Fri, 29 Oct 2010 00:27:35 +0200
From:	Eric Bénard <eric@...rea.com>
To:	Uwe Kleine-König 
	<u.kleine-koenig@...gutronix.de>
CC:	Dinh.Nguyen@...escale.com, amit.kucheria@...onical.com,
	linux@....linux.org.uk, s.hauer@...gutronix.de,
	linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH] ARM: imx: Fix GPIO_1_xx settings that are wrongly assumed

Hi Uwe,

Le 28/10/2010 22:59, Uwe Kleine-König a écrit :
 > Before b545d9ed1b92f169d0326afac091328be5e76620 the muxmode entries were
 > correct.  Back when I looked at the patch that resulted into b545d9ed1b9
 > I wondered if the intended change was only
 > s/NO_PAD_CTRL/MX51_GPIO_PAD_CTRL/ but didn't check the reference manual.
 >
 > Eric?
 >
GPIO_PAD_CTRL was the original wanted change for that patch and while looking 
at this I misread the iomux pages in the manual for gpio 2 to 9 which leads to 
the mux error.

BTW, Arnaud Patard already provided a fix to this in it's efikamx patch serie.

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