From: Mark Brown <broonie@kernel.org>
To: Alexandre Belloni <alexandre.belloni@free-electrons.com>
Cc: "Jiří Prchal" <jiri.prchal@aksignal.cz>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, nicolas.ferre@atmel.com,
voice.shen@atmel.com
Subject: Re: [PATCH] ARM: at91: spi: request all csgpio in spi probe
Date: Tue, 29 Jul 2014 12:32:36 +0100 [thread overview]
Message-ID: <20140729113236.GM17528@sirena.org.uk> (raw)
In-Reply-To: <20140728223859.GA3214@piout.net>
[-- Attachment #1: Type: text/plain, Size: 937 bytes --]
On Tue, Jul 29, 2014 at 12:38:59AM +0200, Alexandre Belloni wrote:
> Mark: maybe it would make sense to do devm_gpio_request_one() in
> of_spi_register_master(), after of_get_named_gpio.
You need to transition all the drivers doing things manually but yes.
As I keep saying all the GPIO handling needs to be completely
refactored.
> While this solves the particular issue Jiří is seeing, this will not
> solve the case where PA14 (CS0) is not used by the spi driver at all. It
> will remained muxed as CS0 and toggle when the spi master needs to
> access CS0 until another driver muxes it to something else. I still
> believe we should explicitly ask pinctrl to mux them as gpios.
I'm just guessing as to what the issue that he's seeing is but isn't
this just saying that the board pinmuxing is wrong? If the board
doesn't want the pin to be used by the SPI controller it shouldn't be
configuring it that way.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2014-07-29 11:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-28 11:43 [PATCH] ARM: at91: spi: request all csgpio in spi probe Jiri Prchal
2014-07-28 12:21 ` Alexandre Belloni
2014-07-28 13:06 ` Jiří Prchal
2014-07-28 22:38 ` Alexandre Belloni
2014-07-29 8:00 ` Boris BREZILLON
2014-07-31 15:59 ` Alexandre Belloni
2014-07-31 16:10 ` Jean-Christophe PLAGNIOL-VILLARD
2014-07-31 16:48 ` Alexandre Belloni
2014-07-31 17:05 ` Jean-Christophe PLAGNIOL-VILLARD
2014-07-29 11:32 ` Mark Brown [this message]
2014-07-28 15:06 ` Boris BREZILLON
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=20140729113236.GM17528@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alexandre.belloni@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