From: grant.likely@secretlab.ca (Grant Likely)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/4] dt: omap3: add generic board file for dt support
Date: Tue, 19 Jul 2011 15:36:49 -0600 [thread overview]
Message-ID: <20110719213649.GP6848@ponder.secretlab.ca> (raw)
In-Reply-To: <CAP6yH7eSmdU16r5iC2MwvU3RwOBXaJNygMUXG=HSMiWUKnor-w@mail.gmail.com>
On Mon, Jul 18, 2011 at 03:45:57PM +0530, G, Manjunath Kondaiah wrote:
> Hi Grant,
>
> On 17 July 2011 10:43, Grant Likely <grant.likely@secretlab.ca> wrote:
> > Hi Manjunath,
> >
> > Comments below. ?I left in a lot of context for the new folks that
> > I've cc'd (Tony and Kevin).
> >
> > On Sat, Jul 16, 2011 at 2:07 PM, G, Manjunath Kondaiah <manjugk@ti.com> wrote:
> >> On Thu, Jul 14, 2011 at 4:45 AM, Grant Likely <grant.likely@secretlab.ca> wrote:
> >>>> > +static void __init omap3_init(void)
> >>>> > +{
> >>>> > + ? ? ? struct device_node *node;
> >>>> > +
> [...]
> >> +static struct omap_device *of_omap_i2c_device_create(struct device_node *node,
> >> + ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?const char *bus_id,
> >> + ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?void *platform_data,
> >> + ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?struct device *parent)
> >> +{
> >> + ? ? ? struct platform_device *pdev;
> >> + ? ? ? struct i2c_board_info *i2c_board_info;
> >> + ? ? ? u8 id;
> >> +
> >> + ? ? ? printk("Creating omap i2c device %s\n", node->full_name);
> >> +
> >> + ? ? ? if (!of_device_is_available(node))
> >> + ? ? ? ? ? ? ? return NULL;
> >> +
> >> + ? ? ? id = simple_strtol(bus_id, NULL, 0);
> >> + ? ? ? pdev = kzalloc(sizeof(*pdev), GFP_KERNEL);
> >> + ? ? ? pdev->dev.of_node = of_node_get(node);
> >> + ? ? ? if (!pdev->dev.of_node) {
> >> + ? ? ? ? ? ? ? speed = 100;
> >> + ? ? ? } else {
> >> + ? ? ? ? ? ? ? u32 prop;
> >> + ? ? ? ? ? ? ? if (!of_property_read_u32(pdev->dev.of_node, "clock-frequency",
> >> + ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? &prop))
> >> + ? ? ? ? ? ? ? ? ? ? ? speed = prop/100;
> >> + ? ? ? ? ? ? ? else
> >> + ? ? ? ? ? ? ? ? ? ? ? speed = 100;
> >> + ? ? ? }
> >> + ? ? ? printk("%s : speed->%d\n",__func__, speed);
> >> +
> >> + ? ? ? for_each_child_of_node(bus, child) {
> >> + ? ? ? ? ? ? ? u32 prop;
> >> +
> >> + ? ? ? ? ? ? ? printk(" ? create child: %s\n", child->full_name);
> >> + ? ? ? ? ? ? ? i2c_board_info = kzalloc(sizeof(*i2c_board_info), GFP_KERNEL);
> >> + ? ? ? ? ? ? ? if (!of_property_read_u32(pdev->dev.of_node, "reg",
> >> + ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? &prop))
> >> + ? ? ? ? ? ? ? i2c_board_info->addr = prop;
> >> + ? ? ? ? ? ? ? if (!of_property_read_u32(pdev->dev.of_node, "interrupts",
> >> + ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? &prop))
> >> + ? ? ? ? ? ? ? i2c_board_info->irq = prop;
> >> + ? ? ? ? ? ? ? i2c_board_info->platform_data = platform_data;
> >> + ? ? ? ? ? ? ? strncpy(i2c_board_info->type, child->name,
> >> + ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? sizeof(i2c_board_info->type));
> >> + ? ? ? }
> >> + ? ? ? omap_register_i2c_bus(id, speed, i2c_board_info, 1);
> >
> > While this does in a sense work, and creates an omap_device for the
> > i2c bus that does get probed, it ends up encoding an awful lot of
> > device specific details into the generic devicetree support code. ?The
> > i2c bus driver itself must be responsible for decoding the speed and
> > child nodes, and in fact it can easily be modified to do so (I've
>
> Decoding speed in i2c driver seems to be fine. But the i2c child nodes are
> board specific. We might bring board specific handling code into i2c driver
> with this approach.
It shouldn't. They're just i2c devices, and the child nodes will
always follow the i2c device binding.
> BTW, I have observed that, if we create i2c device node in omapx-soc.dtsi
> file and the define i2c bus clock-frequency in beagle.dts, the clock-frequency
> is not available in driver probe. Is this expected behavior?
No, it sounds like something isn't getting set up correctly. Send me
your current beagle.dts and omap3-soc.dtsi files.
g.
next prev parent reply other threads:[~2011-07-19 21:36 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1310592975-25773-1-git-send-email-manjugk@ti.com>
[not found] ` <1310592975-25773-2-git-send-email-manjugk@ti.com>
2011-07-13 22:57 ` [PATCH 1/4] dt: omap3: add SoC file for handling i2c controllers Grant Likely
2011-07-13 22:58 ` Grant Likely
2011-07-14 3:51 ` G, Manjunath Kondaiah
2011-07-14 3:34 ` G, Manjunath Kondaiah
[not found] ` <1310592975-25773-3-git-send-email-manjugk@ti.com>
2011-07-13 23:04 ` [PATCH 2/4] dt: OMAP3: Beagle board: set clock freq for i2c devices Grant Likely
[not found] ` <1310592975-25773-4-git-send-email-manjugk@ti.com>
2011-07-13 23:15 ` [PATCH 3/4] dt: omap3: add generic board file for dt support Grant Likely
2011-07-14 8:53 ` [PATCH] omap2+: Use Kconfig symbol in Makefile instead of obj-y Tony Lindgren
[not found] ` <CAC63_iSqN=rX6MbzFWM6z+zf1Eybg3MOD=qQVdeNg5cyENhPjw@mail.gmail.com>
2011-07-16 20:07 ` [PATCH 3/4] dt: omap3: add generic board file for dt support G, Manjunath Kondaiah
2011-07-17 5:13 ` Grant Likely
2011-07-18 9:07 ` Tony Lindgren
2011-07-19 21:34 ` Grant Likely
2011-07-21 7:18 ` Tony Lindgren
2011-07-21 8:55 ` Rajendra Nayak
2011-07-21 9:09 ` Felipe Balbi
2011-07-21 9:33 ` Rajendra Nayak
2011-07-21 9:39 ` Felipe Balbi
2011-07-28 18:20 ` Cousson, Benoit
2011-07-18 10:15 ` G, Manjunath Kondaiah
2011-07-19 21:36 ` Grant Likely [this message]
2011-07-19 5:58 ` G, Manjunath Kondaiah
2011-07-19 21:37 ` Grant Likely
2011-07-21 10:24 ` G, Manjunath Kondaiah
2011-07-21 23:53 ` Kevin Hilman
[not found] ` <1310592975-25773-5-git-send-email-manjugk@ti.com>
2011-07-13 23:20 ` [PATCH 4/4] dt: i2c-omap: Convert i2c driver to use device tree Grant Likely
2011-07-28 17:34 ` Cousson, Benoit
2011-07-28 21:32 ` Grant Likely
2011-08-03 12:56 ` Cousson, Benoit
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=20110719213649.GP6848@ponder.secretlab.ca \
--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).