From: nicolas.ferre@atmel.com (Nicolas Ferre)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] ARM: at91: fix at91sam9263ek DT mmc pinmuxing settings
Date: Wed, 24 Sep 2014 18:11:12 +0200 [thread overview]
Message-ID: <5422ED20.5010709@atmel.com> (raw)
In-Reply-To: <1411485172-7984-1-git-send-email-andreas.henriksson@endian.se>
On 23/09/2014 17:12, Andreas Henriksson :
> As discovered on a custom board similar to at91sam9263ek and basing
> its devicetree on that one apparently the pin muxing doesn't get
> set up properly. This was discovered since the custom boards u-boot
> does funky stuff with the pin muxing and leaved it set to SPI
> which made the MMC driver not work under Linux.
> The fix is simply to define the given configuration as the default.
> This probably worked by pure luck before, but it's better to
> make the muxing explicitly set.
>
> CC: Boris BREZILLON <boris.brezillon@free-electrons.com>
> Signed-off-by: Andreas Henriksson <andreas.henriksson@endian.se>
Thanks, I stacked it on at91-3.18-fixes-non-critical branch.
Acked-by: Nicolas Ferre <nicolas.ferre@atmel.com>
For the record, we chose to set this
pinctrl-names = "default";
property in the SoC file without the associated pinctrl-0 property
because there is not "default" setting: we never know if we would use
the slot A or slot B with different pins in play.
So, as we must add a pinctrl-0 property in the board anyway, we decided
to not add pinctrl-0 in the SoC while keeping pinctrl-names as it is
always needed (as you experienced the hard way ;-)).
Best regards,
> ---
> arch/arm/boot/dts/at91sam9263.dtsi | 2 ++
> 1 file changed, 2 insertions(+)
>
> v2: put pinctrl-names in dtsi instead as requested/suggested by Nicolas Ferre
>
>
> diff --git a/arch/arm/boot/dts/at91sam9263.dtsi b/arch/arm/boot/dts/at91sam9263.dtsi
> index bb23c2d..5e95a80 100644
> --- a/arch/arm/boot/dts/at91sam9263.dtsi
> +++ b/arch/arm/boot/dts/at91sam9263.dtsi
> @@ -834,6 +834,7 @@
> compatible = "atmel,hsmci";
> reg = <0xfff80000 0x600>;
> interrupts = <10 IRQ_TYPE_LEVEL_HIGH 0>;
> + pinctrl-names = "default";
> #address-cells = <1>;
> #size-cells = <0>;
> clocks = <&mci0_clk>;
> @@ -845,6 +846,7 @@
> compatible = "atmel,hsmci";
> reg = <0xfff84000 0x600>;
> interrupts = <11 IRQ_TYPE_LEVEL_HIGH 0>;
> + pinctrl-names = "default";
> #address-cells = <1>;
> #size-cells = <0>;
> clocks = <&mci1_clk>;
>
--
Nicolas Ferre
prev parent reply other threads:[~2014-09-24 16:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-23 11:42 [PATCH] ARM: at91: fix at91sam9263ek DT mmc pinmuxing settings Andreas Henriksson
2014-09-23 11:47 ` Boris BREZILLON
2014-09-23 12:06 ` Nicolas Ferre
2014-09-23 15:12 ` [PATCH v2] " Andreas Henriksson
2014-09-23 15:43 ` Boris BREZILLON
2014-09-24 16:11 ` Nicolas Ferre [this message]
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=5422ED20.5010709@atmel.com \
--to=nicolas.ferre@atmel.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).