From: "Sören Brinkmann" <soren.brinkmann@xilinx.com>
To: Harini Katakam <harini.katakam@xilinx.com>
Cc: <wsa@the-dreams.de>, <mark.rutland@arm.com>,
<michal.simek@xilinx.com>, <linux-arm-kernel@lists.infradead.org>,
<linux-i2c@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<harinikatakamlinux@gmail.com>, <harinik@xilinx.com>,
Vishnu Motghare <vishnum@xilinx.com>
Subject: Re: [PATCH v4 2/2] i2c: cadence: Check for errata condition involving master receive
Date: Wed, 10 Dec 2014 09:45:54 -0800 [thread overview]
Message-ID: <6b2bd13bcd934b0fb09712e8950348e6@BN1AFFO11FD005.protection.gbl> (raw)
In-Reply-To: <1418211884-5329-3-git-send-email-harinik@xilinx.com>
On Wed, 2014-12-10 at 05:14PM +0530, Harini Katakam wrote:
> Cadence I2C controller has the following bugs:
> - completion indication is not given to the driver at the end of
> a read/receive transfer with HOLD bit set.
> - Invalid read transaction are generated on the bus when HW timeout
> condition occurs with HOLD bit set.
>
> As a result of the above, if a set of messages to be transferred with
> repeated start includes any transfer following a read transfer,
> completion is never indicated and timeout occurs.
> Hence a check is implemented to return -EOPNOTSUPP for such sequences.
>
> Signed-off-by: Harini Katakam <harinik@xilinx.com>
> Signed-off-by: Vishnu Motghare <vishnum@xilinx.com>
> ---
>
> v4:
> Use single dev_warn and make message grep-able.
>
> v3:
> Add warning in case of unsupported transfer.
>
> v2:
> Dont defeteature repeated start. Just check for unsupported conditions in the
> driver and return error.
>
> ---
> drivers/i2c/busses/i2c-cadence.c | 14 ++++++++++++++
> 1 file changed, 14 insertions(+)
>
> diff --git a/drivers/i2c/busses/i2c-cadence.c b/drivers/i2c/busses/i2c-cadence.c
> index 5f5d4fa..f9269a6 100644
> --- a/drivers/i2c/busses/i2c-cadence.c
> +++ b/drivers/i2c/busses/i2c-cadence.c
> @@ -541,6 +541,20 @@ static int cdns_i2c_master_xfer(struct i2c_adapter *adap, struct i2c_msg *msgs,
> * processed with a repeated start.
> */
> if (num > 1) {
> + /*
> + * This controller does not give completion interrupt after a
> + * master receive transfer if HOLD bit is set (repeated start),
> + * resulting in SW timeout. Hence, if a receive transfer is
> + * followed by any other transfer, an error is returned
> + * indicating that this sequence is not supported.
> + */
> + for (count = 0; count < num-1; count++) {
> + if (msgs[count].flags & I2C_M_RD)
> + dev_warn(adap->dev.parent, "No support for "
> + "repeated start when receive is "
> + "followed by a transfer\n");
Still not grepable. There must be no line breaks in the string!
Sören
next prev parent reply other threads:[~2014-12-10 17:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-10 11:44 [PATCH v4 0/2] Cadence I2C driver fixes Harini Katakam
2014-12-10 11:44 ` [PATCH v4 1/2] i2c: cadence: Handle > 252 byte transfers Harini Katakam
2014-12-10 11:44 ` [PATCH v4 2/2] i2c: cadence: Check for errata condition involving master receive Harini Katakam
2014-12-10 17:45 ` Sören Brinkmann [this message]
2014-12-11 7:16 ` Harini Katakam
2014-12-11 17:28 ` Sören Brinkmann
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=6b2bd13bcd934b0fb09712e8950348e6@BN1AFFO11FD005.protection.gbl \
--to=soren.brinkmann@xilinx.com \
--cc=harini.katakam@xilinx.com \
--cc=harinik@xilinx.com \
--cc=harinikatakamlinux@gmail.com \
--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=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®