From: Nicolas Ferre <nicolas.ferre@microchip.com>
To: <cristian.birsan@microchip.com>,
<alexandre.belloni@free-electrons.com>, <robh+dt@kernel.org>,
<mark.rutland@arm.com>, <linux@armlinux.org.uk>
Cc: <cyrille.pitchen@atmel.com>, <boris.brezillon@free-electrons.com>,
<linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ARM: at91/dt: Disable SPI on at91sam9x5ek to allow MCI1 to work.
Date: Mon, 20 Feb 2017 11:20:04 +0100 [thread overview]
Message-ID: <95353208-6734-aec5-a41b-e62d28dd747c@microchip.com> (raw)
In-Reply-To: <1487265388-29390-1-git-send-email-cristian.birsan@microchip.com>
Le 16/02/2017 à 18:16, cristian.birsan@microchip.com a écrit :
> From: Cristian Birsan <cristian.birsan@microchip.com>
>
> The A13 hardware line is shared by SPI and MCI1 controller.This patch
> disables the SPI controller so that the MCI1 (the big MMC card slot) can
> be used.
>
> Signed-off-by: Cristian Birsan <cristian.birsan@microchip.com>
Acked-by: Nicolas Ferre <nicolas.ferre@microchip.com>
> ---
> arch/arm/boot/dts/at91sam9x5ek.dtsi | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/arm/boot/dts/at91sam9x5ek.dtsi b/arch/arm/boot/dts/at91sam9x5ek.dtsi
> index 696b8ba..9d2bbc4 100644
> --- a/arch/arm/boot/dts/at91sam9x5ek.dtsi
> +++ b/arch/arm/boot/dts/at91sam9x5ek.dtsi
> @@ -116,7 +116,7 @@
> };
>
> spi0: spi@f0000000 {
> - status = "okay";
> + status = "disabled"; /* conflicts with mmc1 */
> cs-gpios = <&pioA 14 0>, <0>, <0>, <0>;
> m25p80@0 {
> compatible = "atmel,at25df321a";
>
--
Nicolas Ferre
next prev parent reply other threads:[~2017-02-20 10:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-16 17:16 cristian.birsan
2017-02-20 10:20 ` Nicolas Ferre [this message]
2017-03-05 22:55 ` Alexandre Belloni
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=95353208-6734-aec5-a41b-e62d28dd747c@microchip.com \
--to=nicolas.ferre@microchip.com \
--cc=alexandre.belloni@free-electrons.com \
--cc=boris.brezillon@free-electrons.com \
--cc=cristian.birsan@microchip.com \
--cc=cyrille.pitchen@atmel.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
/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
all inboxes | Powered by JetHome®