From: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: Bo Shen <voice.shen@atmel.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, fengguang.wu@intel.com
Subject: Re: [Resend PATCH v3 2/4] ARM: at91: atmel-ssc: add device tree support
Date: Wed, 07 Nov 2012 15:14:41 +0000 [thread overview]
Message-ID: <20121107151441.GB4576@game.jcrosoft.org> (raw)
In-Reply-To: <20121107144450.GF20844@opensource.wolfsonmicro.com>
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.
>
> Though I have to say now that I look in -next it's a bit surprising that
> there are so many IPs in the file that have no pinmix configuration,
> based on what you're saying it seems like the entire board will be
> falling over with the pinmux code anyway - in the case of the sam9g20ek
> we'd at least need I2C pinmux settings. I may be misunderstanding.
yes I've a new patch series that finish to add them as they was in the Dt
before the add of the pinctrl (macb/usb device /host) i2c after as on 9g20ek
we use gpio i2c so no need to do any pinctrl for now
but now new switch to DT must handle the pinctrl
Best Regards,
J.
next prev parent reply other threads:[~2012-11-07 15:14 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 [this message]
[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
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=20121107151441.GB4576@game.jcrosoft.org \
--to=plagnioj@jcrosoft.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=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