From: Wolfram Sang <wsa@the-dreams.de>
To: Sricharan R <sricharan@codeaurora.org>
Cc: gpramod@codeaurora.org, architt@codeaurora.org,
linux-arm-msm@vger.kernel.org, ntelkar@codeaurora.org,
linux-kernel@vger.kernel.org, andy.gross@linaro.org,
linux-i2c@vger.kernel.org, agross@codeaurora.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] drivers: i2c: Fix qup fifo handling
Date: Thu, 3 Mar 2016 22:14:18 +0100 [thread overview]
Message-ID: <20160303211418.GA1501@katana> (raw)
In-Reply-To: <1456502334-8687-1-git-send-email-sricharan@codeaurora.org>
[-- Attachment #1: Type: text/plain, Size: 639 bytes --]
On Fri, Feb 26, 2016 at 09:28:54PM +0530, Sricharan R wrote:
> After the addition of V2 support, there was a regression observed
> when testing it on MSM8996. The reason is driver puts the controller
> in to RUN state and writes the data to be 'tx' ed in fifo. But controller
> has to be put in to 'PAUSE' state and data has to written to fifo. Then
> should be put in to 'RUN' state separately.
>
> Signed-off-by: Sricharan R <sricharan@codeaurora.org>
Changed the subject to "i2c: qup: Fix fifo handling after adding V2
support". Please note the prefixes and the more detailed description.
Applied to for-next, thanks!
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: wsa@the-dreams.de (Wolfram Sang)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] drivers: i2c: Fix qup fifo handling
Date: Thu, 3 Mar 2016 22:14:18 +0100 [thread overview]
Message-ID: <20160303211418.GA1501@katana> (raw)
In-Reply-To: <1456502334-8687-1-git-send-email-sricharan@codeaurora.org>
On Fri, Feb 26, 2016 at 09:28:54PM +0530, Sricharan R wrote:
> After the addition of V2 support, there was a regression observed
> when testing it on MSM8996. The reason is driver puts the controller
> in to RUN state and writes the data to be 'tx' ed in fifo. But controller
> has to be put in to 'PAUSE' state and data has to written to fifo. Then
> should be put in to 'RUN' state separately.
>
> Signed-off-by: Sricharan R <sricharan@codeaurora.org>
Changed the subject to "i2c: qup: Fix fifo handling after adding V2
support". Please note the prefixes and the more detailed description.
Applied to for-next, thanks!
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20160303/01126608/attachment.sig>
next prev parent reply other threads:[~2016-03-03 21:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-26 15:58 [PATCH] drivers: i2c: Fix qup fifo handling Sricharan R
2016-02-26 15:58 ` Sricharan R
2016-03-01 5:51 ` Pramod Gurav
2016-03-01 5:51 ` Pramod Gurav
2016-03-01 5:51 ` Pramod Gurav
2016-03-03 21:14 ` Wolfram Sang [this message]
2016-03-03 21:14 ` Wolfram Sang
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=20160303211418.GA1501@katana \
--to=wsa@the-dreams.de \
--cc=agross@codeaurora.org \
--cc=andy.gross@linaro.org \
--cc=architt@codeaurora.org \
--cc=gpramod@codeaurora.org \
--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=ntelkar@codeaurora.org \
--cc=sricharan@codeaurora.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.