From: "Grant Likely" <grant.likely@secretlab.ca>
To: "Wolfgang Grandegger" <wg@grandegger.com>
Cc: Linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] powerpc: 85xx: add proper OF bus ids for the TQM85xx
Date: Fri, 25 Jul 2008 09:20:22 -0400 [thread overview]
Message-ID: <fa686aa40807250620r1ab574basd07ecce6be2bc238@mail.gmail.com> (raw)
In-Reply-To: <48898470.80109@grandegger.com>
On Fri, Jul 25, 2008 at 3:44 AM, Wolfgang Grandegger <wg@grandegger.com> wrote:
> Since recent modifications to the MPC I2C code, the MPC I2C buses are not
> found any more. This patch fixes the problem by adding proper OF
> bus ids.
>
> Signed-off-by: Wolfgang Grandegger <wg@grandegger.com>
> ---
> arch/powerpc/platforms/85xx/tqm85xx.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> Index: linux-2.6-galak/arch/powerpc/platforms/85xx/tqm85xx.c
> ===================================================================
> --- linux-2.6-galak.orig/arch/powerpc/platforms/85xx/tqm85xx.c
> +++ linux-2.6-galak/arch/powerpc/platforms/85xx/tqm85xx.c
> @@ -156,15 +156,15 @@ static void tqm85xx_show_cpuinfo(struct }
>
> static struct of_device_id __initdata of_bus_ids[] = {
> + { .type = "soc", },
> + { .compatible = "soc", },
> { .compatible = "simple-bus", },
Ugh, i assume this is to support older .dts files that don't have
simple-bus in their compatible property? Please put them at the end
of the list and put a comment ahead of them stating that they are
legacy support. You should also state in the comment which boards or
dts files these entries provide support for.
g.
--
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
next prev parent reply other threads:[~2008-07-25 13:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-25 7:44 [PATCH] powerpc: 85xx: add proper OF bus ids for the TQM85xx Wolfgang Grandegger
2008-07-25 13:20 ` Grant Likely [this message]
2008-07-25 15:16 ` Wolfgang Grandegger
2008-07-25 15:30 ` Jon Loeliger
2008-07-25 15:37 ` Wolfgang Grandegger
2008-08-17 9:03 ` Wolfgang Grandegger
2008-08-17 15:52 ` Jon Loeliger
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=fa686aa40807250620r1ab574basd07ecce6be2bc238@mail.gmail.com \
--to=grant.likely@secretlab.ca \
--cc=Linuxppc-dev@ozlabs.org \
--cc=wg@grandegger.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).