devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Heiko Stuebner <heiko@sntech.de>
To: Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Kever Yang <kever.yang@rock-chips.com>,
	Jagan Teki <jagan@edgeble.ai>
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, David Wu <david.wu@rock-chips.com>
Subject: Re: [PATCH v4 01/13] i2c: rk3x: Add rv1126 support
Date: Fri, 09 Sep 2022 19:28:09 +0200	[thread overview]
Message-ID: <6158946.mvXUDI8C0e@phil> (raw)
In-Reply-To: <20220907160207.3845791-2-jagan@edgeble.ai>

Hi Jagan,

it looks like this is missing Wolfram Sang, the i2c maintainer?

Am Mittwoch, 7. September 2022, 18:01:55 CEST schrieb Jagan Teki:
> Add i2c support for Rockchip RV1126 SoC.
> 
> Cc: linux-i2c@vger.kernel.org
> Signed-off-by: David Wu <david.wu@rock-chips.com>
> Signed-off-by: Jagan Teki <jagan@edgeble.ai>

Reviewed-by: Heiko Stuebner <heiko@sntech.de>


Heiko

> ---
> 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
> 





  reply	other threads:[~2022-09-09 17:28 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-07 16:01 [PATCH v4 00/13] ARM: Add Rockchip RV1126 support Jagan Teki
2022-09-07 16:01 ` [PATCH v4 01/13] i2c: rk3x: Add rv1126 support Jagan Teki
2022-09-09 17:28   ` Heiko Stuebner [this message]
2022-09-12 19:22     ` Jagan Teki
2022-09-07 16:01 ` [PATCH v4 02/13] clk: rockchip: Add MUXTBL variant Jagan Teki
2022-09-07 16:01 ` [PATCH v4 03/13] clk: rockchip: Add dt-binding header for RV1126 Jagan Teki
2022-09-12 20:56   ` Rob Herring
2022-09-07 16:01 ` [PATCH v4 04/13] dt-bindings: clock: rockchip: Document RV1126 CRU Jagan Teki
2022-09-07 16:01 ` [PATCH v4 05/13] clk: rockchip: Add clock controller support for RV1126 SoC Jagan Teki
2022-09-13 10:13   ` Heiko Stuebner
2022-09-07 16:02 ` [PATCH v4 06/13] dt-bindings: soc: rockchip: Document RV1126 grf Jagan Teki
2022-09-07 16:02 ` [PATCH v4 07/13] dt-bindings: soc: rockchip: Document RV1126 pmugrf Jagan Teki
2022-09-07 16:02 ` [PATCH v4 08/13] ARM: dts: rockchip: Add Rockchip RV1126 pinctrl Jagan Teki
2022-09-07 16:02 ` [PATCH v4 09/13] ARM: dts: rockchip: Add Rockchip RV1126 SoC Jagan Teki
2022-09-07 16:02 ` [PATCH v4 10/13] dt-bindings: vendor-prefixes: Add Edgeble AI Technologies Pvt. Ltd Jagan Teki
2022-09-07 16:02 ` [PATCH v4 11/13] dt-bindings: arm: rockchip: Add Edgeble AI Edge Compute Module 0 Carrier Jagan Teki
2022-09-07 16:02 ` [PATCH v4 12/13] ARM: dts: rockchip: rv1126: Add Edgeble AI Edge Compute Module 0 Jagan Teki
2022-09-07 16:02 ` [PATCH v4 13/13] ARM: dts: rockchip: rv1126: Add Edgeble AI Edge Compute Module 0 Carrier Jagan Teki
2022-09-13 10:11 ` (subset) [PATCH v4 00/13] 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=6158946.mvXUDI8C0e@phil \
    --to=heiko@sntech.de \
    --cc=david.wu@rock-chips.com \
    --cc=devicetree@vger.kernel.org \
    --cc=jagan@edgeble.ai \
    --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 \
    /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).