From: Johns Daniel <johns.daniel-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: devicetree-discuss-mnsaURCQ41sdnm+yROfE0A@public.gmane.org
Subject: I2C not working upon 2.6.24 to 2.6.28 kernel upgrade
Date: Thu, 12 Mar 2009 12:37:38 -0500 [thread overview]
Message-ID: <ba5d9360903121037m6d5be5e9m4b164d56bd6b5f3@mail.gmail.com> (raw)
We have had this device tree (a section shown below) working for a long time:
soc8343@e0000000 {
#address-cells = <1>;
#size-cells = <1>;
#interrupt-cells = <2>;
device_type = "soc";
ranges = <00000000 e0000000 00100000>;
reg = <e0000000 00000200>;
bus-frequency = <0>;
i2c@3000 {
device_type = "i2c";
compatible = "fsl-i2c";
reg = <3000 100>;
interrupts = <e 8>;
interrupt-parent = <700>;
dfsrr;
};
...
}
With linux-2.6.24, it worked with this struct defined in the
board-specific file:
static struct of_device_id __initdata of_bus_ids[] = {
{ .compatible = "fsl,pq2pro-localbus", },
{},
};
With linux-2.6.28, it needs the following struct in the board-specific
file for I2C to work:
static struct of_device_id __initdata of_bus_ids[] = {
{ .type = "soc", },
{ .name = "localbus", },
{},
};
Is this easily explained?
What is the right way to do this now? Ideally, I would like to keep
the device tree unchanged since I need for it to work with older
versions of the kernel!
-- Johns
next reply other threads:[~2009-03-12 17:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-12 17:37 Johns Daniel [this message]
[not found] ` <ba5d9360903121037m6d5be5e9m4b164d56bd6b5f3-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-03-12 18:08 ` I2C not working upon 2.6.24 to 2.6.28 kernel upgrade Grant Likely
[not found] ` <fa686aa40903121108p50338218w18714686d1f8bdbf-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-03-12 21:38 ` Johns Daniel
[not found] ` <ba5d9360903121438p57e068b6n46e58868b814539c-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-03-12 22:18 ` Mitch Bradley
2009-03-17 18:36 ` Scott Wood
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=ba5d9360903121037m6d5be5e9m4b164d56bd6b5f3@mail.gmail.com \
--to=johns.daniel-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=devicetree-discuss-mnsaURCQ41sdnm+yROfE0A@public.gmane.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