From: Alexandre Belloni <alexandre.belloni@free-electrons.com>
To: "Jiří Prchal" <jiri.prchal@aksignal.cz>
Cc: Boris BREZILLON <boris.brezillon@free-electrons.com>,
devicetree@vger.kernel.org, nicolas.ferre@atmel.com,
linux-arm-kernel@lists.infradead.org,
Bo Shen <voice.shen@atmel.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ARM: at91: at91sam9x5: sets NPCS0 (PA14) back to GPIO
Date: Fri, 25 Jul 2014 11:02:06 +0200 [thread overview]
Message-ID: <20140725090206.GG9532@piout.net> (raw)
In-Reply-To: <53D21C57.3010805@aksignal.cz>
On 25/07/2014 at 10:59:03 +0200, Jiří Prchal wrote :
> >>Of course, it's the way, but in all other drivers, for example LEDS,
> >>it's not needed. And in other way, if I will not use PA14 at all,
> >>the pin will goes down every spi transfer.
> >
> >You must not assumed that the pins are muxed to their default state
> >which is gpio and you should set the pinctrl accordingly for each
> >device.
> >
> >If you don't use PA14 at all, then you don't really care about its
> >state...
> Yes and no, what about on board is populated some chip on PA14, but
> for some reason at this time I don't need it and not defined in DT?
> >
If this is really an issue for that chip, I would think that you will
change the bootloader to not mux PA14 to periph A and stop it from
trying to read it like an spi flash ?
--
Alexandre Belloni, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-07-25 9:02 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-11 10:22 [PATCH] ARM: at91: at91sam9x5: add clocks for usb device Bo Shen
2014-07-11 10:47 ` Alexandre Belloni
2014-07-11 10:55 ` Jiří Prchal
2014-07-24 13:38 ` [PATCH] ARM: at91: at91sam9x5: sets NPCS0 (PA14) back to GPIO Jiří Prchal
2014-07-24 14:26 ` Boris BREZILLON
2014-07-24 15:06 ` Jiří Prchal
2014-07-24 15:58 ` Boris BREZILLON
2014-07-25 6:14 ` Jiří Prchal
2014-07-25 7:53 ` Boris BREZILLON
2014-07-25 8:27 ` Jiří Prchal
2014-07-25 8:45 ` Boris BREZILLON
2014-07-25 8:54 ` Jiří Prchal
2014-07-25 9:01 ` Boris BREZILLON
2014-07-25 9:13 ` Jiří Prchal
2014-07-25 9:31 ` Boris BREZILLON
2014-07-25 10:06 ` Jiří Prchal
2014-07-25 10:18 ` Boris BREZILLON
2014-07-25 10:32 ` Jiří Prchal
2014-07-25 11:34 ` Boris BREZILLON
2014-07-25 8:33 ` Jiří Prchal
2014-07-25 8:30 ` Alexandre Belloni
2014-07-25 8:36 ` Boris BREZILLON
2014-07-25 8:50 ` Alexandre Belloni
2014-07-25 8:37 ` Jiří Prchal
2014-07-25 8:54 ` Alexandre Belloni
2014-07-25 8:59 ` Jiří Prchal
2014-07-25 9:02 ` Alexandre Belloni [this message]
2014-07-25 9:10 ` Boris BREZILLON
2014-07-25 9:40 ` Jiří Prchal
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140725090206.GG9532@piout.net \
--to=alexandre.belloni@free-electrons.com \
--cc=boris.brezillon@free-electrons.com \
--cc=devicetree@vger.kernel.org \
--cc=jiri.prchal@aksignal.cz \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nicolas.ferre@atmel.com \
--cc=voice.shen@atmel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox