devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Linus Walleij <linus.walleij@linaro.org>
To: Rob Herring <robherring2@gmail.com>
Cc: linux@arm.linux.org.uk, arnd@arndb.de,
	devicetree-discuss@lists.ozlabs.org,
	Rob Herring <rob.herring@calxeda.com>,
	Grant Likely <grant.likely@secretlab.ca>,
	Jeremy Kerr <jeremy.kerr@canonical.com>,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [RFC PATCH v3 1/2] drivers/amba: create devices from device tree
Date: Thu, 26 May 2011 09:41:06 +0200	[thread overview]
Message-ID: <BANLkTimq=6UGTHVL=r2GQZJaKMBH7X6wqw@mail.gmail.com> (raw)
In-Reply-To: <1306359073-16274-2-git-send-email-robherring2@gmail.com>

2011/5/25 Rob Herring <robherring2@gmail.com>:

Trivia:

> +       /* Allow the arm,amba-deviceid value to override the h/w value */
> +       prop = of_get_property(node, "arm,amba-deviceid", NULL);
> +       if (prop)
> +               dev->periphid = of_read_ulong(prop, 1);

That currently does not override the H/W value at all. But when/if patch
http://www.arm.linux.org.uk/developer/patches/viewpatch.php?id=6829/1
gets merged, it eventually will.

Acked-by: Linus Walleij <linus.walleij@linaro.org>

Yours,
Linus Walleij

  reply	other threads:[~2011-05-26  7:41 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-25 21:31 [RFC PATCH v3 0/2] amba bus device tree probing Rob Herring
     [not found] ` <1306359073-16274-1-git-send-email-robherring2-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2011-05-25 21:31   ` [RFC PATCH v3 1/2] drivers/amba: create devices from device tree Rob Herring
2011-05-26  7:41     ` Linus Walleij [this message]
2011-05-25 21:31   ` [RFC PATCH v3 2/2] dt: add custom device creation to platform bus scan Rob Herring
     [not found]     ` <1306359073-16274-3-git-send-email-robherring2-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2011-05-26 13:11       ` Arnd Bergmann
     [not found]         ` <201105261511.23659.arnd-r2nGTMty4D4@public.gmane.org>
2011-05-26 18:43           ` Rob Herring
     [not found]             ` <4DDE9F4A.5050507-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2011-05-27 12:06               ` Arnd Bergmann
     [not found]                 ` <201105271406.18841.arnd-r2nGTMty4D4@public.gmane.org>
2011-06-01 16:52                   ` Rob Herring
     [not found]                     ` <4DE66E39.2070300-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2011-06-01 16:58                       ` Grant Likely
     [not found]                         ` <BANLkTimTdVKspjJ8GD4M90wiKCC0SzkgpA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-06-01 21:29                           ` Arnd Bergmann
     [not found]                             ` <201106012329.20651.arnd-r2nGTMty4D4@public.gmane.org>
2011-06-08  3:12                               ` Rob Herring
     [not found]                                 ` <4DEEE8AF.50603-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2011-06-08  6:16                                   ` Arnd Bergmann

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='BANLkTimq=6UGTHVL=r2GQZJaKMBH7X6wqw@mail.gmail.com' \
    --to=linus.walleij@linaro.org \
    --cc=arnd@arndb.de \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=grant.likely@secretlab.ca \
    --cc=jeremy.kerr@canonical.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux@arm.linux.org.uk \
    --cc=rob.herring@calxeda.com \
    --cc=robherring2@gmail.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;
as well as URLs for NNTP newsgroup(s).