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, grygorii.strashko@ti.com,
vigneshr@ti.com
Cc: Franklin S Cooper Jr <fcooper@ti.com>
Subject: [PATCH v3 0/2] ARM: dts: keystone-k2g: Add I2C support for 66AK2G
Date: Fri, 8 Sep 2017 12:54:46 -0500 [thread overview]
Message-ID: <20170908175448.3367-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
Version 2 changes:
Moved ordering of pm runtime calls
Version 3 changes:
Dropped first patch since it was pulled in.
Remove clk = NULL statements
Fix error path
Franklin S Cooper Jr (2):
i2c: davinci: Add PM Runtime Support
dt-bindings: i2c: i2c-davinci: Update binding for 66AK2Gx pwr dm
property
.../devicetree/bindings/i2c/i2c-davinci.txt | 12 ++++
drivers/i2c/busses/i2c-davinci.c | 64 ++++++++++++++++++----
2 files changed, 65 insertions(+), 11 deletions(-)
--
2.9.4.dirty
next reply other threads:[~2017-09-08 17:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-08 17:54 Franklin S Cooper Jr [this message]
2017-09-08 17:54 ` [PATCH v3 1/2] i2c: davinci: Add PM Runtime Support Franklin S Cooper Jr
2017-09-11 11:29 ` Sekhar Nori
2017-09-11 20:07 ` Franklin S Cooper Jr
2017-09-11 20:11 ` Grygorii Strashko
2017-09-12 8:25 ` Sekhar Nori
2017-09-08 17:54 ` [PATCH v3 2/2] dt-bindings: i2c: i2c-davinci: Update binding for 66AK2Gx pwr dm property Franklin S Cooper Jr
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=20170908175448.3367-1-fcooper@ti.com \
--to=fcooper@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=grygorii.strashko@ti.com \
--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=vigneshr@ti.com \
--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).