From: Wolfram Sang <w.sang-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
To: Michael Lawnick <ml.lawnick-Mmb7MZpHnFY@public.gmane.org>
Cc: linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, "Delvare,
Jean " <khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org>
Subject: Re: [PATCH] assign a default class to MPC adapter
Date: Thu, 16 Apr 2009 13:47:01 +0200 [thread overview]
Message-ID: <20090416114701.GD3052@pengutronix.de> (raw)
In-Reply-To: <49E7101E.6070806-Mmb7MZpHnFY@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 750 bytes --]
> Could you please elaborate?
Instead of probing you specify the devices on the i2c-bus in the dts. Example
for the pcm032 looks like this (from the kernel-tree):
i2c@3d40 {
#address-cells = <1>;
#size-cells = <0>;
compatible = "fsl,mpc5200b-i2c","fsl,mpc5200-i2c","fsl-i2c";
reg = <0x3d40 0x40>;
interrupts = <2 16 0>;
fsl5200-clocking;
rtc@51 {
compatible = "nxp,pcf8563";
reg = <0x51>;
};
eeprom@52 {
compatible = "at24,24c32";
reg = <0x52>;
};
};
Boards which relied on probing need to have such child nodes added.
Regards,
Wolfram
--
Pengutronix e.K. | Wolfram Sang |
Industrial Linux Solutions | http://www.pengutronix.de/ |
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2009-04-16 11:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-16 9:06 [PATCH] assign a default class to MPC adapter Michael Lawnick
[not found] ` <49E6F4F9.3060705-Mmb7MZpHnFY@public.gmane.org>
2009-04-16 9:20 ` Wolfram Sang
[not found] ` <20090416092012.GB3052-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2009-04-16 10:55 ` Michael Lawnick
2009-04-16 11:01 ` Michael Lawnick
[not found] ` <49E7101E.6070806-Mmb7MZpHnFY@public.gmane.org>
2009-04-16 11:47 ` Wolfram Sang [this message]
[not found] ` <20090416114701.GD3052-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2009-04-16 13:36 ` Michael Lawnick
[not found] ` <49E7344C.2060704-Mmb7MZpHnFY@public.gmane.org>
2009-04-16 13:55 ` Jean Delvare
[not found] ` <49E82270.4030509@gmx.de>
[not found] ` <49E82270.4030509-Mmb7MZpHnFY@public.gmane.org>
2009-04-17 7:33 ` Jean Delvare
[not found] ` <20090417093356.79f38e40-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>
2009-04-17 7:46 ` Wolfram Sang
2009-04-16 14:05 ` Wolfram Sang
2009-04-21 6:47 ` Michael Lawnick
[not found] ` <49ED6C0D.2060607-Mmb7MZpHnFY@public.gmane.org>
2009-04-21 7:13 ` Wolfgang Grandegger
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=20090416114701.GD3052@pengutronix.de \
--to=w.sang-bicnvbalz9megne8c9+irq@public.gmane.org \
--cc=khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=ml.lawnick-Mmb7MZpHnFY@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