From: Harini Katakam <harinik@xilinx.com>
To: wsa@the-dreams.de, grant.likely@linaro.org, robh+dt@kernel.org,
pawel.moll@arm.com, mark.rutland@arm.com,
ijc+devicetree@hellion.org.uk, galak@codeaurora.org
Cc: michal.simek@xilinx.com, soren.brinkmann@xilinx.com,
linux-arm-kernel@lists.infradead.org, linux-i2c@vger.kernel.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
harinik@xilinx.com, vishnum@xilinx.com
Subject: [PATCH 3/4] devicetree: bindings: Add defeature-repeated-start property for Cadence I2C
Date: Tue, 2 Dec 2014 15:35:48 +0530 [thread overview]
Message-ID: <1417514749-24319-4-git-send-email-harinik@xilinx.com> (raw)
In-Reply-To: <1417514749-24319-1-git-send-email-harinik@xilinx.com>
From: Vishnu Motghare <vishnum@xilinx.com>
This patch adds "defeature-repeated-start" property in i2c-cadence.txt.
Signed-off-by: Vishnu Motghare <vishnum@xilinx.com>
Signed-off-by: Harini Katakam <harinik@xilinx.com>
---
.../devicetree/bindings/i2c/i2c-cadence.txt | 11 +++++++++++
1 file changed, 11 insertions(+)
diff --git a/Documentation/devicetree/bindings/i2c/i2c-cadence.txt b/Documentation/devicetree/bindings/i2c/i2c-cadence.txt
index 7cb0b56..9d417a7 100644
--- a/Documentation/devicetree/bindings/i2c/i2c-cadence.txt
+++ b/Documentation/devicetree/bindings/i2c/i2c-cadence.txt
@@ -11,6 +11,17 @@ Required properties:
Optional properties:
- clock-frequency: Desired operating frequency, in Hz, of the bus.
- clock-names: Input clock name, should be 'pclk'.
+ - defeature-repeated-start: Include this property to defeature repeated start
+ This defeature is due to a few bugs in the
+ I2C controller.
+ Completion interrupt after a read/receive
+ operation is NOT obtained if HOLD bit is set
+ at that time. Because of this bug, repeated start
+ will only work if there are no transfers following
+ a read/receive transfer.
+ If HOLD is held for long without a transfer,
+ invalid read transactions are generated by the
+ controller due to a HW timeout related bug.
Example:
i2c@e0004000 {
--
1.7.9.5
next prev parent reply other threads:[~2014-12-02 10:06 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-02 10:05 [PATCH 0/4] Cadence I2C driver fixes Harini Katakam
2014-12-02 10:05 ` [PATCH 1/4] i2c: cadence: Handle > 252 byte transfers Harini Katakam
2014-12-02 10:05 ` [PATCH 2/4] i2c: cadence: Set the hardware time-out register to maximum value Harini Katakam
2014-12-03 11:28 ` Wolfram Sang
2014-12-02 10:05 ` Harini Katakam [this message]
2014-12-02 11:19 ` [PATCH 3/4] devicetree: bindings: Add defeature-repeated-start property for Cadence I2C Mark Rutland
2014-12-02 12:13 ` Harini Katakam
2014-12-02 12:52 ` Wolfram Sang
2014-12-02 13:10 ` Harini Katakam
2014-12-02 13:16 ` Wolfram Sang
2014-12-02 13:30 ` Harini Katakam
2014-12-02 14:15 ` Wolfram Sang
2014-12-02 15:12 ` Lars-Peter Clausen
2014-12-02 10:05 ` [PATCH 4/4] i2c: cadence: Defeature repeated start based on devicetree property Harini Katakam
2014-12-02 11:21 ` Mark Rutland
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=1417514749-24319-4-git-send-email-harinik@xilinx.com \
--to=harinik@xilinx.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=grant.likely@linaro.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=michal.simek@xilinx.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=soren.brinkmann@xilinx.com \
--cc=vishnum@xilinx.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
all inboxes | Powered by JetHome®