linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robherring2@gmail.com>
To: Scott Wood <scottwood@freescale.com>
Cc: Valentin Longchamp <valentin.longchamp@keymile.com>,
	linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Subject: Re: [PATCH v3 2/3] devcietree: bindings: add some MFD Keymile FPGAs
Date: Thu, 10 Apr 2014 10:06:29 -0500	[thread overview]
Message-ID: <CAL_JsqLLD4fAuhDzdQPWNSbWj444kWESvsprMBFmStUF-QNTiQ@mail.gmail.com> (raw)
In-Reply-To: <1397004291.32034.327.camel@snotra.buserror.net>

On Tue, Apr 8, 2014 at 7:44 PM, Scott Wood <scottwood@freescale.com> wrote:
> On Tue, 2014-03-25 at 14:41 +0100, Valentin Longchamp wrote:
>> These are the bindings for 2 MFD devices used on some of the Keymile boards.
>> The first one is the chassis managmenet bfticu FPGA.
>> The second one is the board controller (reset, LEDs, GPIOs) QRIO CPDL.
>> These FPGAs are used in the kmcoge4 board.
>>
>> This patch also add KEYMILE to the vendor-prefixes.

You can drop the keymile addition. I have that queued up.

[snip]

>> +Required properties:
>> +- compatible: "keymile,bfticu"
>> +- interrupt-controller: the bfticu FPGA is an interrupt controller
>> +- interrupts: the main IRQ line to signal the collected IRQs
>> +- #interrupt-cells : is 2
>> +     - The 1st cell is the local IRQ number on the bfticu
>> +     - The 2nd cell is the type of the IRQ (IRQ_TYPE_xxx)
>
> Device tree bindings should not depend on the content of Linux headers.
> One is stable ABI, and the other isn't.
>
> If you want you can make the values the same for convenience, as is done
> by IPIC, CPM PIC, etc -- but the values need to be explicitly stated in
> the binding.  It'll still break if the Linux values change (so it may
> not be a good idea to try to keep the values the same), but at least the
> fix would be in Linux code rather than an ABI change.

You can simply refer to
Documentation/devicetree/bindings/interrupt-controller/interrupts.txt.

Rob

  parent reply	other threads:[~2014-04-10 15:06 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-25 13:41 [PATCH v3 0/3] Support of the kmcoge4 board Valentin Longchamp
2014-03-25 13:41 ` [PATCH v3 1/3] devicetree: bindings: add Zarlink to the vendor prefixes Valentin Longchamp
2014-03-25 13:56   ` Rob Herring
2014-03-25 13:41 ` [PATCH v3 2/3] devcietree: bindings: add some MFD Keymile FPGAs Valentin Longchamp
2014-04-09  0:44   ` Scott Wood
2014-04-09  6:39     ` Valentin Longchamp
2014-04-10 15:06     ` Rob Herring [this message]
2014-03-25 13:41 ` [PATCH v3 3/3] powerpc/mpc85xx: add support for Keymile's kmcoge4 board Valentin Longchamp
2014-04-09  0:47   ` Scott Wood

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=CAL_JsqLLD4fAuhDzdQPWNSbWj444kWESvsprMBFmStUF-QNTiQ@mail.gmail.com \
    --to=robherring2@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=scottwood@freescale.com \
    --cc=valentin.longchamp@keymile.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).