All of lore.kernel.org
 help / color / mirror / Atom feed
From: rbthomas@pobox.com (Rick Thomas)
To: linux-arm-kernel@lists.infradead.org
Subject: mvsdio not working on OpenRD
Date: Sun, 10 Jan 2016 13:19:51 -0800	[thread overview]
Message-ID: <55F9489C-1BCE-46F2-ABDC-C3E842306646@pobox.com> (raw)
In-Reply-To: <20160110153843.GA22229@lunn.ch>


On Jan 10, 2016, at 7:38 AM, Andrew Lunn <andrew@lunn.ch> wrote:

> On Sat, Jan 09, 2016 at 08:26:19PM -0800, Martin Michlmayr wrote:
>> Rick Thomas reported that MMC no longer works on his OpenRD Base.
>> 
>> With Debian's 3.16 kernel (using mach ID):
>> 
>> mvsdio mvsdio: no pins associated
>> mmc0: host does not support reading read-only switch.  assuming write-enable.
>> mmc0: new high speed SDHC card at address 0007
>> mmcblk0: mmc0:0007 SD4GB 3.70 GiB?
>> mmcblk0: p1
>> 
>> With Debian's 4.3 and 4.4-rc8 kernels (using Device Tree):
>> 
>> kirkwood-pinctrl f1010000.pin-controller: pin PIN13 already requested by f1012100.serial; cannot claim for f1090000.mvsdio
>> kirkwood-pinctrl f1010000.pin-controller: pin-13 (f1090000.mvsdio) status -22
>> kirkwood-pinctrl f1010000.pin-controller: could not request pin 13 (PIN13) from group mpp13  on device f1010000.pin-controller
>> mvsdio f1090000.mvsdio: Error applying setting, reverse things back
>> mvsdio f1090000.mvsdio: Got CD GPIO
>> [and no mmc0 or mmcblk0]
>> 
>> -- 
>> Martin Michlmayr
>> http://www.cyrius.com/
> 
> Hi Rick, Martin
> 
> If i remember correctly, the OpenRD has some odd muxing going on with
> MMC and the second serial port. This fits the error message:
> 
>                        pmx_uart1: pmx-uart1 {
>                                marvell,pins = "mpp13", "mpp14";
>                                marvell,function = "uart1";
>                        };
> 
> and
> 
>                        pmx_sdio: pmx-sdio {
>                                marvell,pins = "mpp12", "mpp13", "mpp14",
>                                               "mpp15", "mpp16", "mpp17";
>                                marvell,function = "sdio";
> 			};
> 
> Either you can have MMC, or you can have the RS-232/RS485 on a DB9 or
> you can have MMC. You cannot have both.
> 
> It seems like older Debian kernels has defaulted to MMC, so we should
> probably disable the serial port.
> 
> Please can you try the following patch. If this works, i can add it to
> mainline. The issue we might run into is that somebody else wants
> serial not MMC....
> 
>       Andrew
> 
> diff --git a/arch/arm/boot/dts/kirkwood-openrd-base.dts b/arch/arm/boot/dts/kirkwood-openrd-base.dts
> index 8af58999606d..883bd416ba0b 100644
> --- a/arch/arm/boot/dts/kirkwood-openrd-base.dts
> +++ b/arch/arm/boot/dts/kirkwood-openrd-base.dts
> @@ -18,11 +18,6 @@
> / {
>        model = "OpenRD Base";
>        compatible = "marvell,openrd-base", "marvell,openrd", "marvell,kirkwood-88f6281", "marvell,kirkwood";
> -
> -       ocp at f1000000 {
> -               serial at 12100 {
> -                       status = "okay";
> -               };
>        };
> };

OK, I understand the issue, and what the patch would mean.  Given that Debian releases up thru Jessie have chosen to support MMC rather than RS-232/RS485, I don?t think there will be many Debian users who would complain.

Unfortuntaely, I?m not set up to build kernels here.  If someone can apply this patch and send me a link to the resulting binary or .deb or .dts, or ? I?ll be happy to try it out on my test machine.

Thanks!
Rick

  reply	other threads:[~2016-01-10 21:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-10  4:26 mvsdio not working on OpenRD Martin Michlmayr
2016-01-10 15:38 ` Andrew Lunn
2016-01-10 21:19   ` Rick Thomas [this message]
2016-01-15 18:03   ` Aaro Koskinen
2016-01-15 19:22     ` Martin Michlmayr
2016-01-15 22:00       ` Aaro Koskinen
2016-01-17 23:05         ` Martin Michlmayr
2016-01-17 22:42   ` Martin Michlmayr

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=55F9489C-1BCE-46F2-ABDC-C3E842306646@pobox.com \
    --to=rbthomas@pobox.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.