From: Anton Vorontsov <avorontsov@ru.mvista.com>
To: Pierre Ossman <drzeus@drzeus.cx>
Cc: Ben Dooks <ben-linux@fluff.org>, Arnd Bergmann <arnd@arndb.de>,
Liu Dave <DaveLiu@freescale.com>,
linux-kernel@vger.kernel.org, linuxppc-dev@ozlabs.org,
sdhci-devel@list.drzeus.cx
Subject: Re: [PATCH 10/11] sdhci: Add quirk for Freescale eSDHC controllers
Date: Fri, 13 Feb 2009 17:42:38 +0300 [thread overview]
Message-ID: <20090213144238.GA12304@oksana.dev.rtsoft.ru> (raw)
In-Reply-To: <20090208221209.628ae782@mjolnir.drzeus.cx>
On Sun, Feb 08, 2009 at 10:12:09PM +0100, Pierre Ossman wrote:
> On Fri, 6 Feb 2009 21:07:01 +0300
> Anton Vorontsov <avorontsov@ru.mvista.com> wrote:
>
> > This patch adds SDHCI_QUIRK_FSL quirk. The quirk is used to instruct
> > the sdhci driver about various FSL eSDHC host incompatibilities:
> >
>
> No device quirks please. They should be for specific bugs, not lumping
> things together like this. Otherwise we'll soon have an unmanageable
> mess.
OK.
> > 1) FSL eSDHC controllers can support maximum block size up to 4096
> > bytes. The MBL (Maximum Block Length) field in the capabilities
> > register extended by one bit.
> >
> > (Should we implement a dedicated quirk for this? I.e.
> > SDHCI_QUIRK_MAX_BLK_SZ_4096?)
> >
>
> Yes please. It would have to mean "always support 4096" though, not
> "turn reserved bit 18 into a block length bit".
OK.
> > 2) sdhci_init() is needed after error conditions.
> >
> > (Can we safely do this for all controllers?)
> >
>
> Please investigate which part of sdhci_init() is needed. How does it
> break without this?
After reset eSDHC lose signal/interrupt enable states:
Before reset:
sdhci: ============== REGISTER DUMP ==============
sdhci: Sys addr: 0x00000008 | Version: 0x00000000
sdhci: Blk size: 0x00000008 | Blk cnt: 0x00000000
sdhci: Argument: 0x000001aa | Trn mode: 0x00000000
sdhci: Present: 0xff850000 | Host ctl: 0x00000021
sdhci: Power: 0x00000000 | Blk gap: 0x00000000
sdhci: Wake-up: 0x00000000 | Clock: 0x00001077
sdhci: Timeout: 0x00000000 | Int stat: 0x00000000
sdhci: Int enab: 0x007f0003 | Sig enab: 0x007f0003
sdhci: AC12 err: 0x00000000 | Slot int: 0x00000001
sdhci: Caps: 0x01e30000 | Max curr: 0x00000000
sdhci: ===========================================
after sdhci_reset(host, SDHCI_RESET_CMD):
sdhci: ============== REGISTER DUMP ==============
sdhci: Sys addr: 0x00000008 | Version: 0x00000000
sdhci: Blk size: 0x00000008 | Blk cnt: 0x00000000
sdhci: Argument: 0x00000000 | Trn mode: 0x00000000
sdhci: Present: 0xff850000 | Host ctl: 0x00000021
sdhci: Power: 0x00000000 | Blk gap: 0x00000000
sdhci: Wake-up: 0x00000000 | Clock: 0x00001077
sdhci: Timeout: 0x00000000 | Int stat: 0x00000000
sdhci: Int enab: 0x017f0003 | Sig enab: 0x00700002
sdhci: AC12 err: 0x00000000 | Slot int: 0x00000001
sdhci: Caps: 0x01e30000 | Max curr: 0x00000000
sdhci: ===========================================
After sdhci_reset(host, SDHCI_RESET_DATA):
sdhci: ============== REGISTER DUMP ==============
sdhci: Sys addr: 0x00000008 | Version: 0x00000000
sdhci: Blk size: 0x00000008 | Blk cnt: 0x00000000
sdhci: Argument: 0x00000000 | Trn mode: 0x00000000
sdhci: Present: 0xff850000 | Host ctl: 0x00000021
sdhci: Power: 0x00000000 | Blk gap: 0x00000000
sdhci: Wake-up: 0x00000000 | Clock: 0x00001077
sdhci: Timeout: 0x00000000 | Int stat: 0x00000000
sdhci: Int enab: 0x117f003f | Sig enab: 0x00000000
sdhci: AC12 err: 0x00000000 | Slot int: 0x00000001
sdhci: Caps: 0x01e30000 | Max curr: 0x00000000
sdhci: ===========================================
> > 3) Small udelay is needed to make eSDHC work in PIO mode. Without
> > the delay reading causes endless interrupt storm, and writing
> > corrupts data. The first guess would be that we must wait for
> > some bit in some register, but I didn't find any reliable bits
> > that changes before and after the delay. Though, more investigation
> > on this is in my todo list.
>
> Please try to investigate more, but if you cannot improve it further
> then a specific quirk can be added.
No luck so far... :-/
Thanks,
--
Anton Vorontsov
email: cbouatmailru@gmail.com
irc://irc.freenode.net/bd2
next prev parent reply other threads:[~2009-02-13 14:42 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-06 18:05 [PATCH RFC 0/11] FSL eSDHC support: second call for comments Anton Vorontsov
2009-02-06 18:06 ` [PATCH 01/11] sdhci: Add quirk for controllers with no end-of-busy IRQ Anton Vorontsov
2009-02-06 18:06 ` [PATCH 02/11] sdhci: Add support for bus-specific IO memory accessors Anton Vorontsov
2009-02-08 20:50 ` Pierre Ossman
2009-02-13 14:40 ` Anton Vorontsov
2009-02-21 15:57 ` Pierre Ossman
2009-03-04 17:46 ` Anton Vorontsov
2009-03-08 14:08 ` Pierre Ossman
2009-02-06 18:06 ` [PATCH 03/11] sdhci: Add type checking for " Anton Vorontsov
2009-02-08 20:53 ` Pierre Ossman
2009-02-06 18:06 ` [PATCH 04/11] sdhci: Add support for card-detection polling Anton Vorontsov
2009-02-08 20:57 ` Pierre Ossman
2009-02-06 18:06 ` [PATCH 05/11] sdhci: Add support for hosts reporting inverted write-protect state Anton Vorontsov
2009-02-06 18:06 ` [PATCH 06/11] sdhci: Add support for hosts with strict 32 bit addressing Anton Vorontsov
2009-02-06 18:06 ` [PATCH 07/11] sdhci: Add quirk to suppress PIO interrupts during DMA transfers Anton Vorontsov
2009-02-08 21:02 ` Pierre Ossman
2009-02-06 18:06 ` [PATCH 08/11] sdhci: Add support for hosts that don't specify clocks in the cap. register Anton Vorontsov
2009-02-08 21:04 ` Pierre Ossman
2009-02-06 18:06 ` [PATCH 09/11] sdhci: Add set_clock callback Anton Vorontsov
2009-02-08 21:06 ` Pierre Ossman
2009-02-06 18:07 ` [PATCH 10/11] sdhci: Add quirk for Freescale eSDHC controllers Anton Vorontsov
2009-02-08 21:12 ` Pierre Ossman
2009-02-13 14:42 ` Anton Vorontsov [this message]
2009-02-06 18:07 ` [PATCH 11/11] mmc: Add OpenFirmware bindings for SDHCI driver Anton Vorontsov
2009-02-08 20:33 ` [PATCH RFC 0/11] FSL eSDHC support: second call for comments Pierre Ossman
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=20090213144238.GA12304@oksana.dev.rtsoft.ru \
--to=avorontsov@ru.mvista.com \
--cc=DaveLiu@freescale.com \
--cc=arnd@arndb.de \
--cc=ben-linux@fluff.org \
--cc=drzeus@drzeus.cx \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=sdhci-devel@list.drzeus.cx \
/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).