linux-kernel - Re: [PATCH] libata: pata_bf54x: handle portmuxing of pins through GPIO PORTs

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: <4B2FC527.2010301@garzik.org>
Date:	Mon, 21 Dec 2009 13:57:43 -0500
From:	Jeff Garzik <jeff@...zik.org>
To:	Mike Frysinger <vapier@...too.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>
CC:	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org, Sonic Zhang <sonic.zhang@...log.com>,
	Bryan Wu <cooloney@...nel.org>
Subject: Re: [PATCH] libata: pata_bf54x: handle portmuxing of pins through
 GPIO PORTs

On 07/14/2009 01:39 PM, Mike Frysinger wrote:
> From: Sonic Zhang<sonic.zhang@...log.com>
>
> By default, the PATA pins are routed to the async address lines in which
> case, no peripheral muxing needs to be done.  However, if the pins get
> routed through the GPIO PORTs pins, we need to make sure to request them
> so that the muxing is properly set up.
>
> Signed-off-by: Sonic Zhang<sonic.zhang@...log.com>
> Signed-off-by: Bryan Wu<cooloney@...nel.org>
> Signed-off-by: Mike Frysinger<vapier@...too.org>
> ---
> Andrew: could you pick this up ?  it was posted over a month ago to the
> Linux/IDE list w/no feedback.
>
>   drivers/ata/pata_bf54x.c |   19 +++++++++++++++++++
>   1 files changed, 19 insertions(+), 0 deletions(-)


Added to the tip of libata-dev...

Linus, if you pull

master.kernel.org:/pub/scm/linux/kernel/git/jgarzik/libata-dev.git 
upstream-linus

then you will receive the previous pull (two pata_cmd64x fixes), plus 
the above fix to pata_bf54x.

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