From: Jagan Teki <jagan@edgeble.ai>
To: Heiko Stuebner <heiko@sntech.de>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Kever Yang <kever.yang@rock-chips.com>
Cc: linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, devicetree@vger.kernel.org,
Jagan Teki <jagan@edgeble.ai>,
linux-i2c@vger.kernel.org, Wolfram Sang <wsa@kernel.org>,
David Wu <david.wu@rock-chips.com>
Subject: [PATCH v5 1/6] i2c: rk3x: Add rv1126 support
Date: Thu, 15 Sep 2022 22:09:42 +0530 [thread overview]
Message-ID: <20220915163947.1922183-2-jagan@edgeble.ai> (raw)
In-Reply-To: <20220915163947.1922183-1-jagan@edgeble.ai>
Add i2c support for Rockchip RV1126 SoC.
Cc: linux-i2c@vger.kernel.org
Cc: Wolfram Sang <wsa@kernel.org>
Reviewed-by: Heiko Stuebner <heiko@sntech.de>
Signed-off-by: David Wu <david.wu@rock-chips.com>
Signed-off-by: Jagan Teki <jagan@edgeble.ai>
---
Changes for v5:
- collect Rob r-b
- Cced Wolfram
Changes for v4:
- new patch
drivers/i2c/busses/i2c-rk3x.c | 9 +++++++++
1 file changed, 9 insertions(+)
diff --git a/drivers/i2c/busses/i2c-rk3x.c b/drivers/i2c/busses/i2c-rk3x.c
index 2e98e7793bba..d1658ed76562 100644
--- a/drivers/i2c/busses/i2c-rk3x.c
+++ b/drivers/i2c/busses/i2c-rk3x.c
@@ -1165,6 +1165,11 @@ static const struct rk3x_i2c_soc_data rv1108_soc_data = {
.calc_timings = rk3x_i2c_v1_calc_timings,
};
+static const struct rk3x_i2c_soc_data rv1126_soc_data = {
+ .grf_offset = 0x118,
+ .calc_timings = rk3x_i2c_v1_calc_timings,
+};
+
static const struct rk3x_i2c_soc_data rk3066_soc_data = {
.grf_offset = 0x154,
.calc_timings = rk3x_i2c_v0_calc_timings,
@@ -1195,6 +1200,10 @@ static const struct of_device_id rk3x_i2c_match[] = {
.compatible = "rockchip,rv1108-i2c",
.data = &rv1108_soc_data
},
+ {
+ .compatible = "rockchip,rv1126-i2c",
+ .data = &rv1126_soc_data
+ },
{
.compatible = "rockchip,rk3066-i2c",
.data = &rk3066_soc_data
--
2.25.1
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-09-15 16:41 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-15 16:39 [PATCH v5 0/6] ARM: Add Rockchip RV1126 support Jagan Teki
2022-09-15 16:39 ` Jagan Teki [this message]
2022-09-16 19:29 ` [PATCH v5 1/6] i2c: rk3x: Add rv1126 support Wolfram Sang
2022-09-15 16:39 ` [PATCH v5 2/6] clk: rockchip: Add dt-binding header for RV1126 Jagan Teki
2022-09-15 16:39 ` [PATCH v5 3/6] dt-bindings: clock: rockchip: Document RV1126 CRU Jagan Teki
2022-09-15 16:39 ` [PATCH v5 4/6] clk: rockchip: Add clock controller support for RV1126 SoC Jagan Teki
2022-09-17 6:55 ` Heiko Stuebner
2022-09-17 11:58 ` Jagan Teki
2022-09-17 14:25 ` Heiko Stuebner
2022-09-15 16:39 ` [PATCH v5 5/6] ARM: dts: rockchip: Add Rockchip RV1126 pinctrl Jagan Teki
2022-09-17 14:26 ` Heiko Stuebner
2022-09-17 14:37 ` Jagan Teki
2022-09-18 9:29 ` Heiko Stübner
2022-09-15 16:39 ` [PATCH v5 6/6] ARM: dts: rockchip: Add Rockchip RV1126 SoC Jagan Teki
2022-09-23 13:33 ` Heiko Stuebner
2022-09-23 13:38 ` Jagan Teki
2022-09-18 8:45 ` (subset) [PATCH v5 0/6] ARM: Add Rockchip RV1126 support Heiko Stuebner
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=20220915163947.1922183-2-jagan@edgeble.ai \
--to=jagan@edgeble.ai \
--cc=david.wu@rock-chips.com \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=kever.yang@rock-chips.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--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).