linux-i2c.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: rajeev kumar <rajeevkumar.linux@gmail.com>
To: Harini Katakam <harinik@xilinx.com>
Cc: wsa@the-dreams.de, mark.rutland@arm.com, michal.simek@xilinx.com,
	soren.brinkmann@xilinx.com,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	linux-i2c@vger.kernel.org,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Harini Katakam <harinikatakamlinux@gmail.com>,
	Vishnu Motghare <vishnum@xilinx.com>
Subject: Re: [PATCH v3 2/2] i2c: cadence: Check for errata condition involving master receive
Date: Fri, 5 Dec 2014 14:03:21 +0530	[thread overview]
Message-ID: <CAA7nrtg7xG5NekMMPLH-XLV+KEurX+akubhLqc3o6DA9R1bd9Q@mail.gmail.com> (raw)
In-Reply-To: <1417766884-8383-3-git-send-email-harinik@xilinx.com>

On Fri, Dec 5, 2014 at 1:38 PM, Harini Katakam <harinik@xilinx.com> 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>
> ---
>
> v3:
> Add warning in case of unsupported transfer.
>

Reviewed-by: Rajeev Kumar <rajeevkumar.linux@gmail.com>

> v2:
> Dont defeteature repeated start. Just check for unsupported conditions in the
> driver and return error.
>
> ---
>  drivers/i2c/busses/i2c-cadence.c |   15 +++++++++++++++
>  1 file changed, 15 insertions(+)
>
> diff --git a/drivers/i2c/busses/i2c-cadence.c b/drivers/i2c/busses/i2c-cadence.c
> index 5f5d4fa..3ea3b7a 100644
> --- a/drivers/i2c/busses/i2c-cadence.c
> +++ b/drivers/i2c/busses/i2c-cadence.c
> @@ -541,6 +541,21 @@ 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\t");
> +                               dev_warn(adap->dev.parent,
> +                                       "receive is followed by a transfer\n");
> +                               return -EOPNOTSUPP;
> +               }
>                 id->bus_hold_flag = 1;
>                 reg = cdns_i2c_readreg(CDNS_I2C_CR_OFFSET);
>                 reg |= CDNS_I2C_CR_HOLD;
> --
> 1.7.9.5
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-i2c" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2014-12-05  8:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-05  8:08 [PATCH v3 0/2] Cadence I2C driver fixes Harini Katakam
     [not found] ` <1417766884-8383-1-git-send-email-harinik-gjFFaj9aHVfQT0dZR+AlfA@public.gmane.org>
2014-12-05  8:08   ` [PATCH v3 1/2] i2c: cadence: Handle > 252 byte transfers Harini Katakam
2014-12-05  8:08 ` [PATCH v3 2/2] i2c: cadence: Check for errata condition involving master receive Harini Katakam
2014-12-05  8:33   ` rajeev kumar [this message]
2014-12-05 17:11   ` 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=CAA7nrtg7xG5NekMMPLH-XLV+KEurX+akubhLqc3o6DA9R1bd9Q@mail.gmail.com \
    --to=rajeevkumar.linux@gmail.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=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;
as well as URLs for NNTP newsgroup(s).