From: Andy Gross <andy.gross@linaro.org>
To: Abhishek Sahu <absahu@codeaurora.org>
Cc: Sricharan <sricharan@codeaurora.org>,
agross@codeaurora.org, architt@codeaurora.org,
linux-arm-msm@vger.kernel.org, ntelkar@codeaurora.org,
linux-kernel@vger.kernel.org, linux-i2c@vger.kernel.org,
dmaengine@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
wsa@the-dreams.de
Subject: Re: [PATCH 1/2] i2c: qup: Cleared the error bits in ISR
Date: Thu, 12 May 2016 12:58:30 -0500 [thread overview]
Message-ID: <20160512175830.GA32019@hector> (raw)
In-Reply-To: <20160512061843.GA6187@chewinlnx07.qualcomm.com>
On Thu, May 12, 2016 at 11:48:43AM +0530, Abhishek Sahu wrote:
> On Thu, May 12, 2016 at 12:13:47AM -0500, Andy Gross wrote:
> > On Wed, May 11, 2016 at 11:04:17PM +0530, Abhishek Sahu wrote:
> >
> > <snip>
> >
> > > > In qup_i2c_xfer and qup_i2c_xfer_v2 state is set to RESET at the
> > > >end, when
> > > > there is no error. So would it be fine if we do it there
> > > >unconditionally ?
> > > >
> > > >Regards,
> > > > Sricharan
> > >
> > > RESET the QUP state wouldn't create any issue in the case of multiple calls.
> > > The existing code also RESET the QUP state for bus_err but it is not
> > > clearing
> > > status bits.
> >
> > It'd be better to not reset the QUP inside the ISR at all. I think the better
> > solution is making the reset occur in the xfer function. So just clear the bits
> > like you should in the isr, and defer reset till later.
>
> This is a HW workaround for QUP where we need to RESET the core in
> ISR. When interrupt is level triggerd, more than one interrupt may
> fire in error cases and QUP will generate these interrupts after
> completion of current interrupt. Thus we reset the core immediately
> in the ISR to ward off the next interrupt.
I wonder if that was just an expedient solution. And it seems like it could be
a little racy as a poll is not being done to make sure the QUP state machine
transitions to reset. Is there any documentation/errata on this? Or is this
just from commit comments?
Regards,
Andy
next prev parent reply other threads:[~2016-05-12 17:58 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 [this message]
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
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=20160512175830.GA32019@hector \
--to=andy.gross@linaro.org \
--cc=absahu@codeaurora.org \
--cc=agross@codeaurora.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).