From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Bo Shen <voice.shen@atmel.com>
Cc: plagnioj@jcrosoft.com, nicolas.ferre@atmel.com,
linux-arm-kernel@lists.infradead.org,
devicetree-discuss@lists.ozlabs.org, linux-sound@vger.kernel.org,
alsa-devel@alsa-project.org
Subject: Re: [Resend v6 PATCH 2/2] ASoC: atmel-ssc: add pinctrl consumer
Date: Tue, 20 Nov 2012 19:27:38 +0900 [thread overview]
Message-ID: <20121120102712.GF10560@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <50AB4DEA.3090100@atmel.com>
[-- Attachment #1: Type: text/plain, Size: 546 bytes --]
On Tue, Nov 20, 2012 at 05:31:22PM +0800, Bo Shen wrote:
> >based on ASoC tree? And the upper go into pinctrl tree?
> >---<8---
> >ssc0: ssc@fffbc000 {
> > compatible = "atmel,at91rm9200-ssc";
> > reg = <0xfffbc000 0x4000>;
> > interrupts = <14 4 5>;
> >+ pinctrl-names = "default";
> >+ pinctrl-0 = <&pinctrl_ssc0_tx &pinctrl_ssc0_rx>;
> > status = "disable";
> >};
> >--->8---
> Any suggestion for this? what should I do with this patch for next?
Send it to pinctrl and we'll deal with the add/add.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: broonie@opensource.wolfsonmicro.com (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [Resend v6 PATCH 2/2] ASoC: atmel-ssc: add pinctrl consumer
Date: Tue, 20 Nov 2012 19:27:38 +0900 [thread overview]
Message-ID: <20121120102712.GF10560@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <50AB4DEA.3090100@atmel.com>
On Tue, Nov 20, 2012 at 05:31:22PM +0800, Bo Shen wrote:
> >based on ASoC tree? And the upper go into pinctrl tree?
> >---<8---
> >ssc0: ssc at fffbc000 {
> > compatible = "atmel,at91rm9200-ssc";
> > reg = <0xfffbc000 0x4000>;
> > interrupts = <14 4 5>;
> >+ pinctrl-names = "default";
> >+ pinctrl-0 = <&pinctrl_ssc0_tx &pinctrl_ssc0_rx>;
> > status = "disable";
> >};
> >--->8---
> Any suggestion for this? what should I do with this patch for next?
Send it to pinctrl and we'll deal with the add/add.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20121120/243220af/attachment-0001.sig>
WARNING: multiple messages have this Message-ID (diff)
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Bo Shen <voice.shen@atmel.com>
Cc: plagnioj@jcrosoft.com, nicolas.ferre@atmel.com,
linux-arm-kernel@lists.infradead.org,
devicetree-discuss@lists.ozlabs.org, linux-sound@vger.kernel.org,
alsa-devel@alsa-project.org
Subject: Re: [Resend v6 PATCH 2/2] ASoC: atmel-ssc: add pinctrl consumer
Date: Tue, 20 Nov 2012 10:27:38 +0000 [thread overview]
Message-ID: <20121120102712.GF10560@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <50AB4DEA.3090100@atmel.com>
[-- Attachment #1: Type: text/plain, Size: 546 bytes --]
On Tue, Nov 20, 2012 at 05:31:22PM +0800, Bo Shen wrote:
> >based on ASoC tree? And the upper go into pinctrl tree?
> >---<8---
> >ssc0: ssc@fffbc000 {
> > compatible = "atmel,at91rm9200-ssc";
> > reg = <0xfffbc000 0x4000>;
> > interrupts = <14 4 5>;
> >+ pinctrl-names = "default";
> >+ pinctrl-0 = <&pinctrl_ssc0_tx &pinctrl_ssc0_rx>;
> > status = "disable";
> >};
> >--->8---
> Any suggestion for this? what should I do with this patch for next?
Send it to pinctrl and we'll deal with the add/add.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-11-20 10:27 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-16 6:03 [Resend v6 PATCH 1/2] ARM: at91: atmel-ssc: add pinctrl nodes Bo Shen
2012-11-16 6:03 ` Bo Shen
2012-11-16 6:03 ` Bo Shen
2012-11-16 6:03 ` [Resend v6 PATCH 2/2] ASoC: atmel-ssc: add pinctrl consumer Bo Shen
2012-11-16 6:03 ` Bo Shen
2012-11-16 6:03 ` Bo Shen
2012-11-16 6:12 ` Mark Brown
2012-11-16 6:12 ` Mark Brown
2012-11-16 6:12 ` Mark Brown
2012-11-16 6:33 ` Bo Shen
2012-11-16 6:33 ` Bo Shen
2012-11-16 6:33 ` Bo Shen
2012-11-16 6:41 ` Mark Brown
2012-11-16 6:41 ` Mark Brown
2012-11-16 6:41 ` Mark Brown
2012-11-16 6:59 ` Bo Shen
2012-11-16 6:59 ` Bo Shen
2012-11-16 6:59 ` Bo Shen
2012-11-20 9:31 ` Bo Shen
2012-11-20 9:31 ` Bo Shen
2012-11-20 9:31 ` Bo Shen
2012-11-20 10:27 ` Mark Brown [this message]
2012-11-20 10:27 ` Mark Brown
2012-11-20 10:27 ` Mark Brown
2012-11-21 1:43 ` Bo Shen
2012-11-21 1:43 ` Bo Shen
2012-11-21 1:43 ` Bo Shen
2012-11-21 1:46 ` Mark Brown
2012-11-21 1:46 ` Mark Brown
2012-11-21 1:46 ` Mark Brown
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=20121120102712.GF10560@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-sound@vger.kernel.org \
--cc=nicolas.ferre@atmel.com \
--cc=plagnioj@jcrosoft.com \
--cc=voice.shen@atmel.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.