From: Franklin S Cooper Jr <fcooper@ti.com>
To: wsa@the-dreams.de, robh+dt@kernel.org, linux@armlinux.org.uk,
nsekhar@ti.com, linux-i2c@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Cc: Franklin S Cooper Jr <fcooper@ti.com>
Subject: [PATCH 0/4] ARM: dts: keystone-k2g: Add I2C support for 66AK2G
Date: Wed, 2 Aug 2017 17:17:49 -0500 [thread overview]
Message-ID: <20170802221753.13786-1-fcooper@ti.com> (raw)
Add I2C support to 66AK2G. Primary requirement is to add PM
Runtime support to the driver.
This has been tested on following platforms by performing simple i2c test
such as i2c detect and reading on board i2c devices:
K2G GP evm
OMAPL138
K2L GP EVM
and boot tested on:
K2E GP EVM
K2HK GP EVM
Franklin S Cooper Jr (3):
i2c: davinci: Preserve return value of devm_clk_get
i2c: davinci: Add PM Runtime Support
dt-bindings: i2c: i2c-davinci: Update binding for 66AK2Gx pwr dm
property
Vitaly Andrianov (1):
ARM: dts: keystone-k2g: Add I2C nodes
.../devicetree/bindings/i2c/i2c-davinci.txt | 12 +++++
arch/arm/boot/dts/keystone-k2g.dtsi | 36 +++++++++++++
drivers/i2c/busses/i2c-davinci.c | 63 ++++++++++++++++++----
3 files changed, 102 insertions(+), 9 deletions(-)
--
2.9.4.dirty
next reply other threads:[~2017-08-02 22:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-02 22:17 Franklin S Cooper Jr [this message]
2017-08-02 22:17 ` [PATCH 1/4] i2c: davinci: Preserve return value of devm_clk_get Franklin S Cooper Jr
2017-08-11 22:00 ` Grygorii Strashko
2017-08-02 22:17 ` [PATCH 2/4] i2c: davinci: Add PM Runtime Support Franklin S Cooper Jr
2017-08-11 22:11 ` Grygorii Strashko
[not found] ` <20170802221753.13786-1-fcooper-l0cyMroinI0@public.gmane.org>
2017-08-02 22:17 ` [PATCH 3/4] dt-bindings: i2c: i2c-davinci: Update binding for 66AK2Gx pwr dm property Franklin S Cooper Jr
2017-08-10 16:36 ` Rob Herring
2017-08-02 22:17 ` [PATCH 4/4] ARM: dts: keystone-k2g: Add I2C nodes Franklin S Cooper Jr
2017-08-11 22:18 ` Grygorii Strashko
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=20170802221753.13786-1-fcooper@ti.com \
--to=fcooper@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=nsekhar@ti.com \
--cc=robh+dt@kernel.org \
--cc=wsa@the-dreams.de \
/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).