From: "Heiko Stübner" <heiko@sntech.de>
To: Yakir Yang <ykk@rock-chips.com>
Cc: Wolfram Sang <wsa@the-dreams.de>,
Rob Herring <robh+dt@kernel.org>,
Kumar Gala <galak@codeaurora.org>,
Pawel Moll <pawel.moll@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
devicetree@vger.kernel.org, linux-i2c@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org
Subject: Re: [PATCH 1/2] i2c: rk3x: add support for rk3228
Date: Mon, 14 Mar 2016 23:23:47 +0100 [thread overview]
Message-ID: <1737352.02BE0tcSEc@diego> (raw)
In-Reply-To: <1457924955-29996-1-git-send-email-ykk@rock-chips.com>
Am Montag, 14. März 2016, 11:09:15 schrieb Yakir Yang:
> Enable the I2C core for this SoC.
>
> Signed-off-by: Yakir Yang <ykk@rock-chips.com>
Reviewed-by: Heiko Stuebner <heiko@sntech.de>
Heiko
> ---
> Documentation/devicetree/bindings/i2c/i2c-rk3x.txt | 4 ++--
> drivers/i2c/busses/i2c-rk3x.c | 1 +
> 2 files changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/i2c/i2c-rk3x.txt
> b/Documentation/devicetree/bindings/i2c/i2c-rk3x.txt index f0d71bc..0b4a85f
> 100644
> --- a/Documentation/devicetree/bindings/i2c/i2c-rk3x.txt
> +++ b/Documentation/devicetree/bindings/i2c/i2c-rk3x.txt
> @@ -6,8 +6,8 @@ RK3xxx SoCs.
> Required properties :
>
> - reg : Offset and length of the register set for the device
> - - compatible : should be "rockchip,rk3066-i2c", "rockchip,rk3188-i2c" or
> - "rockchip,rk3288-i2c".
> + - compatible : should be "rockchip,rk3066-i2c", "rockchip,rk3188-i2c",
> + "rockchip,rk3228-i2c" or "rockchip,rk3288-i2c".
> - interrupts : interrupt number
> - clocks : parent clock
>
> diff --git a/drivers/i2c/busses/i2c-rk3x.c b/drivers/i2c/busses/i2c-rk3x.c
> index 9096d17..3dcc5f3 100644
> --- a/drivers/i2c/busses/i2c-rk3x.c
> +++ b/drivers/i2c/busses/i2c-rk3x.c
> @@ -855,6 +855,7 @@ static struct rk3x_i2c_soc_data soc_data[3] = {
> static const struct of_device_id rk3x_i2c_match[] = {
> { .compatible = "rockchip,rk3066-i2c", .data = (void *)&soc_data[0] },
> { .compatible = "rockchip,rk3188-i2c", .data = (void *)&soc_data[1] },
> + { .compatible = "rockchip,rk3228-i2c", .data = (void *)&soc_data[2] },
> { .compatible = "rockchip,rk3288-i2c", .data = (void *)&soc_data[2] },
> {},
> };
next prev parent reply other threads:[~2016-03-14 22:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-14 3:09 [PATCH 1/2] i2c: rk3x: add support for rk3228 Yakir Yang
2016-03-14 3:11 ` [PATCH 2/2] ARM: dts: rockchip: add i2c nodes RK3228 SoCs Yakir Yang
2016-04-12 21:39 ` Wolfram Sang
2016-04-13 1:23 ` Yakir Yang
2016-04-13 2:37 ` Wolfram Sang
2016-04-13 3:12 ` Yakir Yang
2016-04-13 20:57 ` Heiko Stübner
2016-03-14 22:23 ` Heiko Stübner [this message]
2016-03-18 20:16 ` [PATCH 1/2] i2c: rk3x: add support for rk3228 Rob Herring
2016-04-12 21:38 ` Wolfram Sang
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=1737352.02BE0tcSEc@diego \
--to=heiko@sntech.de \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=wsa@the-dreams.de \
--cc=ykk@rock-chips.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).