From: broonie@opensource.wolfsonmicro.com (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 18/19] Documentation: Define the MSP Driver Device Tree bindings
Date: Tue, 31 Jul 2012 16:10:24 +0100 [thread overview]
Message-ID: <20120731151024.GA4468@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <5017F2E2.4040100@linaro.org>
On Tue, Jul 31, 2012 at 03:59:46PM +0100, Lee Jones wrote:
> On 31/07/12 14:55, Mark Brown wrote:
> >>+Optional properties:
> >>+ - interrupts : The interrupt outputs from the device.
> >If there's more than one interrupt then how are they ordered?
> It doesn't matter. If there are any more than one (which there
> aren't in this case), we usually use the interrupt-names property
> then request them by name in the driver.
So the binding therefore needs to say "The interrupt output from the
device" as there's only one output supported. If we were using
interrupt-names then we'd need to document what the supported names are.
next prev parent reply other threads:[~2012-07-31 15:10 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-31 13:38 [PATCH 01/19] Configure ux500 Audio Drivers for Device Tree Lee Jones
2012-07-31 13:38 ` [PATCH 01/19] ASoC: Ux500: Move MSP pinctrl setup into the MSP driver Lee Jones
2012-07-31 13:38 ` [PATCH 02/19] ASoC: Ux500: Enable MOP500 driver for Device Tree Lee Jones
2012-07-31 13:38 ` [PATCH 03/19] ASoC: Ux500: Enable ux500 MSP " Lee Jones
2012-07-31 13:38 ` [PATCH 04/19] ASoC: Ux500: Initialise PCM from MSP probe rather than as a device Lee Jones
2012-07-31 13:38 ` [PATCH 05/19] ASoC: codecs: Enable AB8500 CODEC for Device Tree Lee Jones
2012-07-31 13:39 ` [PATCH 06/19] ARM: ux500: Clean-up MSP platform code Lee Jones
2012-07-31 13:39 ` [PATCH 07/19] ARM: ux500: Add AB8500 CODEC node to DB8500 Device Tree Lee Jones
2012-07-31 13:39 ` [PATCH 08/19] ARM: ux500: Fork MSP platform registration for step-by-step DT enablement Lee Jones
2012-07-31 13:39 ` [PATCH 09/19] ARM: ux500: Pass MSP DMA platform data though AUXDATA Lee Jones
2012-07-31 13:39 ` [PATCH 10/19] ARM: ux500: Stop registering the MOP500 Audio driver from platform code Lee Jones
2012-07-31 13:39 ` [PATCH 11/19] ARM: ux500: Stop registering the PCM " Lee Jones
2012-07-31 13:39 ` [PATCH 12/19] ARM: ux500: Remove platform registration of MSP devices Lee Jones
2012-07-31 13:39 ` [PATCH 13/19] ARM: ux500: Rename MSP board file to something more meaningful Lee Jones
2012-07-31 13:39 ` [PATCH 14/19] ARM: ux500: Rename db8500.dtsi to dbx5x0.dtsi to encompass the u9500, u8540 and u9540 Lee Jones
2012-07-31 13:39 ` [PATCH 15/19] ARM: ux500: Add nodes for the MSP into Device Tree Lee Jones
2012-07-31 13:39 ` [PATCH 16/19] ARM: ux500: Add all encompassing sound node to the Snowball " Lee Jones
2012-07-31 13:39 ` [PATCH 17/19] Documentation: Define the MOP500 Audio Machine Driver Device Tree bindings Lee Jones
2012-07-31 13:53 ` Mark Brown
2012-07-31 15:00 ` Lee Jones
2012-08-02 12:12 ` Lee Jones
2012-07-31 13:39 ` [PATCH 18/19] Documentation: Define the MSP " Lee Jones
2012-07-31 13:55 ` Mark Brown
2012-07-31 14:59 ` Lee Jones
2012-07-31 15:10 ` Mark Brown [this message]
2012-08-02 12:45 ` Lee Jones
2012-07-31 13:39 ` [PATCH 19/19] Documentation: Add the AB8500 CODEC device to the MFD AB8500 doc Lee Jones
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=20120731151024.GA4468@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=linux-arm-kernel@lists.infradead.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).