linux-arm-msm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sricharan R <sricharan@codeaurora.org>
To: devicetree@vger.kernel.org, linux-arm-msm@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, dmaengine@vger.kernel.org,
	galak@codeaurora.org, linux-i2c@vger.kernel.org,
	linux-kernel@vger.kernel.org, agross@codeaurora.org,
	iivanov@mm-sol.com
Cc: srichara@qti.qualcomm.com
Subject: [PATCH V2 0/6] i2c: qup: Add support for v2 tags and bam dma
Date: Tue,  7 Apr 2015 00:01:01 +0530	[thread overview]
Message-ID: <1428345067-21878-1-git-send-email-sricharan@codeaurora.org> (raw)

QUP from version 2.1.1 onwards, supports a new format of i2c command tags. Tag codes instructs the controller to perform a operation like read/write. This new tagging version supports and is required for adding bam dma capabilities.
v2 tags supports transfer of more than 256 bytes in a single i2c transaction. Also adding bam dma support facilitates transferring each i2c_msg in i2c_msgs without a 'stop' bit in between which is required for some of the clients.

This series depends on the below bam dma bug fix
 https://lkml.org/lkml/2015/2/20/47

Tested this series on apq8074 dragon board eeprom client on i2c bus1

[V2] Addressed comments from Ivan T. Ivanov, Andy Gross
[v1] Initial Version

Andy Gross (1):
  i2c: qup: Add V2 tags support

Sricharan R (5):
  i2c: qup: Change qup_wait_writeready function to use for all timeouts
  i2c: qup: Add bam dma capabilities
  i2c: qup: Transfer every i2c_msg in i2c_msgs without stop
  dts: msm8974: Add blsp2_bam dma node
  dts: msm8974: Add dma channels for blsp2_i2c1 node

 arch/arm/boot/dts/qcom-msm8974.dtsi |  14 +-
 drivers/i2c/busses/i2c-qup.c        | 788 +++++++++++++++++++++++++++++++++---
 2 files changed, 748 insertions(+), 54 deletions(-)

-- 
1.8.2.1

             reply	other threads:[~2015-04-06 18:31 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-06 18:31 Sricharan R [this message]
2015-04-06 18:31 ` [PATCH V2 2/6] i2c: qup: Add V2 tags support Sricharan R
     [not found]   ` <1428345067-21878-3-git-send-email-sricharan-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2015-04-07  5:06     ` Andy Gross
     [not found]       ` <20150407050640.GB9225-zC7DfRvBq/JWk0Htik3J/w@public.gmane.org>
2015-04-08  5:30         ` Sricharan
2015-04-06 18:31 ` [PATCH V2 3/6] i2c: qup: Add bam dma capabilities Sricharan R
2015-04-06 18:31 ` [PATCH V2 4/6] i2c: qup: Transfer every i2c_msg in i2c_msgs without stop Sricharan R
     [not found] ` <1428345067-21878-1-git-send-email-sricharan-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2015-04-06 18:31   ` [PATCH V2 1/6] i2c: qup: Change qup_wait_writeready function to use for all timeouts Sricharan R
2015-04-06 18:31   ` [PATCH V2 5/6] dts: msm8974: Add blsp2_bam dma node Sricharan R
2015-04-06 18:31 ` [PATCH V2 6/6] dts: msm8974: Add dma channels for blsp2_i2c1 node Sricharan R

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=1428345067-21878-1-git-send-email-sricharan@codeaurora.org \
    --to=sricharan@codeaurora.org \
    --cc=agross@codeaurora.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dmaengine@vger.kernel.org \
    --cc=galak@codeaurora.org \
    --cc=iivanov@mm-sol.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=srichara@qti.qualcomm.com \
    /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).