From: Brendan Higgins <brendanhiggins@google.com>
To: linux-i2c@vger.kernel.org
Subject: [PATCH] i2c: slave framework support for SMBus Alert
Date: Tue, 9 Aug 2016 17:02:52 -0700 [thread overview]
Message-ID: <1470787373-26738-1-git-send-email-brendanhiggins@google.com> (raw)
This adds support for an SMBus Alert to be requested from a slave mode Linux
I2C driver.
It appears that there is an attempt to keep master mode SMBus framework code
separate from raw I2C framework code, but that only appears to apply to master
mode I2C code. This seemed to make the most sense as part of i2c_algorithm.
This will not affect any existing drivers.
This has been tested with a slave mode driver I am currently working which I
can provide upon request (I am planning on submitting the driver as well, but
it part of a larger upstream submission).
My apologies in advance for any mistakes I might have made in the submission
process (I am new to the kernel mailing list).
Thanks!
next reply other threads:[~2016-08-10 0:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-10 0:02 Brendan Higgins [this message]
2016-08-10 0:02 ` [PATCH] i2c: slave framework support for SMBus Alert Brendan Higgins
2016-08-10 8:26 ` Wolfram Sang
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=1470787373-26738-1-git-send-email-brendanhiggins@google.com \
--to=brendanhiggins@google.com \
--cc=linux-i2c@vger.kernel.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).