From: Bo Shen <bard.shen@gmail.com>
To: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
Cc: Mark Brown <broonie@opensource.wolfsonmicro.com>,
alsa-devel@alsa-project.org, devicetree-discuss@lists.ozlabs.org,
nicolas.ferre@atmel.com, linux-sound@vger.kernel.org,
Bo Shen <voice.shen@atmel.com>,
fengguang.wu@intel.com, linux-arm-kernel@lists.infradead.org
Subject: Re: [Resend PATCH v3 2/4] ARM: at91: atmel-ssc: add device tree support
Date: Thu, 08 Nov 2012 09:50:41 +0800 [thread overview]
Message-ID: <509B0FF1.4080504@gmail.com> (raw)
In-Reply-To: <20121107151607.GC4576@game.jcrosoft.org>
Hi J,
On 11/7/2012 23:16, Jean-Christophe PLAGNIOL-VILLARD wrote:
> On 15:44 Wed 07 Nov , Mark Brown wrote:
>> On Wed, Nov 07, 2012 at 03:30:46PM +0100, Jean-Christophe PLAGNIOL-VILLARD wrote:
>>
>>> the one via ASoC for the driver with the pinctrl for now but MUST add it later
>>
>>> the arch/arm related via AT91 tree where the pinctrl is mandatory in the dtsi
>>
>>> I'm no going to spend hours to do the pinctrl to test Bo patch that he is
>>> supposed to have deon to test this code
>>
>>> As basically today on DT none of the board will work if BO does no provide the
>>> pinctrl so for me he MUST put in the dtsi
>>
>>> is it ok with you?
>>
>> Or add the pinmux bindings for other IPs over in the pinmux branch and
>> the pinmux binding for SSC here (which will help with bisection as the
>> DT bindings for the audio will then always exist in conjunction with the
>> .dtsi changes for them). Either way is fine with me; I'll leave things
>> as they are until I see some new patches.
> for where it's merge honestly I do not care much but the pinctrl must be
> handled correctly
I will send patches to add pinctrl support.
For atmel ssc driver, it is simple, however for dtsi, which point should
I based on? which git and which branch? Because, I am not sure which
branch on git://github.com/at91linux/linux-at91.git is the right point.
Thanks.
Best Regards,
Bo Shen
> Best Regards,
> J.
>
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
>
prev parent reply other threads:[~2012-11-08 1:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-07 3:41 [Resend PATCH v3 2/4] ARM: at91: atmel-ssc: add device tree support Bo Shen
2012-11-07 8:24 ` Mark Brown
2012-11-07 8:47 ` Jean-Christophe PLAGNIOL-VILLARD
2012-11-07 9:04 ` Mark Brown
2012-11-07 8:49 ` Jean-Christophe PLAGNIOL-VILLARD
2012-11-07 9:21 ` Mark Brown
[not found] ` <20121107092124.GE12323-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@public.gmane.org>
2012-11-07 10:41 ` Jean-Christophe PLAGNIOL-VILLARD
2012-11-07 14:05 ` Mark Brown
2012-11-07 14:30 ` Jean-Christophe PLAGNIOL-VILLARD
[not found] ` <20121107143046.GA4576-RQcB7r2h9QmfDR2tN2SG5Ni2O/JbrIOy@public.gmane.org>
2012-11-07 14:44 ` Mark Brown
2012-11-07 15:14 ` Jean-Christophe PLAGNIOL-VILLARD
[not found] ` <20121107144450.GF20844-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@public.gmane.org>
2012-11-07 15:16 ` Jean-Christophe PLAGNIOL-VILLARD
2012-11-08 1:50 ` Bo Shen [this message]
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=509B0FF1.4080504@gmail.com \
--to=bard.shen@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=fengguang.wu@intel.com \
--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 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).