From: grant.likely@secretlab.ca (Grant Likely)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: CSR: Adding CSR SiRFprimaII board support
Date: Wed, 22 Jun 2011 10:38:42 -0600 [thread overview]
Message-ID: <BANLkTikP8WSSQbqre0UdKqWZjgp+TBOe9A@mail.gmail.com> (raw)
In-Reply-To: <BANLkTi=fdg=f_mM87YOJGn--TUDVcGz7fA@mail.gmail.com>
On Wed, Jun 22, 2011 at 1:36 AM, Barry Song <21cnbao@gmail.com> wrote:
> so the problem still need to be solved since device names coming from DT is not
> that much "stable" as statically registered devices. the name from DT
> isn't the same
> as what board support code currently uses for statically registered
> platform_devices.
>
> Grant has two threads for this:
> 1. of: add clock providers to provide clk mapping in DT
> http://www.mail-archive.com/devicetree-discuss at lists.ozlabs.org/msg03016.html
> 2. " If Linux needs specific devices to have specific names, then it
> can pass in a lookup table that matches DT nodes to device names,
> which is considerably simpler and it leaves the platform setup code in
> control over how devices get instantiated."
>
> both seems not ready yet?
I'm planning to merge the auxdata patch (thread 2 above) into
linux-next in a couple of days. When I push out that branch, it can
be merged into the subarch tree before picking up the sirfprimall
support patch (assuming it gets picked up for v3.1)
g.
next prev parent reply other threads:[~2011-06-22 16:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-20 7:53 [PATCH] ARM: CSR: Adding CSR SiRFprimaII board support Barry Song
2011-06-21 15:53 ` Arnd Bergmann
2011-06-22 9:09 ` Barry Song
2011-06-22 12:34 ` Arnd Bergmann
2011-06-23 7:42 ` Barry Song
2011-06-23 10:21 ` Arnd Bergmann
2011-06-21 16:22 ` Russell King - ARM Linux
2011-06-22 7:36 ` Barry Song
2011-06-22 16:38 ` Grant Likely [this message]
2011-06-24 2:28 ` Barry Song
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=BANLkTikP8WSSQbqre0UdKqWZjgp+TBOe9A@mail.gmail.com \
--to=grant.likely@secretlab.ca \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).