public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Hans-Jürgen Koch" <hjk@linutronix.de>
To: David Brownell <david-b@pacbell.net>
Cc: dwmw2@infradead.org, Andrew Victor <andrew@sanpeople.com>,
	tglx@linutronix.de,
	Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: drivers/mtd/devices/at91_dataflash26.c
Date: Mon, 25 Jun 2007 08:35:04 +0200	[thread overview]
Message-ID: <200706250835.04848.hjk@linutronix.de> (raw)
In-Reply-To: <200706241951.37589.david-b@pacbell.net>

Am Montag 25 Juni 2007 04:51 schrieb David Brownell:
> On Thursday 10 May 2007, Hans-Jürgen Koch wrote:
> > Am Donnerstag 10 Mai 2007 22:07 schrieb David Brownell:
> > > On Friday 27 April 2007, David Brownell wrote:
> > > > On Friday 27 April 2007, Hans-Jürgen Koch wrote:
> > > > 
> > > > > > 	 the m25p80 driver
> > > > > > was pretty close to working with those Atmel devices too ...
> > > > > > most of the commands are identical.
> > > > > 
> > > > > Thanks for that hint, I'll have a look at the data sheet.
> > > 
> > > Any progress on that?  I looked again, and yes most commands
> > > are identical.
> 
> Still true.  :)

I came to the same conclusion.

> 
> For that and a boatload of other SPI flash chips.  I'm
> wondering just what that JEDEC standard covers; either
> it's got useful command coverage, or vendors of SPI flash
> noticed that converging command sets is a Good Thing.
> 
> 
> > >  - That driver relies on an AT91-only SPI stack that's not
> > >    going upstream, instead of drivers/spi/atmel_spi.c;
> > > 
> > >  - Driver can't even be selected on kernel.org kernel (!!);
> > > 
> > >  - The m25p80 driver will need at most minor tweaks to
> > >    handle those AT26 (and AT25) series chips;
> > > 
> > > So 340ea370c2ce89d1c15fbf785460f2f74314ce58 should be reverted.
> 
> Also still true...

I agree.

> 
> 
> > > 
> > > - Dave
> > >
> > 
> > Dave,
> > sorry for not responding earlier, I was busy with lots of other 
> > stuff. At the moment, I'm working on this again. I had a bit
> > of trouble getting a recent kernel working on my test system,
> > but that seems to be OK now.
> > 
> > You'll hear from me soon.
> 
> Ping?  Have a look at
> 
>     http://lists.infradead.org/pipermail/linux-mtd/2007-June/018706.html

Great! Didn't notice that one.

> 
> which depends on the resent mutex conversion patch in the
> "previous message" link of that patch.
> 
> That should highlight more reasons why at91_dataflash should
> be reverted ASAP.  I'd expect you would be able to just drop
> that in and have it work ... 

Looks like that.

> unless you're seeing that nCS0 
> issue built out of at91rm9200 errata, in which case there's
> an experiment I can forward to you.  :)

I'll look at that ASAP. I had tons of other work on my desk and last time
I tried, SPI was broken on my device. It would be OK for me if you threw out
that at91_dataflash/at91_dataflash26 stuff now.

Thanks,
Hans


      reply	other threads:[~2007-06-25  6:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200704271812.26392.david-b@pacbell.net>
     [not found] ` <200704280336.44913.hjk@linutronix.de>
     [not found]   ` <200704271908.17403.david-b@pacbell.net>
2007-05-10 20:07     ` drivers/mtd/devices/at91_dataflash26.c David Brownell
2007-05-10 21:19       ` drivers/mtd/devices/at91_dataflash26.c Thomas Gleixner
2007-05-10 21:34         ` drivers/mtd/devices/at91_dataflash26.c David Brownell
2007-05-10 21:31       ` drivers/mtd/devices/at91_dataflash26.c Hans-Jürgen Koch
2007-06-25  2:51         ` drivers/mtd/devices/at91_dataflash26.c David Brownell
2007-06-25  6:35           ` Hans-Jürgen Koch [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=200706250835.04848.hjk@linutronix.de \
    --to=hjk@linutronix.de \
    --cc=andrew@sanpeople.com \
    --cc=david-b@pacbell.net \
    --cc=dwmw2@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tglx@linutronix.de \
    /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