From: Segher Boessenkool <segher@kernel.crashing.org>
To: Zhang Wei <wei.zhang@freescale.com>
Cc: linuxppc-dev@ozlabs.org, paulus@samba.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/5 v3] Add the explanation and a sample of RapidIO OF node to the document of booting-without-of.txt file.
Date: Tue, 31 Jul 2007 18:19:44 +0200 [thread overview]
Message-ID: <14098723940361a2b58ccd251a381f11@kernel.crashing.org> (raw)
In-Reply-To: <11854393733580-git-send-email-wei.zhang@freescale.com>
> + l) RapidIO
"FSL PowerPC bridge RapidIO" or something like that -- you
aren't doing a _generic_ rapidio binding here.
> + RapidIO is a definition of a system interconnect. This node add
> + the support for RapidIO processor in kernel. The node name is
> + suggested to be 'rapidio'.
> +
> + Required properties:
> +
> + - compatible : Using "fsl,rapidio-delta" for Freescale PowerPC
> + RapidIO controller.
> + - #address-cells : Address representation for "rapidio" devices.
> + This field represents the number of cells needed to represent
> + the RapidIO address of the registers.
> + See 1) above for more details on defining #address-cells.
> + - reg : Offset and length of the register set for the device
> + - ranges : Should be defined as specified in 1) to describe the
> + translation of addresses for memory mapped RapidIO memory
> + space.
> + - interrupts : binding interrupts for this device node,
> + please follow below orders:
> + <err_irq bell_outb_irq bell_inb_irq msg1_tx_irq msg1_rx_irq
> + msg2_tx_irq msg2_rx_irq ... msgN_tx_irq msgN_rx_irq>.
_All_ of these are "as specified in 1)". You should be saying
the specifics for your device here; for example, what register
blocks of your controller are described in "reg", and in what
order?
Segher
WARNING: multiple messages have this Message-ID (diff)
From: Segher Boessenkool <segher@kernel.crashing.org>
To: Zhang Wei <wei.zhang@freescale.com>
Cc: linux-kernel@vger.kernel.org, galak@kernel.crashing.org,
mporter@kernel.crashing.org, paulus@samba.org,
linuxppc-dev@ozlabs.org
Subject: Re: [PATCH 1/5 v3] Add the explanation and a sample of RapidIO OF node to the document of booting-without-of.txt file.
Date: Tue, 31 Jul 2007 18:19:44 +0200 [thread overview]
Message-ID: <14098723940361a2b58ccd251a381f11@kernel.crashing.org> (raw)
In-Reply-To: <11854393733580-git-send-email-wei.zhang@freescale.com>
> + l) RapidIO
"FSL PowerPC bridge RapidIO" or something like that -- you
aren't doing a _generic_ rapidio binding here.
> + RapidIO is a definition of a system interconnect. This node add
> + the support for RapidIO processor in kernel. The node name is
> + suggested to be 'rapidio'.
> +
> + Required properties:
> +
> + - compatible : Using "fsl,rapidio-delta" for Freescale PowerPC
> + RapidIO controller.
> + - #address-cells : Address representation for "rapidio" devices.
> + This field represents the number of cells needed to represent
> + the RapidIO address of the registers.
> + See 1) above for more details on defining #address-cells.
> + - reg : Offset and length of the register set for the device
> + - ranges : Should be defined as specified in 1) to describe the
> + translation of addresses for memory mapped RapidIO memory
> + space.
> + - interrupts : binding interrupts for this device node,
> + please follow below orders:
> + <err_irq bell_outb_irq bell_inb_irq msg1_tx_irq msg1_rx_irq
> + msg2_tx_irq msg2_rx_irq ... msgN_tx_irq msgN_rx_irq>.
_All_ of these are "as specified in 1)". You should be saying
the specifics for your device here; for example, what register
blocks of your controller are described in "reg", and in what
order?
Segher
next prev parent reply other threads:[~2007-07-31 16:19 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-26 8:42 [PATCH 0/5 v3] Porting RapidIO driver from ppc to powerpc architecture and adding memory mapped RapidIO driver Zhang Wei
2007-07-26 8:42 ` Zhang Wei
2007-07-26 8:42 ` [PATCH 1/5 v3] Add the explanation and a sample of RapidIO OF node to the document of booting-without-of.txt file Zhang Wei
2007-07-26 8:42 ` Zhang Wei
2007-07-26 8:42 ` [PATCH 2/5 v3] Add RapidIO OF-node to the MPC8641HPCN board dts file Zhang Wei
2007-07-26 8:42 ` Zhang Wei
2007-07-26 8:42 ` [PATCH 3/5 v3] Add the platform device support with RapidIO to MPC8641HPCN platform Zhang Wei
2007-07-26 8:42 ` Zhang Wei
2007-07-26 8:42 ` [PATCH 4/5 v3] Add RapidIO support to powerpc architecture Zhang Wei
2007-07-26 8:42 ` Zhang Wei
2007-07-26 8:42 ` [PATCH 5/5 v3] Add the memory management driver to RapidIO Zhang Wei
2007-07-26 8:42 ` Zhang Wei
2008-01-24 7:01 ` Kumar Gala
2008-01-24 7:01 ` Kumar Gala
2007-07-27 8:12 ` [PATCH 4/5 v3] Add RapidIO support to powerpc architecture Stephen Rothwell
2007-07-27 8:12 ` Stephen Rothwell
2007-07-27 8:22 ` Kumar Gala
2007-07-27 8:22 ` Kumar Gala
2007-07-27 9:03 ` Zhang Wei-r63237
2007-07-27 9:03 ` Zhang Wei-r63237
2007-07-27 7:54 ` [PATCH 3/5 v3] Add the platform device support with RapidIO to MPC8641HPCN platform Stephen Rothwell
2007-07-27 7:54 ` Stephen Rothwell
2007-07-29 13:56 ` Arnd Bergmann
2007-07-29 13:56 ` Arnd Bergmann
2007-07-30 8:26 ` Zhang Wei-r63237
2007-07-30 8:26 ` Zhang Wei-r63237
2007-07-27 8:51 ` [PATCH 1/5 v3] Add the explanation and a sample of RapidIO OF node to the document of booting-without-of.txt file Kumar Gala
2007-07-27 8:51 ` Kumar Gala
2007-07-27 9:12 ` Zhang Wei-r63237
2007-07-27 9:12 ` Zhang Wei-r63237
2007-07-31 16:15 ` Segher Boessenkool
2007-07-31 16:15 ` Segher Boessenkool
2007-07-31 16:19 ` Segher Boessenkool [this message]
2007-07-31 16:19 ` Segher Boessenkool
2007-07-27 8:28 ` [PATCH 0/5 v3] Porting RapidIO driver from ppc to powerpc architecture and adding memory mapped RapidIO driver Kumar Gala
2007-07-27 8:28 ` Kumar Gala
2007-10-29 19:38 ` Phil Terry
2007-10-29 19:38 ` Phil Terry
2007-10-29 20:30 ` Kumar Gala
2007-10-29 20:30 ` Kumar Gala
2007-10-30 8:40 ` Zhang Wei-r63237
2007-10-30 8:40 ` Zhang Wei-r63237
2007-11-09 22:34 ` Randy Vinson
2007-11-12 2:18 ` Zhang Wei-r63237
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=14098723940361a2b58ccd251a381f11@kernel.crashing.org \
--to=segher@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.org \
--cc=wei.zhang@freescale.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 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.