From: Abhishek Sahu <absahu@codeaurora.org>
To: Wolfram Sang <wsa@the-dreams.de>
Cc: Andy Gross <andy.gross@linaro.org>,
Sricharan <sricharan@codeaurora.org>,
Andy Gross <agross@codeaurora.org>,
Archit Taneja <architt@codeaurora.org>,
linux-arm-msm <linux-arm-msm@vger.kernel.org>,
ntelkar@codeaurora.org,
Linux Kernel list <linux-kernel@vger.kernel.org>,
linux-i2c@vger.kernel.org, dmaengine@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/2] i2c: qup: Cleared the error bits in ISR
Date: Mon, 20 Jun 2016 18:18:41 +0530 [thread overview]
Message-ID: <7c979c4e5b5c1652211405ce1e93fe72@codeaurora.org> (raw)
In-Reply-To: <20160618163228.GG3017@tetsubishi>
On 2016-06-18 22:02, Wolfram Sang wrote:
>> We run the command i2cdetect for address 0x3 to 0x77. The QUP
>> generates
>> write error for address 0x3 to 0x7 apart from other bus errors since
>> these are reserved addresses. I was getting the crash in non DMA mode
>> and BAM hang in DMA mode before putting the fix.
>>
>> Also we have connected the I2C TPM and run the following script
>> overnight for both DMA and Non DMA mode. The script checks for
>> all transfer length and we are generating multiple NACK and
>> Non NACK error before each valid transfer.
>>
>> a=1
>>
>> while [ $a -lt 4096 ]
>> do
>> echo $a
>> i2cdetect -y -a -r 0 0x03 0x77
>> tpm-manager get_random $a
>> i2cdetect -y -a -r 1 0x03 0x77
>> a=`expr $a + 1`
>> done
>
> So, what is the outcome of this discussion?
Discussion was regarding resetting the QUP state in ISR and it is the
part of
existing code itself. The current patch only added the error checking
for bus
errors so we can go ahead with this patch. I have shared the script
which we
are using for testing error path.
next prev parent reply other threads:[~2016-06-20 12:48 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-09 12:44 [PATCH 0/2] i2c: qup: Fixed the DMA transfer errors Abhishek Sahu
2016-05-09 12:44 ` [PATCH 1/2] i2c: qup: Cleared the error bits in ISR Abhishek Sahu
2016-05-11 15:57 ` Sricharan
2016-05-11 17:34 ` Abhishek Sahu
2016-05-12 2:28 ` Sricharan
2016-05-12 5:13 ` Andy Gross
2016-05-12 6:18 ` Abhishek Sahu
2016-05-12 17:58 ` Andy Gross
2016-05-12 19:32 ` Abhishek Sahu
2016-05-12 20:05 ` Andy Gross
2016-05-12 20:27 ` Abhishek Sahu
2016-06-18 16:32 ` Wolfram Sang
2016-06-20 12:48 ` Abhishek Sahu [this message]
2016-07-15 6:33 ` Wolfram Sang
2016-05-09 12:44 ` [PATCH 2/2] i2c: qup: Fixed the DMA segments length Abhishek Sahu
2016-05-11 16:18 ` Sricharan
2016-05-11 17:43 ` Abhishek Sahu
2016-07-15 6:38 ` 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=7c979c4e5b5c1652211405ce1e93fe72@codeaurora.org \
--to=absahu@codeaurora.org \
--cc=agross@codeaurora.org \
--cc=andy.gross@linaro.org \
--cc=architt@codeaurora.org \
--cc=dmaengine@vger.kernel.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 \
--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).