From: Sergei Shtylyov <sshtylyov@ru.mvista.com>
To: avorontsov@ru.mvista.com
Cc: "Steven A. Falco" <sfalco@harris.com>,
linux-ide@vger.kernel.org, Jeff Garzik <jgarzik@pobox.com>,
"Sparks, Sam" <SSparks@aclaratech.com>,
linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] pata_of_platform: fix no irq handling
Date: Tue, 12 Aug 2008 18:18:42 +0400 [thread overview]
Message-ID: <48A19BC2.8060008@ru.mvista.com> (raw)
In-Reply-To: <20080812140457.GA9103@oksana.dev.rtsoft.ru>
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...
WBR, Sergei
next prev parent reply other threads:[~2008-08-12 14:18 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <48A05152.7020508@harris.com>
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 [this message]
2008-08-12 14:31 ` Anton Vorontsov
2008-08-13 21:25 ` Steven A. Falco
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
[not found] <20080925083622.GA2701@debian>
[not found] ` <48DB51C3.6040504@linux.net.cn>
2008-09-25 10:40 ` [PATCH] pata_platform struct resource signness fix 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 13:27 ` Jeff Garzik
2008-10-13 13:53 ` 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=48A19BC2.8060008@ru.mvista.com \
--to=sshtylyov@ru.mvista.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=sfalco@harris.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;
as well as URLs for NNTP newsgroup(s).