platform_data when using of?

[Wolfram Sang <w.sang-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>]

[-- Attachment #1.1: Type: text/plain, Size: 1212 bytes --]

Hello,

I finally could get the work started with I2C on a MPC8260-based
platform. I applied Jochen's series on top of 2.6.25 and it seems I
could get the i2c-cpm and the rtc-rs5c372 driver working (except that it
doesn't autoload as a module, but I think this is my fault somewhere).
I have not checked all yet, but at least some reasonable things do happen.

I now wanted to test the latest at24-driver on top of that and stumbled
over the fact, that I can't directly add platform_data to the dts-file.
(As at24 shall be a generic driver, data about the eeprom type needs to
be provided.) If I understood of correctly, I need to create another
child node and put all necessary data in there (what also means one
cannot use the predefined macros for known chips in at24.h). After that
I use of_get_property and collect the data.

So, at the end, every driver using platform_data has to cope with two
mechanisms to get the desired data? This sounds questionable to me, but
maybe I just got something wrong as this is my first contact with of.

Kind regards,

   Wolfram

-- 
  Dipl.-Ing. Wolfram Sang | http://www.pengutronix.de
 Pengutronix - Linux Solutions for Science and Industry

[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

[-- Attachment #2: Type: text/plain, Size: 157 bytes --]

_______________________________________________
i2c mailing list
i2c-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org
http://lists.lm-sensors.org/mailman/listinfo/i2c