From: Bo Shen <voice.shen@atmel.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.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: Wed, 21 Nov 2012 09:43:33 +0800 [thread overview]
Message-ID: <50AC31C5.2000504@atmel.com> (raw)
In-Reply-To: <20121120102712.GF10560@opensource.wolfsonmicro.com>
Hi Mark,
On 11/20/2012 18:27, Mark Brown wrote:
> 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.
So, should I keep these two patches [1] and [2] and then send to pinctrl
again, or I need keep it in one patch as [3] which i sent first.
1. [Resend,v6,1/2] ARM: at91: atmel-ssc: add pinctrl nodes
https://patchwork.kernel.org/patch/1753101/
2. [Resend,v6,2/2] ASoC: atmel-ssc: add pinctrl consumer
https://patchwork.kernel.org/patch/1753091/
3. [v6,1/4] ARM: at91: atmel-ssc: add pinctrl support
https://patchwork.kernel.org/patch/1740391/
Best regards,
Bo Shen
next prev parent reply other threads:[~2012-11-21 1:43 UTC|newest]
Thread overview: 10+ 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 ` [Resend v6 PATCH 2/2] ASoC: atmel-ssc: add pinctrl consumer Bo Shen
2012-11-16 6:12 ` Mark Brown
2012-11-16 6:33 ` Bo Shen
2012-11-16 6:41 ` Mark Brown
2012-11-16 6:59 ` Bo Shen
2012-11-20 9:31 ` Bo Shen
2012-11-20 10:27 ` Mark Brown
2012-11-21 1:43 ` Bo Shen [this message]
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=50AC31C5.2000504@atmel.com \
--to=voice.shen@atmel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--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 \
/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).