From: Alain Volmat <alain.volmat@foss.st.com>
To: <wsa@kernel.org>, <robh+dt@kernel.org>
Cc: <mark.rutland@arm.com>, <pierre-yves.mordret@foss.st.com>,
<mcoquelin.stm32@gmail.com>, <alexandre.torgue@foss.st.com>,
<linux-i2c@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-stm32@st-md-mailman.stormreply.com>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <fabrice.gasnier@foss.st.com>,
<alain.volmat@foss.st.com>
Subject: [PATCH v4 0/2] i2c: stm32f7: add SMBus-Alert support
Date: Wed, 5 May 2021 15:14:37 +0200 [thread overview]
Message-ID: <1620220479-2647-1-git-send-email-alain.volmat@foss.st.com> (raw)
This serie adds support for SMBus Alert on the STM32F7.
A new binding smbus-alert is added in order to differenciate
with the existing smbus binding.
SMBus-Alert is an optional SMBus feature and SMBA alert control
and status logic must be enabled along with SMBALERT# pin
configured via pinctrl in the device tree. This is the
rational for adding "smbus-alert" property.
---
v4:
add a new generic smbus-alert property instead of st,smbus-alert
update driver to use smbus-alert instead of st,smbus-alert
v3:
use lore.kernel.org links instead of marc.info
v2:
When SMBUS alert isn't available on the board (SMBA unused), this
logic musn't be enabled. Enabling it unconditionally wrongly lead to get
SMBA interrupts.
So, add "st,smbus-alert" dedicated binding to have a smbus alert with a
consistent pin configuration in DT.
Alain Volmat (2):
i2c: add binding to mark a bus as supporting SMBus-Alert
i2c: stm32f7: add SMBus-Alert support
Documentation/devicetree/bindings/i2c/i2c.txt | 7 ++-
drivers/i2c/busses/i2c-stm32f7.c | 73 +++++++++++++++++++++++++++
2 files changed, 78 insertions(+), 2 deletions(-)
--
2.7.4
next reply other threads:[~2021-05-05 13:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-05 13:14 Alain Volmat [this message]
2021-05-05 13:14 ` [PATCH v4 1/2] i2c: add binding to mark a bus as supporting SMBus-Alert Alain Volmat
2021-05-07 0:55 ` Rob Herring
2021-05-25 19:47 ` Wolfram Sang
2021-05-25 19:53 ` Wolfram Sang
2021-05-05 13:14 ` [PATCH v4 2/2] i2c: stm32f7: add SMBus-Alert support Alain Volmat
2021-05-10 8:02 ` Pierre Yves MORDRET
2021-05-25 19:53 ` 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=1620220479-2647-1-git-send-email-alain.volmat@foss.st.com \
--to=alain.volmat@foss.st.com \
--cc=alexandre.torgue@foss.st.com \
--cc=devicetree@vger.kernel.org \
--cc=fabrice.gasnier@foss.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=mark.rutland@arm.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=pierre-yves.mordret@foss.st.com \
--cc=robh+dt@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).