* at24.c - "convenient" byte transfer through sysfs
@ 2008-07-25 23:37 Matti Kaasinen
0 siblings, 0 replies; only message in thread
From: Matti Kaasinen @ 2008-07-25 23:37 UTC (permalink / raw)
To: i2c-GZX6beZjE8VD60Wz+7aTrA
Hi all!
Could anyone explain a bit the "convenient" part of transferring bytes
through sysfs. Both reading and writing seems requiring kobject
reference to the client operation is directed to. I have tried finding
ways getting the kobject reference for required i2c client without
getting too convinced without the my solutions. The best choice so far
is using bus_for_each_dev -helper function scanning through all the i2c
clients instantiated on i2c bus. That requires bus_type structure as its
first parameter. Unfortunately i2c_bus_type is not exported at least in
2.6.24 that I'm playing currently with. I've seen patch discussions
related to exporting/not exporting i2c_bus_type. Do anyone know the
current status/future plans with it or have other suggestions regarding
this byte transfer structure through sysfs to i2c clients?
Thanks in advance,
Matti Kaasinen
_______________________________________________
i2c mailing list
i2c-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org
http://lists.lm-sensors.org/mailman/listinfo/i2c
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2008-07-25 23:37 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2008-07-25 23:37 at24.c - "convenient" byte transfer through sysfs Matti Kaasinen
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox