From: Segher Boessenkool <segher@kernel.crashing.org>
To: Jason Jin <Jason.jin@freescale.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH 1/4 V2] booting-without-of for Freescale MSI
Date: Fri, 9 May 2008 11:26:46 +0200 [thread overview]
Message-ID: <c6e4b0f3534e38db766d76fd6450f163@kernel.crashing.org> (raw)
In-Reply-To: <1210323810-24833-1-git-send-email-Jason.jin@freescale.com>
Hi Jason,
Some more comments...
> + - compatible : set as "fsl,86xx-MSI" for 86xx cpu, "fsl,85xx-MSI"
> for 85xx
> + cpu and "fsl,83xx-MSI" for 83xx cpu.
Don't use "xx", use real device names instead. If for example the
oldest
86xx device that implements this is 8600, and you write a tree for the
8699,
you'd write compatible = "fsl,8699-msi", "fsl,8600-msi"; and the
driver
will look for "fsl,8600-msi" only usually, but it can take some special
actions for 8699 if it needs to.
If these MSI devices work really identical for 83xx, 85xx, 86xx, there
is
no need to distinguish between them for probing either -- you want to
use
the same driver for all, anyway.
Oh, and the norm is to write compatible values in lower case.
> + - msi-available-ranges: use <start count> style section to define
> which
> + msi interrupt can be used in the 256 msi interrupts.
Please make this property optional, default to "all available".
Segher
next prev parent reply other threads:[~2008-05-09 9:27 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-09 9:03 [PATCH 1/4 V2] booting-without-of for Freescale MSI Jason Jin
2008-05-09 9:03 ` [PATCH 2/4 V4] MSI support on 83xx/85xx/86xx board Jason Jin
2008-05-09 12:21 ` Michael Ellerman
2008-05-13 2:18 ` Jin Zhengxiong
2008-05-09 13:31 ` Grant Likely
2008-05-09 9:26 ` Segher Boessenkool [this message]
2008-05-09 9:52 ` [PATCH 1/4 V2] booting-without-of for Freescale MSI Jin Zhengxiong
2008-05-09 10:13 ` Segher Boessenkool
2008-05-09 10:18 ` Jin Zhengxiong
2008-05-09 10:51 ` Segher Boessenkool
2008-05-09 13:25 ` Grant Likely
2008-05-13 2:31 ` Jin Zhengxiong
2008-05-09 13:34 ` Grant Likely
2008-05-09 16:18 ` Timur Tabi
2008-05-09 16:24 ` Grant Likely
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=c6e4b0f3534e38db766d76fd6450f163@kernel.crashing.org \
--to=segher@kernel.crashing.org \
--cc=Jason.jin@freescale.com \
--cc=linuxppc-dev@ozlabs.org \
/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).