From: Lee Jones <lee.jones@linaro.org>
To: Stephen Warren <swarren@wwwdotorg.org>
Cc: Linus Walleij <linus.walleij@linaro.org>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linus.walleij@stericsson.com,
arnd@arndb.de,
Gabriel FERNANDEZ <gabriel.fernandez@stericsson.com>,
Loic Pallardy <loic.pallardy@stericsson.com>,
Patrice CHOTARD <patrice.chotard@stericsson.com>
Subject: Re: [PATCH] ARM: ux500: Register pinctrl from platform code until it's been DT:ed
Date: Thu, 05 Jul 2012 16:58:09 +0100 [thread overview]
Message-ID: <4FF5B991.9070807@linaro.org> (raw)
In-Reply-To: <4FF5B8B9.8030200@wwwdotorg.org>
On 05/07/12 16:54, Stephen Warren wrote:
> On 07/05/2012 03:36 AM, Lee Jones wrote:
>> On 05/07/12 09:55, Linus Walleij wrote:
> ...
>>> There are plenty of
>>> examples of how to do this in for example:
>>> arch/arm/boot/dts/tegra-seaboard.dts
>>
>> I don't see this file anywhere?
>
> It was recently renamed to tegra20-seaboard.dts.
>
> While Tegra doesn't need any AUXDATA for the pinctrl driver specifically
> (since we're purely initializing pinctrl from DT now when booting with
> DT), we do need AUXDATA for other devices mainly for clocks. You can
> find the AUXDATA setup in:
>
> arch/arch/mach-tegra/board-dt-tegra*.c
That's okay.
We use it quite a lot in arch/arch/mach-ux500/board-mop500.c already
(also for things like clocks, dma and call-backs).
--
Lee Jones
Linaro ST-Ericsson Landing Team Lead
M: +44 77 88 633 515
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
prev parent reply other threads:[~2012-07-05 15:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-04 14:34 [PATCH] ARM: ux500: Register pinctrl from platform code until it's been DT:ed Lee Jones
2012-07-05 8:55 ` Linus Walleij
2012-07-05 9:36 ` Lee Jones
2012-07-05 10:10 ` Linus Walleij
2012-07-05 15:54 ` Stephen Warren
2012-07-05 15:58 ` Lee Jones [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=4FF5B991.9070807@linaro.org \
--to=lee.jones@linaro.org \
--cc=arnd@arndb.de \
--cc=gabriel.fernandez@stericsson.com \
--cc=linus.walleij@linaro.org \
--cc=linus.walleij@stericsson.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=loic.pallardy@stericsson.com \
--cc=patrice.chotard@stericsson.com \
--cc=swarren@wwwdotorg.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