From: Alain Volmat <alain.volmat@st.com>
To: <wsa@kernel.org>, <pierre-yves.mordret@st.com>
Cc: <alexandre.torgue@st.com>, <linux-i2c@vger.kernel.org>,
<linux-stm32@st-md-mailman.stormreply.com>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <fabrice.gasnier@st.com>,
<alain.volmat@st.com>
Subject: [PATCH v3 0/2] i2c: stm32: add host-notify support via i2c slave
Date: Mon, 3 Aug 2020 07:17:54 +0200 [thread overview]
Message-ID: <1596431876-24115-1-git-send-email-alain.volmat@st.com> (raw)
This serie replaces the previous 'stm32-f7: Addition of SMBus Alert /
Host-notify features' serie to only focus on the SMBus Host-Notify feature.
It should be applied with "[PATCH] i2c: add binding to mark a bus as SMBus"
from Wolfram which defines the newly introduced "smbus" binding.
Alain Volmat (2):
i2c: smbus: add core function handling SMBus host-notify
i2c: stm32f7: Add SMBus Host-Notify protocol support
drivers/i2c/busses/Kconfig | 1 +
drivers/i2c/busses/i2c-stm32f7.c | 110 +++++++++++++++++++++++++++++++++------
drivers/i2c/i2c-smbus.c | 107 +++++++++++++++++++++++++++++++++++++
include/linux/i2c-smbus.h | 12 +++++
4 files changed, 215 insertions(+), 15 deletions(-)
--
v3: move smbus host-notify slave code into i2c-smbus.c file
rework slave callback index handling
add sanity check in slave free function
v2: fix a bad test within the i2c-stm32f7 driver leading to decrease of
available slave slot
next reply other threads:[~2020-08-03 5:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-03 5:17 Alain Volmat [this message]
2020-08-03 5:17 ` [PATCH v3 1/2] i2c: smbus: add core function handling SMBus host-notify Alain Volmat
2020-08-04 14:03 ` Pierre Yves MORDRET
2020-09-09 8:39 ` Wolfram Sang
2020-08-03 5:17 ` [PATCH v3 2/2] i2c: stm32f7: Add SMBus Host-Notify protocol support Alain Volmat
2020-08-04 14:04 ` Pierre Yves MORDRET
2020-09-09 8:39 ` 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=1596431876-24115-1-git-send-email-alain.volmat@st.com \
--to=alain.volmat@st.com \
--cc=alexandre.torgue@st.com \
--cc=fabrice.gasnier@st.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=pierre-yves.mordret@st.com \
--cc=wsa@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
all inboxes | Powered by JetHome®