Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
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
Message-ID: <1620220479-2647-1-git-send-email-alain.volmat@foss.st.com>
MIME-Version: 1.0
Content-Type: text/plain
Precedence: bulk

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