From: Shawn Guo <shawnguo@kernel.org>
To: "Peng Fan (OSS)" <peng.fan@oss.nxp.com>
Cc: wsa@kernel.org, aisheng.dong@nxp.com, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, s.hauer@pengutronix.de,
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: Re: [PATCH V3 0/7] i2c-imx-lpi2c: add IPG clock
Date: Sat, 3 Sep 2022 11:38:51 +0800 [thread overview]
Message-ID: <20220903033851.GE1728671@dragon> (raw)
In-Reply-To: <20220823030215.870414-1-peng.fan@oss.nxp.com>
On Tue, Aug 23, 2022 at 11:02:08AM +0800, Peng Fan (OSS) wrote:
> 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
Applied 3 DTS patches, thanks!
prev parent reply other threads:[~2022-09-03 3:39 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-23 3:02 [PATCH V3 0/7] i2c-imx-lpi2c: add IPG clock Peng Fan (OSS)
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 ` Shawn Guo [this message]
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=20220903033851.GE1728671@dragon \
--to=shawnguo@kernel.org \
--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=peng.fan@oss.nxp.com \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--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).