All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lee Jones <lee.jones@linaro.org>
To: Per Forlin <per.forlin@stericsson.com>
Cc: grant.likely@secretlab.ca, rob.herring@calxeda.com,
	Linus Walleij <linus.walleij@linaro.org>,
	fredrik.soderstedt@stericsson.com,
	devicetree-discuss@lists.ozlabs.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dt: platform: Extract device name from device tree blob
Date: Wed, 14 Nov 2012 09:21:58 +0000	[thread overview]
Message-ID: <20121114092158.GA12596@gmail.com> (raw)
In-Reply-To: <1352732343-1199-1-git-send-email-per.forlin@stericsson.com>

On Mon, 12 Nov 2012, Per Forlin wrote:

> Add support to extract device name from device tree blob.
> If the property "dev-name" is set in the DTS this name will
> be used when creating the device.
> The auxdata_lookup has precedence and will override
> the "dev-name" property.
> 
> Adding support to parse DTS "dev-name" will make it possible to
> replace these kind of structures with a dev-name in the DTS.
> OF_DEV_AUXDATA("compatible", BASE_ADDRESS, "dev-name", NULL)

This patch isn't required. The correct action is to make the driver
DT aware. Also, is naming devices "devname.id" a Linux only thing,
or do other OSes do the same? If the former is true, then we
definitely do not want to add this binding.

> OF_DEV_AUXDATA("st,nomadik-gpio", 0x8012e000, "gpio.0", NULL),
> OF_DEV_AUXDATA("st,nomadik-i2c", 0x80004000, "nmk-i2c.0", NULL),

In this case, once we have added common clk functionality to our
Device Trees, these will vanish.

Kind regards,
Lee

-- 
Lee Jones
Linaro ST-Ericsson Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog

      parent reply	other threads:[~2012-11-14  9:21 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-12 14:59 [PATCH] dt: platform: Extract device name from device tree blob Per Forlin
2012-11-12 14:59 ` Per Forlin
     [not found] ` <1352732343-1199-1-git-send-email-per.forlin-0IS4wlFg1OjSUeElwK9/Pw@public.gmane.org>
2012-11-12 15:20   ` Grant Likely
2012-11-12 15:20     ` Grant Likely
2012-11-12 22:54     ` Per Förlin
2012-11-13 14:33       ` Per Förlin
     [not found]       ` <50A17E30.7030807-0IS4wlFg1OjSUeElwK9/Pw@public.gmane.org>
2012-11-15 15:52         ` Grant Likely
2012-11-15 16:15           ` Per Förlin
2012-11-16  8:15             ` lee.jones
2012-11-14  9:21 ` 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=20121114092158.GA12596@gmail.com \
    --to=lee.jones@linaro.org \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=fredrik.soderstedt@stericsson.com \
    --cc=grant.likely@secretlab.ca \
    --cc=linus.walleij@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=per.forlin@stericsson.com \
    --cc=rob.herring@calxeda.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.