All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Radovan Vápeník" <radovan.vapenik@tcz.cz>
To: Stanislaw Gruszka <stf_xl@wp.pl>
Cc: linux-ide@vger.kernel.org
Subject: Re: AT91 IDE module
Date: Thu, 02 Dec 2010 17:10:21 +0100	[thread overview]
Message-ID: <4CF7C4ED.6070400@tcz.cz> (raw)
In-Reply-To: <20101126182045.GA3404@r2bh72.net.upc.cz>

Stanislaw Gruszka napsal(a):
> On Thu, Nov 25, 2010 at 09:53:19PM +0100, Radovan Vapeník wrote:
>   
>>> We do not detect any IDE device, registers do not contain status/data
>>> that IDE layer expect. As far only two possible reasons of that
>>> problem come in mind:
>>> - board specific code does not reset CF device (with proper
>>>  reset duration?). This is expected, there is rst_pin in
>>>  struct at91_cf_data but driver does not use it
>>> - CF 9 pin (ATA SEL) is not grounded or set to 0 if connected
>>>  to controller (also in board specific initialization code)
>>>
>>> To debug problem further, you can add your own code at the end of
>>> at91_ide_probe(), which read/write IDE register to see if device
>>> react properly and give some sensible status values.
>>>
>>> Stanislaw
>>>
>>>       
>> Seems problem is really on reset pin, i have analysed using
>> oscilloscope and on reset pin is still in logical "1", without
>> change during module loading. I will try to find out why is this
>> happening.
>>     
>
> I was unclear. Driver does not change reset pin. Reset need to be
> done in board initialization code. You have to add something like that
>
> #define RST_PIN AT91_PIN_PC5
> at91_set_gpio_output(RST_PIN, 1);
> at91_set_gpio_value(RST_PIN,0);
> mdelay(2);
> at91_set_gpio_value(RST_PIN,1);
>
> in your arch/arm/mach-at91/board-NAME.c (I'm not sure if 2ms is
> correct IDE reset duration).
>
> Stanislaw
>
>   
I found out the reason of transients - it is caused by enabled pull-up
resistor on lower 16 bits on EBI0 - bit EBI0_DBPUC shoul be set to "1",
normally is set to "0". But the CF still no working, problem is is
elsewhere.

Radovan

I had mistake in schematic - after repair I get some new debug messages 
- is possible to tell, what can be wrong? Thanks for advice

at91_ide_probe chipselect 4 irq 132 res 50000000
apply_timings t0=600 t1=70 t2=290 t6z=30
apply_timings mck_hz=99328000
apply_timings cycle=60 setup=7 pulse=29 data_float=3
Probing IDE interface ide0...
probing for hda: present=0, media=32, probetype=ATA
probing for hda: present=0, media=32, probetype=ATAPI
hda: probing with STATUS(0xa0) instead of ALTSTATUS(0x00)
hda: probing with STATUS(0xa0) instead of ALTSTATUS(0x1e)
probing for hdb: present=0, media=32, probetype=ATA
probing for hdb: present=0, media=32, probetype=ATAPI
hdb: probing with STATUS(0xa0) instead of ALTSTATUS(0x1e)
hdb: probing with STATUS(0xa0) instead of ALTSTATUS(0x1e)
ide0 at 0xc4866000-0xc4866007,0xc486e006 on irq 132

Radovan


  parent reply	other threads:[~2010-12-02 16:10 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4CEB8FB8.80702@tcz.cz>
2010-11-23 21:00 ` AT91 IDE module Stanislaw Gruszka
2010-11-24  9:36   ` Radovan Vápeník
2010-11-24 21:50     ` Stanislaw Gruszka
2010-11-25 20:53       ` Radovan Vapeník
2010-11-26 18:20         ` Stanislaw Gruszka
2010-11-29 14:12           ` Radovan Vápeník
2010-11-30 14:32           ` Radovan Vápeník
2010-12-02 16:10           ` Radovan Vápeník [this message]
2010-12-04 20:16             ` Stanislaw Gruszka

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=4CF7C4ED.6070400@tcz.cz \
    --to=radovan.vapenik@tcz.cz \
    --cc=linux-ide@vger.kernel.org \
    --cc=stf_xl@wp.pl \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.