From: heiko@sntech.de (Heiko Stuebner)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 2/6] dt-bindings: i2c: rk3x: add support for rk3328
Date: Thu, 16 Mar 2017 14:37:07 +0100 [thread overview]
Message-ID: <5087805.bpN37vxbEt@phil> (raw)
In-Reply-To: <1489670244-13328-3-git-send-email-cl@rock-chips.com>
Am Donnerstag, 16. M?rz 2017, 21:17:20 CET schrieb cl at rock-chips.com:
> From: Liang Chen <cl@rock-chips.com>
>
> The rk3328 i2c is the same as rk3399
>
> Signed-off-by: Liang Chen <cl@rock-chips.com>
Reviewed-by: Heiko Stuebner <heiko@sntech.de>
next prev parent reply other threads:[~2017-03-16 13:37 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-16 13:17 [PATCH v2 0/6] initialize dtsi file and dts file for RK3328 SoCs cl at rock-chips.com
2017-03-16 13:17 ` [PATCH v2 1/6] dt-bindings: iio: rockchip-saradc: add support for rk3328 cl at rock-chips.com
2017-03-16 13:36 ` Heiko Stuebner
2017-03-24 2:13 ` Rob Herring
2017-03-16 13:17 ` [PATCH v2 2/6] dt-bindings: i2c: rk3x: " cl at rock-chips.com
2017-03-16 13:37 ` Heiko Stuebner [this message]
2017-03-22 9:10 ` Wolfram Sang
2017-03-16 13:17 ` [PATCH v2 3/6] dt-bindings: soc: rockchip: grf: " cl at rock-chips.com
2017-03-24 2:14 ` Rob Herring
2017-03-16 13:17 ` [PATCH v2 4/6] arm64: dts: rockchip: add core dtsi file for RK3328 SoCs cl at rock-chips.com
2017-03-21 8:55 ` Heiko Stübner
2017-03-22 10:23 ` Elaine Zhang
2017-03-22 11:06 ` Heiko Stübner
2017-03-23 2:06 ` 陈亮
2017-03-23 9:16 ` Heiko Stübner
2017-03-23 3:33 ` 陈亮
2017-03-24 6:31 ` 陈亮
2017-03-24 7:12 ` Heiko Stübner
2017-03-22 18:09 ` Sudeep Holla
2017-03-23 2:15 ` 陈亮
2017-03-16 13:22 ` [PATCH v2 5/6] arm64: dts: rockchip: add dts file for RK3328 cl at rock-chips.com
2017-03-16 13:23 ` [PATCH v2 6/6] dt-bindings: document rockchip rk3328-evb board cl at rock-chips.com
2017-03-24 2:15 ` Rob Herring
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=5087805.bpN37vxbEt@phil \
--to=heiko@sntech.de \
--cc=linux-arm-kernel@lists.infradead.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).