From: Segher Boessenkool <segher@kernel•crashing.org>
To: "Gerhard Pircher" <gerhard_pircher@gmx•net>
Cc: linuxppc-dev@ozlabs•org, david@gibson•dropbear.id.au
Subject: Re: [RFC] AmigaOne device tree source v2
Date: Thu, 6 Sep 2007 15:41:57 +0200 [thread overview]
Message-ID: <d6f9e35f29d20d697e2f9176011adb70@kernel.crashing.org> (raw)
In-Reply-To: <20070904122040.276440@gmx.net>
> BTW: It looks like the Pegasos II device tree defines device_type =
> "spi"
> for the IDE controller. Is that correct?
There is no standard binding for an "spi" device type. I have no
idea which of various "SPI" kind of devices is meant here; and none
of the ones I know of have anything to do with ATA anyway.
In short, it probably is incorrect.
Also, in general, you shouldn't use "device_type" in flat device
trees (the main exceptions are: some/most bus nodes, cpu nodes,
some other "standard" nodes).
>> There is no such thing as "interrupt 14 and 15" on PCI. You can use
>> the interrupt mapping recommended practice to show two interrupts
>> (and their polarity, and how they are routed to the relevant interrupt
>> controller) in the IDE node.
> But I'll still need a quirk in the IDE driver, because it doesn't make
> use of any interrupt routing information in the device tree. If so, I
> can omit the whole IDE controller device node and simply rely on the
> IDE driver's probe functions and the Pegasos IDE IRQ quirk.
> I wonder how this issue will be handled for libata and the via-pata
> driver, since IIRC this one doesn't contain the Pegasos IDE IRQ quirk.
I imagine the ata quirk would ask the arch or platform code about
the interrupts used; it in turn can query the device tree.
Segher
next prev parent reply other threads:[~2007-09-06 13:41 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-31 17:50 [RFC] AmigaOne device tree source v2 Gerhard Pircher
2007-09-03 1:34 ` David Gibson
2007-09-03 8:41 ` Benjamin Herrenschmidt
2007-09-03 10:02 ` Segher Boessenkool
2007-09-03 10:12 ` David Gibson
2007-09-03 16:11 ` Gerhard Pircher
2007-09-03 22:52 ` Segher Boessenkool
2007-09-04 0:27 ` David Gibson
2007-09-06 13:31 ` Segher Boessenkool
2007-09-04 12:20 ` Gerhard Pircher
2007-09-06 13:41 ` Segher Boessenkool [this message]
2007-09-03 14:58 ` Gerhard Pircher
2007-09-03 22:32 ` Segher Boessenkool
2007-09-04 11:49 ` Gerhard Pircher
2007-09-05 2:48 ` David Gibson
2007-09-05 11:54 ` Gerhard Pircher
2007-09-06 14:00 ` Segher Boessenkool
2007-09-06 14:09 ` Sven Luther
2007-09-06 14:42 ` Segher Boessenkool
2007-09-06 13:56 ` Segher Boessenkool
2007-09-06 14:15 ` PCI I/O space -- reg or ranges? Scott Wood
2007-09-06 20:51 ` Gerhard Pircher
2007-09-06 21:01 ` Segher Boessenkool
2007-09-07 0:20 ` [RFC] AmigaOne device tree source v2 David Gibson
2007-09-06 13:36 ` Segher Boessenkool
2007-09-06 21:09 ` Gerhard Pircher
2007-09-07 0:21 ` David Gibson
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=d6f9e35f29d20d697e2f9176011adb70@kernel.crashing.org \
--to=segher@kernel$(echo .)crashing.org \
--cc=david@gibson$(echo .)dropbear.id.au \
--cc=gerhard_pircher@gmx$(echo .)net \
--cc=linuxppc-dev@ozlabs$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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