From: Jean Delvare <khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org>
To: Linux I2C <linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Cc: Kay Sievers <kay.sievers-tD+1rO4QERM@public.gmane.org>
Subject: [PATCH 0/4] Convert i2c adapters from class devices to bus devices
Date: Wed, 5 Aug 2009 11:05:37 +0200 [thread overview]
Message-ID: <20090805110537.73735169@hyperion.delvare> (raw)
As Kay Sievers explained that i2c adapters should be bus devices rather
than class devices, convert them.
[PATCH 1/4] Add support for compatibility classes
[PATCH 2/4] i2c: Convert i2c clients to a device type
[PATCH 3/4] i2c: Convert i2c adapters to bus devices
[PATCH 4/4] i2c: Provide compatibility links for i2c adapters
drivers/base/class.c | 87 +++++++++++++++++++++++++
drivers/i2c/Kconfig | 8 ++
drivers/i2c/i2c-core.c | 165 +++++++++++++++++++++++++++++++++----------------
include/linux/device.h | 8 ++
4 files changed, 217 insertions(+), 51 deletions(-)
Care has been taken to not break user-space compatibility. I have also
updated libsensors and sensors-detect already to look for i2c adapters
in /sys/bus/i2c/devices rather than /sys/class/i2c-adapter. I am not
aware of other user-space applications or libraries using
/sys/class/i2c-adapter, but if you do please tell me.
Improvements are possible on the power management side, but I did not
have the time to deal with this now, so this is left for later.
--
Jean Delvare
next reply other threads:[~2009-08-05 9:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-05 9:05 Jean Delvare [this message]
[not found] ` <20090805110537.73735169-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>
2009-08-05 9:11 ` [PATCH 1/4] Add support for compatibility classes Jean Delvare
2009-08-05 9:12 ` [PATCH 2/4] i2c: Convert i2c clients to a device type Jean Delvare
2009-08-05 9:13 ` [PATCH 3/4] i2c: Convert i2c adapters to bus devices Jean Delvare
2009-08-05 9:14 ` [PATCH 4/4] i2c: Provide compatibility links for i2c adapters Jean Delvare
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=20090805110537.73735169@hyperion.delvare \
--to=khali-puyad+kwke1g9huczpvpmw@public.gmane.org \
--cc=kay.sievers-tD+1rO4QERM@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@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;
as well as URLs for NNTP newsgroup(s).