linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marek Vasut <marek.vasut@gmail.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Russell King - ARM Linux <linux@arm.linux.org.uk>,
	Jeff Garzik <jgarzik@pobox.com>,
	linux-arm-kernel@lists.arm.linux.org.uk,
	Eric Miao <eric.y.miao@gmail.com>,
	linux-ide@vger.kernel.org
Subject: Re: [PATCH 4/6] PalmLD IDE
Date: Tue, 21 Apr 2009 19:44:08 +0200	[thread overview]
Message-ID: <200904211944.08970.marek.vasut@gmail.com> (raw)
In-Reply-To: <20090421161933.334bc5a2@lxorguk.ukuu.org.uk>

On Tuesday 21 of April 2009 17:19:33 Alan Cox wrote:
> > http://www.palm.com/us/support/contact/environment/disassem_inst_Lifedriv
> >e.pdf , see slide 10 and 15 for yourself, I think noone would want to
> > solder anything into that device ;-)
>
> Agreed but if the hardware can do it you don't need the flag. Obviously
> not very important in this case.

OK, we can remove that, I'll resend the patch.
>
> > > +	/* we'd better wait for drive's ready signal here
> > > +	  (if we knew where it will come from) */
> > > +	msleep(300);
> > >
> > > Our probe code should already be waiting for ready signals  ?
> >
> > The drive asserts some GPIO when it becomes ready, dunno which one though
> > so we just wait here.
>
> Ok so the ATA bus side ready isn't sufficient for your hardware ?

I can retry without the delay, but I'm quite afraid I ran into problems 
without it. Btw. I rewrote that driver more than half year ago, so I don't 
really recall the details, sorry, I don't want to misinform you here.
>
> > > The only other question is a general architectural one as to whether it
> > > would be better to set up the GPIO etc and create a pata_platform
> > > platform device (possibly tweaking pata_platform flags to allow the
> > > caller to indicate generic pio with mode setting by set features
> > > command)
> >
> > I already explained this to Eric, there isn't any other obscure hardware
> > I think. Or if this is concerning something else, I'll recheck later.



  reply	other threads:[~2009-04-21 17:44 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-21  0:05 [PATCH 4/6] PalmLD IDE Marek Vasut
2009-04-21 14:27 ` Alan Cox
2009-04-21 14:52   ` Marek Vasut
2009-04-21 15:19     ` Alan Cox
2009-04-21 17:44       ` Marek Vasut [this message]
2009-04-21 19:35         ` Alan Cox
2009-04-21 19:38           ` Jeff Garzik
  -- strict thread matches above, loose matches on Subject: below --
2009-03-22 21:23 Marek Vasut
2009-04-19 16:14 ` Marek Vasut
2009-04-20 20:38   ` Bartlomiej Zolnierkiewicz
2009-04-20 20:53     ` Marek Vasut
2009-04-20 21:01       ` Bartlomiej Zolnierkiewicz
2009-04-20 21:17       ` Alan Cox
2009-04-21  4:02 ` Eric Miao
2009-04-21 14:01   ` Marek Vasut
     [not found] <200808132252.23732.marek.vasut@gmail.com>
     [not found] ` <20080816090803.GI5946@flint.arm.linux.org.uk>
2008-08-16 14:30   ` Marek Vasut

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=200904211944.08970.marek.vasut@gmail.com \
    --to=marek.vasut@gmail.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=eric.y.miao@gmail.com \
    --cc=jgarzik@pobox.com \
    --cc=linux-arm-kernel@lists.arm.linux.org.uk \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    /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).