From: david.wu@rock-chips.com (David Wu)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v9 0/8] add i2c driver supported for rk3399
Date: Thu, 12 May 2016 15:52:58 +0800 [thread overview]
Message-ID: <1463039586-8134-1-git-send-email-david.wu@rock-chips.com> (raw)
There are three points differert from others:
- new method to caculate i2c timings for rk3399
- pclk and function clk are separated at rk3399
- add fast-plus mode supported for rk3399
David Wu (8):
i2c: rk3x: add documentation to fields in "struct rk3x_i2c"
i2c: rk3x: use struct "rk3x_i2c_calced_timings"
i2c: rk3x: Remove redundant rk3x_i2c_clean_ipd()
i2c: rk3x: Change SoC data to not use array
i2c: rk3x: Move spec timing data to "static const" structs
dt-bindings: i2c: rk3x: add support for rk3399
i2c: rk3x: add i2c support for rk3399 soc
i2c: rk3x: support fast-mode plus for rk3399
Documentation/devicetree/bindings/i2c/i2c-rk3x.txt | 16 +-
drivers/i2c/busses/i2c-rk3x.c | 495 +++++++++++++++++----
2 files changed, 432 insertions(+), 79 deletions(-)
--
1.9.1
next reply other threads:[~2016-05-12 7:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-12 7:52 David Wu [this message]
2016-05-12 7:52 ` [PATCH v9 1/8] i2c: rk3x: add documentation to fields in "struct rk3x_i2c" David Wu
2016-05-12 7:53 ` [PATCH v9 2/8] i2c: rk3x: use struct "rk3x_i2c_calced_timings" David Wu
2016-05-12 7:53 ` [PATCH v9 3/8] i2c: rk3x: Remove redundant rk3x_i2c_clean_ipd() David Wu
2016-05-12 7:53 ` [PATCH v9 4/8] i2c: rk3x: Change SoC data to not use array David Wu
2016-05-12 7:57 ` [PATCH v9 5/8] i2c: rk3x: Move spec timing data to "static const" structs David Wu
2016-05-12 7:57 ` [PATCH v9 6/8] dt-bindings: i2c: rk3x: add support for rk3399 David Wu
2016-05-12 7:58 ` [PATCH v9 7/8] i2c: rk3x: add i2c support for rk3399 soc David Wu
2016-05-12 8:01 ` [PATCH v9 8/8] i2c: rk3x: support fast-mode plus for rk3399 David Wu
2016-05-14 11:30 ` [PATCH v9 0/8] add i2c driver supported " 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=1463039586-8134-1-git-send-email-david.wu@rock-chips.com \
--to=david.wu@rock-chips.com \
--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).