From: Przemyslaw Wegrzyn <pwegrzyn-qaBtZ/OuEkOiu113P13oHA@public.gmane.org>
To: linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Finding particular I2C adapter?
Date: Fri, 07 Oct 2011 14:43:08 +0200 [thread overview]
Message-ID: <4E8EF3DC.7060704@codepainters.com> (raw)
Hi!
First of all - I know what I'm asking for is somewhat "broken by
design", but anyway...
I'm about to develop a driver for a custom chip attached to SMBus in a
sort of industrial PC (choosing SMBus was a really bad idea, imho, but
unfortunately I can't change hardware team decisions).
While developing the I2C client driver seems pretty straight-forward,
I'm slightly confused about making it look for the device on a
particular I2C adapter instance. The project is limited to particular
board types, each using ICH chipset, so I need to use i2c_adapter
controlled by i2c-i801 module.
Here's my understanding so far:
- it is not an embedded system in a strict sense -> thus no
i2c_board_info -> no static I2C configuration
- AFAIR I can force the bus and address using 'force' parameter at
module loading time (e.g. via /etc/modules), but the I2C adapter number
is not static anyway on PC, and depend on e.g. adapter modules loading
order, so I'm a bit afraid of users breaking this configuration too easily.
- similar issue with echo'ing to /sys/bus/i2c/devices/i2c-<n>/new_device
- I need to know the bus ID in advance
Ideally, I'd like to have a sort of wrapper module that will find the
proper i2c_adapter and instantiate my i2c_client explicitly. Yet I know
that iterating i2c adapters is discouraged at least (actually, is there
any API now allowing for this? calling i2c_get_adapter with successive
numbers is clearly a hack).
Any ideas?
BR,
Przemek
next reply other threads:[~2011-10-07 12:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-07 12:43 Przemyslaw Wegrzyn [this message]
[not found] ` <4E8EF3DC.7060704-qaBtZ/OuEkOiu113P13oHA@public.gmane.org>
2011-10-10 12:20 ` Finding particular I2C adapter? Przemyslaw Wegrzyn
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=4E8EF3DC.7060704@codepainters.com \
--to=pwegrzyn-qabtz/ouekoiu113p13oha@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.