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>,
<amelie.delaunay@foss.st.com>, <alain.volmat@foss.st.com>
Subject: [PATCH 0/4] i2c: stm32: addition of STM32MP13 support
Date: Mon, 20 Jun 2022 12:54:01 +0200 [thread overview]
Message-ID: <20220620105405.145959-1-alain.volmat@foss.st.com> (raw)
This series adds the support for the stm32mp13.
Alain Volmat (4):
dt-bindings: i2c: st,stm32-i2c: don't mandate a reset line
i2c: stm32: only perform a reset if there is a reset property
dt-bindings: i2c: st,stm32-i2c: add entry for stm32mp13
i2c: stm32: add support for the STM32MP13 soc
.../devicetree/bindings/i2c/st,stm32-i2c.yaml | 3 ++-
drivers/i2c/busses/i2c-stm32f7.c | 20 +++++++++++++------
2 files changed, 16 insertions(+), 7 deletions(-)
--
2.25.1
next reply other threads:[~2022-06-20 10:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-20 10:54 Alain Volmat [this message]
2022-06-20 10:54 ` [PATCH 1/4] dt-bindings: i2c: st,stm32-i2c: don't mandate a reset line Alain Volmat
2022-06-28 13:41 ` Rob Herring
2022-06-29 19:44 ` Wolfram Sang
2022-07-06 22:46 ` Rob Herring
2022-07-07 6:38 ` Alain Volmat
2022-06-20 10:54 ` [PATCH 2/4] i2c: stm32: only perform a reset if there is a reset property Alain Volmat
2022-06-21 13:39 ` Pierre Yves MORDRET
2022-06-20 10:54 ` [PATCH 3/4] dt-bindings: i2c: st,stm32-i2c: add entry for stm32mp13 Alain Volmat
2022-06-20 10:54 ` [PATCH 4/4] i2c: stm32: add support for the STM32MP13 soc Alain Volmat
2022-06-21 13:40 ` Pierre Yves MORDRET
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=20220620105405.145959-1-alain.volmat@foss.st.com \
--to=alain.volmat@foss.st.com \
--cc=alexandre.torgue@foss.st.com \
--cc=amelie.delaunay@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).