public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Olliver Schinagl <oliver+list@schinagl.nl>
To: hramrach@gmail.com, linux-sunxi <linux-sunxi@googlegroups.com>,
	Hans de Goede <hdegoede@redhat.com>
Cc: sigintmailru@gmail.com, arend@broadcom.com,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	linux-arm-kernel <linux-arm-kernel@lists.infradead.org>
Subject: Re: [linux-sunxi] MMC clock gating broken on a20
Date: Wed, 12 Aug 2015 13:55:59 +0200	[thread overview]
Message-ID: <55CB344F.6050608@schinagl.nl> (raw)
In-Reply-To: <55CB3095.9050509@schinagl.nl>

Actually, I've reverted hans's

mmc: sunxi: Don't start commands while the card is busy

and that makes it disapear as well. So it looks like that patch triggers 
the aggressiveness more?

I'll apply your patch and undo the revert to see if that fixes the root 
issue.

Olliver

On 12-08-15 13:40, Olliver Schinagl wrote:
> Hey all,
>
> I'm noticing the exact same thing using hans's sunxi-wip from a few 
> days ago.
>
> I did see a patch from you about this very issue I belive
> mmc: sunxi: fix timeout in sunxi_mmc_oclk_onoff
>
> but can't find it in any of the repo's. Has it been merged yet and did 
> that actually solve the problem eventually?
>
>
> On 24-05-15 14:37, Michal Suchanek wrote:
>> Hello,
>>
>> I tried to update the kernel on my cubieboards to something recent and
>> while the a10 cubieboard works fine the a20 one won't boot.
>>
>> Looking at the console I found that the culprit is mmc clock so I
>> disabled mmc clock gating and the board works.
>>
>> I went as far back as 3.19 and the issue is pretty much the same. The
>> difference is that with linus master the clock gating seems more
>> aggressive so the board does not even boot whereas with 3.19 it
>> crashes shortly after booting fully.
>>
>> Anyone has some idea why the clock would fail re-enabling after gated?
>>
>> Supposedly the clock was already set up by the kernel when probing 
>> the mmc.
>>
>> Thanks
>>
>> Michal
>>
>> root@sunxi-a20:~# sunxi-mmc 1c0f000.mmc: fatal err update clk timeout
>> mmcblk0: error -5 requesting status
>> blk_update_request: I/O error, dev mmcblk0, sector 2048
>> Buffer I/O error on dev mmcblk0p1, logical block 0, lost async page 
>> write
>> blk_update_request: I/O error, dev mmcblk0, sector 2056
>> Buffer I/O error on dev mmcblk0p1, logical block 1, lost async page 
>> write
>> mmcblk0: error -5 sending status command, retrying
>> mmcblk0: error -5 sending status command, retrying
>> mmcblk0: error -5 sending status command, aborting
>> blk_update_request: I/O error, dev mmcblk0, sector 6776
>> Buffer I/O error on dev mmcblk0p1, logical block 591, lost async page 
>> write
>> mmcblk0: error -5 sending status command, retrying
>> mmcblk0: error -5 sending status command, retrying
>> mmcblk0: error -5 sending status command, aborting
>>
>


       reply	other threads:[~2015-08-12 11:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAOMqctRhQHv1idY0ci6uzDxnv5oj7dbHtc4CTfo75ipXkXd1gw@mail.gmail.com>
     [not found] ` <55CB3095.9050509@schinagl.nl>
2015-08-12 11:55   ` Olliver Schinagl [this message]
2015-08-12 12:30     ` [linux-sunxi] MMC clock gating broken on a20 Michal Suchanek

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=55CB344F.6050608@schinagl.nl \
    --to=oliver+list@schinagl.nl \
    --cc=arend@broadcom.com \
    --cc=hdegoede@redhat.com \
    --cc=hramrach@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sunxi@googlegroups.com \
    --cc=sigintmailru@gmail.com \
    /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