From: Thomas Gleixner <tglx@linutronix.de>
To: Ian Molton <spyro@f2s.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: Support of stupid devices
Date: Mon, 16 Aug 2004 15:11:17 +0200 [thread overview]
Message-ID: <1092661877.4354.10.camel@lap02.tec.linutronix.de> (raw)
In-Reply-To: <20040816013933.163a101d.spyro@f2s.com>
On Mon, 2004-08-16 at 02:39, Ian Molton wrote:
> Hi.
>
> Im porting linux to the toshiba e7xx and 8xx PDAs
> which contain a nand flash controller.
> Im not certain, but it appears the controllerhas an
> odd quirk meaning byte-reads of the data register
> dont work as the linux mtd code expects.
>
> AFAICT if I read a word (after issuing a chipid command) I get:
>
> 0xYYZZ75ec -- this is good - Samsung, 32MB device.
>
> if I do two byte reads I get 0xec 0xec.
>
> a halfword access gets me 0xYYZZ.
> a misaligned (by one byte) word access gives me 0xecYYZZ75,
Sounds really stupid :)
> but this fails to work for byte accesses. halfword misaligned
> accesses are just weird.
> so basically, the only way to read the chipid is to do:
> a word access to the data reg and then shift the data out
> or
> a word access (and mask off the high 3 bytes followed by a
> misaligned word access and mask off the upper 3 bytes.
> clearly the former solution is the better one, but this
> doesnt fit in the nand driver model very well
> (read_byte() et.al.)
You can provide your own read_byte() et. al. functions which do all the
magic. Look into the other Toshiba nand driver implementations. They do
the same. I don't have the header files which implement the real access
but Alice should be a source of help.
> the chip is a TC6393XB (system on chip) and the flash
> is a samsung K9F5608UOC YCBO
tglx
> ______________________________________________________
> Linux MTD discussion mailing list
> http://lists.infradead.org/mailman/listinfo/linux-mtd/
prev parent reply other threads:[~2004-08-16 13:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-16 0:39 Support of stupid devices Ian Molton
2004-08-16 13:11 ` Thomas Gleixner [this message]
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=1092661877.4354.10.camel@lap02.tec.linutronix.de \
--to=tglx@linutronix.de \
--cc=linux-mtd@lists.infradead.org \
--cc=spyro@f2s.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