From: Alex Dubov <oakad@yahoo.com>
To: Maxim Levitsky <maximlevitsky@gmail.com>
Cc: linux-mtd <linux-mtd@lists.infradead.org>
Subject: Re: Legacy memstick support + FTL questions
Date: Mon, 22 Feb 2010 06:04:26 -0800 (PST) [thread overview]
Message-ID: <597490.7198.qm@web37607.mail.mud.yahoo.com> (raw)
In-Reply-To: <1266792159.3445.9.camel@maxim-laptop>
>
> Alex, could you explain how a single TPC is performed?
>
> I currently first send MS_TPC_SET_RW_REG_ADRS, and then
> MS_TPC_READ_REG
>
> When I send the TPC I specify both the tpc number and its
> len. Is the
> len transmitted?
Of course, it is. How otherwise media would know how many bits to sample
in?
>
> I see that if I set addr.r_length != MS_TPC_READ_REG len, I
> get errors
> in reg #16, but different errors depending if i set it
> lower or higher.
This is an undefined behavior. You're confusing the state machine on the
media side. By the way, left over bytes from the incorrectly ordered
or formatted TPC can spill into block data buffer (this will cause an
apparent data corruption - I've seen this happen).
>
> Currently I think that a level change on the #SDIO is the
> signal for
> host to start reading, but who sets the #BS to high? Host
> or card.
BS line is always mastered by host.
>
> Does card signal end of transmission?
>
Yes, on a data line (there's CRC as well, which must be handled by the host
transparently).
> Also it seems that if I write to 'param' register, I can't
> read it back
> (maybe I do something wrong). Is this register write only?
>
There are no write only registers in the MS spec. Moreover, you need to
read the param register if you're doing multi-page transfer (page address
will be updated during the transfer to point to the last accessed page).
next prev parent reply other threads:[~2010-02-22 14:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1266091737.30330.16.camel@maxim-laptop>
2010-02-14 15:06 ` Legacy memstick support + FTL questions Alex Dubov
2010-02-14 19:03 ` Maxim Levitsky
2010-02-16 14:15 ` Alex Dubov
2010-02-16 23:49 ` Maxim Levitsky
2010-02-17 2:26 ` Alex Dubov
2010-02-17 23:39 ` Maxim Levitsky
2010-02-21 22:42 ` Maxim Levitsky
2010-02-22 14:04 ` Alex Dubov [this message]
2010-02-22 23:11 ` Maxim Levitsky
2010-02-23 9:01 ` Alex Dubov
2010-02-24 1:10 ` Maxim Levitsky
2010-02-24 2:20 ` Alex Dubov
2010-01-26 21:43 Maxim Levitsky
2010-01-27 2:16 ` Alex Dubov
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=597490.7198.qm@web37607.mail.mud.yahoo.com \
--to=oakad@yahoo.com \
--cc=linux-mtd@lists.infradead.org \
--cc=maximlevitsky@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;
as well as URLs for NNTP newsgroup(s).