linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: grant.likely@secretlab.ca (Grant Likely)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/3] serial/imx: add device tree support
Date: Tue, 21 Jun 2011 13:02:48 -0600	[thread overview]
Message-ID: <BANLkTikHTSgowpUhMCcOMXk_oQd4Ue7S3Q@mail.gmail.com> (raw)
In-Reply-To: <20110621185356.GJ23234@n2100.arm.linux.org.uk>

On Tue, Jun 21, 2011 at 12:53 PM, Russell King - ARM Linux
<linux@arm.linux.org.uk> wrote:
> On Tue, Jun 21, 2011 at 12:42:14PM -0600, Grant Likely wrote:
>> On Tue, Jun 21, 2011 at 12:32 PM, Mitch Bradley <wmb@firmworks.com> wrote:
>> > I wonder if it makes sense to create a new device node "/linux-devices" to express a desired mapping from device nodes to /dev entries? ?The properties could be the names of device special files and the values the corresponding node phandles.
>>
>> I've been trying /really/ hard to avoid doing something like that
>> because a lot of the time the desired Linux dev name is a
>> implementation detail, and a potentially unstable one at that. ?If
>> Linux requires certain devices to have certain names because that is
>> how it hooks up clocks
>
> As I keep on saying, we don't _have_ to have to match on device name.
> If DT can come up with a better way to bind a clock to a particular
> device/connection name then DT can provide its own clk_get()
> implementation which does that.

Sorry, I overstated the situation.  My point is only that I don't want
encode how Linux currently views the world into the DT, because
implementation details can and do change.

g.

  reply	other threads:[~2011-06-21 19:02 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-18 15:19 [PATCH 0/3] Add basic device support for imx51 babbage Shawn Guo
2011-06-18 15:19 ` [PATCH 1/3] serial/imx: add device tree support Shawn Guo
2011-06-18 16:19   ` Grant Likely
2011-06-19  7:02     ` Wolfram Sang
2011-06-19  7:30     ` Shawn Guo
2011-06-19 15:05       ` Grant Likely
2011-06-19 15:15         ` Rob Herring
2011-06-19 18:44           ` Grant Likely
2011-06-21 13:55       ` Shawn Guo
2011-06-21 18:32         ` Mitch Bradley
2011-06-21 18:42           ` Grant Likely
2011-06-21 18:53             ` Russell King - ARM Linux
2011-06-21 19:02               ` Grant Likely [this message]
2011-06-21 19:04             ` Mitch Bradley
2011-06-21 19:13         ` Grant Likely
2011-06-21 19:35           ` Mitch Bradley
2011-06-21 19:38             ` Grant Likely
2011-06-21 22:08               ` Mitch Bradley
2011-06-21 22:33                 ` Grant Likely
2011-06-21 22:52                   ` Segher Boessenkool
2011-06-21 22:58                     ` Grant Likely
2011-06-22 15:33           ` Shawn Guo
2011-06-22 15:52             ` Grant Likely
2011-06-23  0:12               ` Shawn Guo
2011-06-23  3:35                 ` Grant Likely
2011-06-23 18:38           ` Shawn Guo
2011-06-23 23:11             ` Grant Likely
2011-06-24  3:49               ` Shawn Guo
2011-06-24  4:05                 ` Grant Likely
2011-06-18 16:21   ` Arnd Bergmann
2011-06-18 16:26     ` Grant Likely
2011-06-18 18:11       ` Arnd Bergmann
2011-06-19  7:41       ` Shawn Guo
2011-06-19  7:40     ` Shawn Guo
2011-06-18 15:19 ` [PATCH 2/3] net/fec: " Shawn Guo
2011-06-18 16:22   ` Grant Likely
2011-06-19  7:46     ` Shawn Guo
2011-06-18 18:27   ` Arnd Bergmann
2011-06-19  0:24     ` Grant Likely
2011-06-19  7:55     ` Shawn Guo
2011-06-19 11:39   ` Greg Ungerer
2011-06-19 12:11     ` Arnd Bergmann
2011-06-19 15:09       ` Rob Herring
2011-06-19 18:43         ` Grant Likely
2011-06-20  0:05       ` Greg Ungerer
2011-06-18 15:19 ` [PATCH 3/3] ARM: mx5: add basic device tree support for imx51 babbage Shawn Guo
2011-06-18 16:24   ` Grant Likely
2011-06-18 16:29 ` [PATCH 0/3] Add basic device " Grant Likely

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=BANLkTikHTSgowpUhMCcOMXk_oQd4Ue7S3Q@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).