From: "Steven A. Falco" <sfalco@harris.com>
To: avorontsov@ru.mvista.com
Cc: "Sparks, Sam" <SSparks@aclaratech.com>,
linuxppc-dev@ozlabs.org, linux-ide@vger.kernel.org,
Stefan Roese <sr@denx.de>, Jeff Garzik <jgarzik@pobox.com>
Subject: Re: [PATCH] pata_of_platform: fix no irq handling
Date: Wed, 13 Aug 2008 17:25:59 -0400 [thread overview]
Message-ID: <48A35167.6030001@harris.com> (raw)
In-Reply-To: <20080812143110.GA23961@oksana.dev.rtsoft.ru>
[-- Attachment #1: Type: text/plain, Size: 1989 bytes --]
Anton Vorontsov wrote:
> On Tue, Aug 12, 2008 at 06:18:42PM +0400, Sergei Shtylyov wrote:
>
>> Anton Vorontsov wrote:
>>
>>
>>>>>> 1. IDE status read does not work. (But am I understand correctly
>>>>>> that IDE works well if IRQ is unspecified? Then this is hardly
>>>>>> an issue.)
>>>>>> 2. IDE interrupt comes when it should not. I'd recommend to use
>>>>>> oscilloscope to find out what is happening there, that is, if
>>>>>> the drive actually deasserts its irq line after status read.
>>>>>> If so, than this could be a PIC problem.
>>>>>>
>>>>>> What is the platform on which you're observing the issue, btw?
>>>>>>
>>>>> Another possibility is that you got the wrong interrupt number
>>>>> in the device-tree...
>>>>>
>>>>> Ben.
>>>>>
>>>> The platform is the AMCC Sequoia board. We've built a little adapter to
>>>> connect a compact flash card to the processor bus. I believe the
>>>> interrupt selection in the device tree is correct, and I've checked over
>>>> the u-boot settings for the IRQ line (active high, level sensitive).
>>>>
>>> IDE IRQs are active-low.
>>>
>> Only on the PCI and only in the native mode. Natively, the IDE INTRQ
>> signal is active-high, rising edge triggering, as on ISA. You seem to
>> have an invertor somewhere, if it's not a PCI chip...
>>
>
> Ugh. Right you are, as always. I've just looked into mpc8349emitx
> schematics, there is indeed an inverter on the irq line.
>
> CF in True IDE mode is active-high, sorry.
>
Ok, just to close this issue, my CF device is now working perfectly.
Two problems, both my fault. 1) I thought the alternate registers used
the same reg-shift and offset, so the alt_command and alt_status were at
the wrong address, and 2) I was missing a pull-down on the IRQ line -
the sequoia eval board has it in the schematic, but it is marked "not
populated".
Thanks to all for your comments and help,
Steve
[-- Attachment #2: Type: text/html, Size: 3345 bytes --]
next prev parent reply other threads:[~2008-08-13 21:26 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-11 14:48 Possible bug in IRQ handling in pata_of_platform / pata_platform Steven A. Falco
2008-08-11 15:19 ` [PATCH] pata_of_platform: fix no irq handling Anton Vorontsov
2008-08-11 16:23 ` Steven A. Falco
2008-08-11 17:07 ` Anton Vorontsov
2008-08-11 22:00 ` Benjamin Herrenschmidt
2008-08-12 14:00 ` Steven A. Falco
2008-08-12 14:04 ` Anton Vorontsov
2008-08-12 14:18 ` Stefan Roese
2008-08-12 14:18 ` Sergei Shtylyov
2008-08-12 14:31 ` Anton Vorontsov
2008-08-13 21:25 ` Steven A. Falco [this message]
2008-08-11 16:29 ` Alan Cox
2008-08-11 16:36 ` Ben Dooks
2008-08-11 16:26 ` Alan Cox
2008-08-11 16:42 ` Steven A. Falco
2008-08-11 22:02 ` Benjamin Herrenschmidt
-- strict thread matches above, loose matches on Subject: below --
2008-09-25 8:36 [PATCH] pata_platform struct resource signness fix Wang Jian
2008-09-25 8:54 ` Wang Jian
2008-09-25 10:40 ` Li Yang
2008-09-25 10:48 ` Anton Vorontsov
2008-09-29 4:19 ` Jeff Garzik
2008-09-29 13:32 ` [PATCH] pata_of_platform: fix no irq handling Anton Vorontsov
2008-10-06 17:26 Anton Vorontsov
2008-10-06 20:41 ` Matt Sealey
2008-10-06 21:32 ` Anton Vorontsov
2008-10-07 1:30 ` Tejun Heo
2008-10-07 9:18 ` Wang Jian
2008-10-07 9:26 ` Anton Vorontsov
2008-10-07 10:04 ` Benjamin Herrenschmidt
2008-10-07 9:37 ` Alan Cox
2008-10-08 8:40 ` David Woodhouse
2008-10-08 9:00 ` Alan Cox
2008-10-08 9:59 ` Geert Uytterhoeven
2008-10-08 10:27 ` Alan Cox
2008-10-10 17:55 ` Paul Mundt
2008-10-13 6:56 ` Tejun Heo
2008-10-13 23:27 ` Benjamin Herrenschmidt
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=48A35167.6030001@harris.com \
--to=sfalco@harris.com \
--cc=SSparks@aclaratech.com \
--cc=avorontsov@ru.mvista.com \
--cc=jgarzik@pobox.com \
--cc=linux-ide@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=sr@denx.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;
as well as URLs for NNTP newsgroup(s).