From: Petr Kulhavy <petr@barix.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Mark Rutland <mark.rutland@arm.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
ALSA Development Mailing List <alsa-devel@alsa-project.org>,
Pawel Moll <pawel.moll@arm.com>,
Kevin Hilman <khilman@kernel.org>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Sekhar Nori <nsekhar@ti.com>, Liam Girdwood <lgirdwood@gmail.com>,
Rob Herring <robh+dt@kernel.org>, Mark Brown <broonie@kernel.org>,
Kumar Gala <galak@codeaurora.org>
Subject: Re: [PATCH v3 1/7] ASoC: davinci-mcbsp: add binding for McBSP
Date: Fri, 22 Apr 2016 10:33:31 +0200 [thread overview]
Message-ID: <5719E1DB.5040703@barix.com> (raw)
In-Reply-To: <CAMuHMdVCW0zAxAZRTazVhXz72fkp_escQM2JTSX2J4Ertru==Q@mail.gmail.com>
On 20.04.2016 08:49, Geert Uytterhoeven wrote:
> On Mon, Apr 18, 2016 at 2:32 PM, Petr Kulhavy <petr@barix.com> wrote:
>> --- /dev/null
>> +++ b/Documentation/devicetree/bindings/sound/davinci-mcbsp.txt
>> @@ -0,0 +1,51 @@
>> +Optional properties:
>> +~~~~~~~~~~~~~~~~~~~~
>> +- interrupts : Interrupt numbers for McBSP
>> +- interrupt-names : Known interrupt names are "rx" and "tx"
>> +
>> +- pinctrl-0: Should specify pin control group used for this controller.
>> +- pinctrl-names: Should contain only one value - "default", for more details
>> + please refer to pinctrl-bindings.txt
>> +
>> +Example (AM1808):
>> +~~~~~~~~~~~~~~~~~
>> +
>> +mcbsp0: mcbsp@1d10000 {
>> + compatible = "ti,da850-mcbsp";
>> + pinctrl-names = "default";
>> + pinctrl-0 = <&mcbsp0_pins>;
>> +
>> + reg = <0x00110000 0x1000>,
>> + <0x00310000 0x1000>;
>> + reg-names = "mpu", "dat";
>> + interrupts = <97 98>;
>> + interrupts-names = "rx", "tx";
> interrupt-names
Good catch, thanks!
Petr
next prev parent reply other threads:[~2016-04-22 8:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-18 12:32 [PATCH v3 0/7] ASoC: davinci-mcbsp: add binding for McBSP Petr Kulhavy
[not found] ` <1460982766-18632-1-git-send-email-petr-Qh/3xLP0EvwAvxtiuMwx3w@public.gmane.org>
2016-04-18 12:32 ` [PATCH v3 1/7] " Petr Kulhavy
[not found] ` <1460982766-18632-2-git-send-email-petr-Qh/3xLP0EvwAvxtiuMwx3w@public.gmane.org>
2016-04-20 6:49 ` Geert Uytterhoeven
2016-04-22 8:33 ` Petr Kulhavy [this message]
2016-04-18 12:32 ` [PATCH v3 2/7] ASoC: Davinci: McBSP: add device tree support " Petr Kulhavy
2016-04-18 12:32 ` [PATCH v3 3/7] ARM: davinci: da850: add clocks for mcbsp0 and 1 Petr Kulhavy
2016-04-18 12:32 ` [PATCH v3 4/7] ARM: davinci: da8xx-dt: add OF_DEV_AUXDATA entries for mcbsp0 and mcbsp1 Petr Kulhavy
2016-04-18 12:32 ` [PATCH v3 5/7] ARM: DTS: da850: Fix wrong number of interrupts Petr Kulhavy
2016-04-18 12:32 ` [PATCH v3 6/7] ARM: DTS: da850: Add McBSP0 and McBSP1 Petr Kulhavy
2016-04-18 12:32 ` [PATCH v3 7/7] ARM: davinci: remove unused davinci-i2s pdata Petr Kulhavy
2016-04-18 13:06 ` [PATCH v3 0/7] ASoC: davinci-mcbsp: add binding for McBSP Peter Ujfalusi
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=5719E1DB.5040703@barix.com \
--to=petr@barix.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=geert@linux-m68k.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=khilman@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=mark.rutland@arm.com \
--cc=nsekhar@ti.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.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).