[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <7c979c4e5b5c1652211405ce1e93fe72@codeaurora.org>
Date: Mon, 20 Jun 2016 18:18:41 +0530
From: Abhishek Sahu <absahu@...eaurora.org>
To: Wolfram Sang <wsa@...-dreams.de>
Cc: Andy Gross <andy.gross@...aro.org>,
Sricharan <sricharan@...eaurora.org>,
Andy Gross <agross@...eaurora.org>,
Archit Taneja <architt@...eaurora.org>,
linux-arm-msm <linux-arm-msm@...r.kernel.org>,
ntelkar@...eaurora.org,
Linux Kernel list <linux-kernel@...r.kernel.org>,
linux-i2c@...r.kernel.org, dmaengine@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH 1/2] i2c: qup: Cleared the error bits in ISR
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.
Powered by blists - more mailing lists