From: "Peng Fan (OSS)" <peng.fan@oss.nxp.com>
To: wsa@kernel.org, aisheng.dong@nxp.com, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, shawnguo@kernel.org,
s.hauer@pengutronix.de
Cc: kernel@pengutronix.de, festevam@gmail.com, linux-imx@nxp.com,
linux-i2c@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, xiaoning.wang@nxp.com,
Peng Fan <peng.fan@nxp.com>
Subject: [PATCH V3 0/7] i2c-imx-lpi2c: add IPG clock
Date: Tue, 23 Aug 2022 11:02:08 +0800 [thread overview]
Message-ID: <20220823030215.870414-1-peng.fan@oss.nxp.com> (raw)
From: Peng Fan <peng.fan@nxp.com>
V3:
Add R-b
Correct clk_bulk_disable to clk_bulk_disable_unprepare in patch 7
V2:
use clk bulk API in driver to support backward compatibility.
Include a new patch, patch 1.
The i.MX LPI2C needs PER and IPG clock, not just PER or IPG clock.
The current driver/dts/bindings use one CLK. Although it works with
upstream kernel, but it not match the hardware design. If IPG clock is
disabled, the LPI2C will not work.
There are changes made to ARM32 i.MX7ULP dts, ARM64 i.MX8 dts, dt-
bindings, and the lpi2c driver.
The driver is updated to use bulk clk API to avoid break backward
compatibility. But it is hard to avoid dtbs_check pass, because the dts and
binding update are in separate patches.
Peng Fan (7):
ARM: dts: imx7ulp: update the LPI2C clock-names
dt-bindings: i2c: i2c-imx-lpi2c: add ipg clk
dt-bindings: i2c: i2c-imx-lpi2c: add dmas property
dt-bindings: i2c: i2c-imx-lpi2c: add i.MX93
arm64: dts: imx8-ss-dma: add IPG clock for i2c
ARM: dts: imx7ulp: Add IPG clock for lpi2c
i2c: imx-lpi2c: use bulk clk API
.../bindings/i2c/i2c-imx-lpi2c.yaml | 20 +++++++++++++---
arch/arm/boot/dts/imx7ulp.dtsi | 10 ++++----
.../arm64/boot/dts/freescale/imx8-ss-dma.dtsi | 20 +++++++++-------
drivers/i2c/busses/i2c-imx-lpi2c.c | 24 +++++++++----------
4 files changed, 47 insertions(+), 27 deletions(-)
--
2.37.1
next reply other threads:[~2022-08-23 3:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-23 3:02 Peng Fan (OSS) [this message]
2022-08-23 3:02 ` [PATCH V3 1/7] ARM: dts: imx7ulp: update the LPI2C clock-names Peng Fan (OSS)
2022-08-23 3:02 ` [PATCH V3 2/7] dt-bindings: i2c: i2c-imx-lpi2c: add ipg clk Peng Fan (OSS)
2022-08-30 10:07 ` Wolfram Sang
2022-08-23 3:02 ` [PATCH V3 3/7] dt-bindings: i2c: i2c-imx-lpi2c: add dmas property Peng Fan (OSS)
2022-08-30 10:07 ` Wolfram Sang
2022-08-23 3:02 ` [PATCH V3 4/7] dt-bindings: i2c: i2c-imx-lpi2c: add i.MX93 Peng Fan (OSS)
2022-08-30 10:07 ` Wolfram Sang
2022-08-23 3:02 ` [PATCH V3 5/7] arm64: dts: imx8-ss-dma: add IPG clock for i2c Peng Fan (OSS)
2022-08-23 3:02 ` [PATCH V3 6/7] ARM: dts: imx7ulp: Add IPG clock for lpi2c Peng Fan (OSS)
2022-08-23 3:02 ` [PATCH V3 7/7] i2c: imx-lpi2c: use bulk clk API Peng Fan (OSS)
2022-08-29 20:12 ` Wolfram Sang
2022-08-30 10:00 ` Peng Fan
2022-08-30 10:04 ` Wolfram Sang
2022-09-03 3:38 ` [PATCH V3 0/7] i2c-imx-lpi2c: add IPG clock Shawn Guo
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=20220823030215.870414-1-peng.fan@oss.nxp.com \
--to=peng.fan@oss.nxp.com \
--cc=aisheng.dong@nxp.com \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peng.fan@nxp.com \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=wsa@kernel.org \
--cc=xiaoning.wang@nxp.com \
/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).