linux-kernel - Re: [PATCH] ARM: at91: at91sam9x5: sets NPCS0 (PA14) back to GPIO

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]

Date:	Fri, 25 Jul 2014 10:36:45 +0200
From:	Boris BREZILLON <boris.brezillon@...e-electrons.com>
To:	Alexandre Belloni <alexandre.belloni@...e-electrons.com>
Cc:	Jiří Prchal <jiri.prchal@...ignal.cz>,
	devicetree@...r.kernel.org, nicolas.ferre@...el.com,
	linux-arm-kernel@...ts.infradead.org,
	Bo Shen <voice.shen@...el.com>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] ARM: at91: at91sam9x5: sets NPCS0 (PA14) back to GPIO

Hi Alexandre,

On Fri, 25 Jul 2014 10:30:54 +0200
Alexandre Belloni <alexandre.belloni@...e-electrons.com> wrote:

> Hi,
> 
> On 25/07/2014 at 08:14:40 +0200, Jiří Prchal wrote :
> > I'm using custom board. My spi node:
> > 			spi0: spi@...00000 {
> 
> You should override the pinctrl here as you are using gpios for the cs.
> 				pinctrl-0 = <&pinctrl_spi0_custom>;

I guess you meant:
			pinctrl-0 <&pinctrl_spi0 &pinctrl_spi0_custom>;

I suggested the same thing, however I'm pretty sure this is not the
source of the problem. As I said, gpio_request already mux the
associated pin to GPIO function.

Best Regards,

Boris


-- 
Boris Brezillon, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
--
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/