From: minyard@acm.org
To: Wolfram Sang <wsa@the-dreams.de>,
linux-i2c@vger.kernel.org, Jean Delvare <jdelvare@suse.de>
Cc: minyard@acm.org
Subject: [PATCH v2 0/3] Add parameters for sysfs added I2C devices
Date: Tue, 10 May 2016 11:11:36 -0500 [thread overview]
Message-ID: <1462896699-1627-1-git-send-email-minyard@acm.org> (raw)
This is a set of patches I posted earlier, it allows you to pass in
parameters when adding I2C devices through sysfs.
I really need this for the IPMI over I2C driver (The SSIF driver)
for a couple of reasons.
The SSIF driver itself needs to take a parameter to tell it's
address on the IPMI bus in case it's not the default. It's also
nice to be able to pass in debug parameters this way.
Second, the IPMI driver can use SMBus alerts, but if the SMBus
alert device is added via sysfs, there is no way to specify the
interrupt information, thus it's fairly useless.
The first patch adds the ability to have parameters for sysfs added
I2C devices. The second patch adds interrupt parameters for the
SMBus alert device. The last is the IPMI SSIF changes, just for
example, I can add those in the IPMI tree.
-corey
next reply other threads:[~2016-05-10 16:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-10 16:11 minyard [this message]
2016-05-10 16:11 ` [PATCH v2 1/3] i2c: Add parameters to sysfs-added i2c devices minyard
2016-05-11 17:23 ` Naveen Kaje
2021-06-25 14:14 ` Wolfram Sang
2016-05-10 16:11 ` [PATCH v2 2/3] i2c-smbus: Allow parms to be passed in from sysfs new_device minyard
2016-05-11 17:26 ` Naveen Kaje
2016-05-10 16:11 ` [PATCH v2 3/3] ipmi: Handle I2C parms in the SSIF driver minyard
2016-05-11 17:26 ` Naveen Kaje
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=1462896699-1627-1-git-send-email-minyard@acm.org \
--to=minyard@acm.org \
--cc=jdelvare@suse.de \
--cc=linux-i2c@vger.kernel.org \
--cc=wsa@the-dreams.de \
/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).