From: "Peng Fan (OSS)" <peng.fan@oss.nxp.com>
To: 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 V2 0/7] i2c-imx-lpi2c: add IPG clock
Date: Tue, 16 Aug 2022 20:55:19 +0800 [thread overview]
Message-ID: <20220816125526.2978895-1-peng.fan@oss.nxp.com> (raw)
From: Peng Fan <peng.fan@nxp.com>
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
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-16 12:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-16 12:55 Peng Fan (OSS) [this message]
2022-08-16 12:55 ` [PATCH V2 1/7] ARM: dts: imx7ulp: update the LPI2C clock-names Peng Fan (OSS)
2022-08-16 12:55 ` [PATCH V2 2/7] dt-bindings: i2c: i2c-imx-lpi2c: add ipg clk Peng Fan (OSS)
2022-08-16 12:55 ` [PATCH V2 3/7] dt-bindings: i2c: i2c-imx-lpi2c: add dmas property Peng Fan (OSS)
2022-08-16 12:55 ` [PATCH V2 4/7] dt-bindings: i2c: i2c-imx-lpi2c: add i.MX93 Peng Fan (OSS)
2022-08-16 12:55 ` [PATCH V2 5/7] arm64: dts: imx8-ss-dma: add IPG clock for i2c Peng Fan (OSS)
2022-08-16 12:55 ` [PATCH V2 6/7] ARM: dts: imx7ulp: Add IPG clock for lpi2c Peng Fan (OSS)
2022-08-16 12:55 ` [PATCH V2 7/7] i2c: imx-lpi2c: use bulk clk API Peng Fan (OSS)
2022-08-22 22:18 ` Wolfram Sang
2022-08-22 23:37 ` Peng Fan
2022-08-22 8:46 ` [PATCH V2 0/7] i2c-imx-lpi2c: add IPG clock Peng Fan
2022-08-23 11:20 ` Krzysztof Kozlowski
2022-08-23 12:49 ` Peng Fan
2022-08-23 12:57 ` Krzysztof Kozlowski
2022-08-24 5:47 ` wsa
2022-08-22 11:49 ` Aisheng Dong
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=20220816125526.2978895-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=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).