From: Kevin Hilman <khilman-rdvid1DuHRBWk0Htik3J/w@public.gmane.org>
To: Matthias Brugger <matthias.bgg-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: Sascha Hauer <s.hauer-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>,
linux-mediatek-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Subject: Re: mt1873-evb: MMC failing with linux-next
Date: Fri, 12 Feb 2016 13:42:50 -0800 [thread overview]
Message-ID: <7h37sx1u79.fsf@baylibre.com> (raw)
In-Reply-To: <56BE01D6.40908-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> (Matthias Brugger's message of "Fri, 12 Feb 2016 17:01:26 +0100")
Matthias Brugger <matthias.bgg-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:
> On 12/02/16 16:24, Matthias Brugger wrote:
>> Hi Kevin,
>>
>> On 09/02/16 02:18, Kevin Hilman wrote:
>>> Hello,
>>>
>>> I tried getting MMC working with linux-next (next-20160208) on
>>> mt8173-evb by enabling a few options[1] on top of the default defconfig,
>>> and this results in a kernel that hangs as soon as it starts userspace.
>>>
>>> The MMC driver seems to start, though has some regulator issues:
>>>
>>> [ 0.526380] sdhci: Secure Digital Host Controller Interface driver
>>> [ 0.527176] sdhci: Copyright(c) Pierre Ossman
>>> [ 0.528835] vio18: unsupportable voltage range: 3300000-1980000uV
>>> [ 0.529610] mtk-msdc 11230000.mmc: Regulator set error -22:
>>> 3300000 - 3300000
>>> [ 0.563731] mtk-msdc 11240000.mmc: Got CD GPIO
>>>
>>> The driver appears to be attempting to set 3.3V but using a 1.8V
>>> regulator (vio18), which is failing.
>>>
>>> Then, the kernel hangs after freeing unused memory:
>>>
>>> [ 0.616386] hctosys: unable to open rtc device (rtc0)
>>> [ 0.624118] usb_vbus: disabling
>>> [ 0.624547] vusb: disabling
>>> [ 0.624929] vgp6: disabling
>>> [ 0.625635] ALSA device list:
>>> [ 0.626009] No soundcards found.
>>> [ 0.626963] Freeing unused kernel memory: 724K (ffffffc000977000 -
>>> ffffffc000a2c000)
>>>
>>> And nothing further here.
>>>
>>
>> I can see the warning from the mmc regulator access, but after that my
>> board boots just fine.
>> I'm using linux-next as of today (20160212).
>> I attached my config, it should be defconfig plus the config options you
>> mentioned (and an initramfs).
>>
>> Is this the configuration you have?
>
> I spotted an error in my scripts to build the kernel. After fixing
> this I can reproduce your error.
OK, let me know if you need anything else to help debug, or want me to
test anything further. Otherwise I'll leave it in your capable hands.
Kevin
next prev parent reply other threads:[~2016-02-12 21:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-09 1:18 mt1873-evb: MMC failing with linux-next Kevin Hilman
[not found] ` <7hegcmadfk.fsf-rdvid1DuHRBWk0Htik3J/w@public.gmane.org>
2016-02-12 15:24 ` Matthias Brugger
2016-02-12 15:28 ` Matthias Brugger
[not found] ` <56BDF937.60208-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-02-12 16:01 ` Matthias Brugger
[not found] ` <56BE01D6.40908-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-02-12 21:42 ` Kevin Hilman [this message]
2016-02-15 3:52 ` Eddie Huang
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=7h37sx1u79.fsf@baylibre.com \
--to=khilman-rdvid1duhrbwk0htik3j/w@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-mediatek-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=matthias.bgg-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=s.hauer-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.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