From: stefan.wahren@i2se.com (Stefan Wahren)
To: linux-arm-kernel@lists.infradead.org
Subject: mmc1 timeout issue with rpi3
Date: Thu, 18 Jan 2018 17:55:21 +0100 [thread overview]
Message-ID: <fe2e55f8-a048-9973-5274-e16e2732f841@i2se.com> (raw)
In-Reply-To: <c578616d-3eb9-0b5c-c4be-1bad0d9052e9@orpaltech.com>
Hi Sergey,
Am 18.01.2018 um 13:55 schrieb Sergey Suloev:
> Hi, Stefan
>
> On 01/18/2018 10:03 AM, Stefan Wahren wrote:
>> Hi Sergey,
>>
>>> Sergey Suloev <ssuloev@orpaltech.com> hat am 17. Januar 2018 um
>>> 21:04 geschrieben:
>>>
>>>
>>> Hi Stefan,
>>>
>>> I am using u-boot tagged 2018.01.
>> interesting. I don't use u-boot as second stage bootloader. Maybe it
>> messed up the pin configuration of the GPIO expander. Could you
>> please try without u-boot?
>
> but how can u-boot influence that ? As far as I understand the error
> happens in a very late boot stage, actually in the end. At this time
> bcm2837-rpi-3-b device tree file from kernel is already loaded. Do you
> think this DTB is incorrect ?
wild guessing doesn't help here. Did you test it without U-Boot? Did the
issue still occur?
Stefan
>
> Thanks
>
>
next prev parent reply other threads:[~2018-01-18 16:55 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5d800b63-d45d-d4e4-214c-3ebf602c79e9@orpaltech.com>
[not found] ` <1059643032.72553.1516136078614@email.1und1.de>
[not found] ` <5ab12aa4-57a9-55b5-ef43-43b2eac9c1b7@orpaltech.com>
2018-01-17 18:19 ` mmc1 timeout issue with rpi3 Stefan Wahren
2018-01-17 18:47 ` Phil Elwell
2018-01-17 18:52 ` Sergey Suloev
2018-01-17 19:38 ` Phil Elwell
2018-01-17 18:49 ` Sergey Suloev
2018-01-17 19:32 ` Stefan Wahren
2018-01-17 20:04 ` Sergey Suloev
2018-01-18 7:03 ` Stefan Wahren
2018-01-18 12:55 ` Sergey Suloev
2018-01-18 16:55 ` Stefan Wahren [this message]
2018-01-18 17:56 ` Sergey Suloev
2018-01-18 18:07 ` Stefan Wahren
2018-01-18 18:09 ` Phil Elwell
2018-01-18 18:15 ` Sergey Suloev
2018-01-18 18:31 ` Sergey Suloev
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=fe2e55f8-a048-9973-5274-e16e2732f841@i2se.com \
--to=stefan.wahren@i2se.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