linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
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] Add the explanation and sample of RapidIO DTS sector to the document of booting-without-of.txt file.
Date: Wed, 13 Jun 2007 07:02:17 +0200	[thread overview]
Message-ID: <39c7d60cebf03badd106d7f75a08f449@kernel.crashing.org> (raw)
In-Reply-To: <1181638939310-git-send-email-wei.zhang@freescale.com>

> +   k) RapidIO
> +
> +   Required properties:
> +
> +    - device_type : Should be "rapidio"

There is no OF binding, so no.

> +    - compatible : Should be "fsl,rapidio-v0.0" or "fsl,rapidio-v1.0"
> +      and so on. The version number is got from IP Block Revision
> +      Register of RapidIO controller.

It's better to use real device names, just like everyone
else.

> +    - #address-cells : Address representation for "rapidio" devices.
> +      This field represents the number of cells needed to represent
> +      the RapidIO address of the registers.  For supporting more than
> +      36-bits RapidIO address, this field should be <2>.

More than 32 bit?

> +    - interrupt-parent : the phandle for the interrupt controller that
> +      services interrupts for this device.

Not required, depends on the interrupt tree of the system.

> +    - interrupts : <a b> where a is the interrupt number and b is a
> +      field that represents an encoding of the sense and level
> +      information for the interrupt.

No.  The format of an "interrupts" entry is defined by
the interrupt domain this device sits in, not by the
device itself.

> For this sector, interrupts order should be
> +      <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>.

That's to be defined in the binding for your specific device,
not in a more generic rapidio binding.

> +		#address-cells = <2>;

You want a #size-cells as well.

Hope this helps,


Segher

  parent reply	other threads:[~2007-06-13  5:02 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-12  9:02 [PATCH 0/5] Porting RapidIO driver from ppc to powerpc architecture and adding memory mapped RapidIO driver Zhang Wei
2007-06-12  9:02 ` [PATCH 1/5] Add the explanation and sample of RapidIO DTS sector to the document of booting-without-of.txt file Zhang Wei
2007-06-12  9:02   ` [PATCH 2/5] Add RapidIO sector to MPC8641HPCN board dts file Zhang Wei
2007-06-12  9:02     ` [PATCH 3/5] Add the platform device support with RapidIO to MPC8641HPCN platform Zhang Wei
2007-06-12  9:02       ` [PATCH 4/5] Add RapidIO support to powerpc architecture Zhang Wei
2007-06-12 22:58     ` [PATCH 2/5] Add RapidIO sector to MPC8641HPCN board dts file Phil Terry
2007-06-13  2:49       ` Zhang Wei-r63237
2007-06-13  5:02   ` Segher Boessenkool [this message]
2007-06-13  8:14     ` [PATCH 1/5] Add the explanation and sample of RapidIO DTS sector to the document of booting-without-of.txt file Zhang Wei-r63237
2007-06-13  8:28       ` Segher Boessenkool
2007-06-13  9:37         ` Zhang Wei-r63237
2007-06-13  9:48           ` Segher Boessenkool
2007-06-14  5:53         ` Kumar Gala
2007-06-14  7:52           ` Segher Boessenkool
2007-06-18  3:27             ` Zhang Wei-r63237
2007-06-18 12:43               ` Segher Boessenkool

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=39c7d60cebf03badd106d7f75a08f449@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 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).