From: kheitke@codeaurora.org (Kenneth Heitke)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] i2c: QUP based bus driver for Qualcomm MSM chipsets
Date: Mon, 20 Jun 2011 21:50:51 -0600 [thread overview]
Message-ID: <4E00151B.90308@codeaurora.org> (raw)
In-Reply-To: <1308018114-19709-1-git-send-email-kheitke@codeaurora.org>
On 06/13/2011 08:21 PM, Kenneth Heitke wrote:
> This bus driver supports the QUP i2c hardware controller in the Qualcomm
> MSM SOCs. The Qualcomm Universal Peripheral Engine (QUP) is a general
> purpose data path engine with input/output FIFOs and an embedded i2c
> mini-core. The driver supports FIFO mode (for low bandwidth applications)
> and block mode (interrupt generated for each block-size data transfer).
> The driver currently does not support DMA transfers.
>
> Signed-off-by: Kenneth Heitke<kheitke@codeaurora.org>
> ---
> v2: updates to runtime PM calls (addresses comments from Mark Brown).
> Disable interrupts before setting completion object to NULL (bug fix).
> ---
> drivers/i2c/busses/Kconfig | 11 +
> drivers/i2c/busses/Makefile | 1 +
> drivers/i2c/busses/i2c-qup.c | 1175 +++++++++++++++++++++++++++++
> include/linux/platform_data/msm_qup_i2c.h | 24 +
> 4 files changed, 1211 insertions(+), 0 deletions(-)
> create mode 100644 drivers/i2c/busses/i2c-qup.c
> create mode 100644 include/linux/platform_data/msm_qup_i2c.h
Hi Ben,
If there are no objections to this i2c driver, can it be pulled into
your -next tree?
thank you,
Ken
--
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.
next prev parent reply other threads:[~2011-06-21 3:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-14 2:21 [PATCH v2] i2c: QUP based bus driver for Qualcomm MSM chipsets Kenneth Heitke
2011-06-21 3:50 ` Kenneth Heitke [this message]
2011-07-25 17:40 ` David Brown
2011-09-14 18:39 ` Kenneth Heitke
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=4E00151B.90308@codeaurora.org \
--to=kheitke@codeaurora.org \
--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).