From: Horng-Shyang Liao <hs.liao-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org>
To: CK Hu <ck.hu-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org>
Cc: Rob Herring <robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
Matthias Brugger
<matthias.bgg-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
Daniel Kurtz <djkurtz-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>,
Sascha Hauer <s.hauer-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
linux-mediatek-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
srv_heupstream-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org,
Sascha Hauer <kernel-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>,
Philipp Zabel <p.zabel-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>,
Nicolas Boichat
<drinkcat-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>,
cawa cheng <cawa.cheng-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org>,
Bibby Hsieh <bibby.hsieh-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org>,
YT Shen <yt.shen-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org>,
Daoyuan Huang
<daoyuan.huang-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org>,
Damon Chu <damon.chu-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org>,
Josh-YC Liu <josh-yc.liu-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org>,
Glory Hung <glory.hung-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org>,
Jiaguang Zhang
<jiaguang.zhang-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org>
Subject: Re: [PATCH v7 2/4] CMDQ: Mediatek CMDQ driver
Date: Fri, 27 May 2016 13:44:18 +0800 [thread overview]
Message-ID: <1464327858.8578.6.camel@mtksdaap41> (raw)
In-Reply-To: <1464247708.13536.14.camel@mtksdaap41>
Hi CK,
Reply in line.
On Thu, 2016-05-26 at 15:28 +0800, CK Hu wrote:
> Hi, HS:
>
> Replay inline.
>
> On Tue, 2016-05-24 at 20:27 +0800, Horng-Shyang Liao wrote:
> > Hi CK,
> >
> > Reply in line.
> >
> > On Tue, 2016-05-24 at 11:05 +0800, CK Hu wrote:
> > > Hi, HS:
> > >
> > > Some comments below.
> > >
> > ...
> > > > +static void cmdq_thread_irq_handler(struct cmdq *cmdq, int tid)
> > > > +{
> > > > + struct cmdq_thread *thread = &cmdq->thread[tid];
> > > > + unsigned long flags = 0L;
> > > > + int value;
> > > > +
> > > > + spin_lock_irqsave(&cmdq->exec_lock, flags);
> > > > +
> > > > + /*
> > > > + * it is possible for another CPU core
> > > > + * to run "release task" right before we acquire the spin lock
> > > > + * and thus reset / disable this HW thread
> > > > + * so we check both the IRQ flag and the enable bit of this thread
> > > > + */
> > > > + value = cmdq_thread_readl(thread, CMDQ_THR_IRQ_STATUS);
> > > > + if (!(value & CMDQ_THR_IRQ_MASK)) {
> > > > + spin_unlock_irqrestore(&cmdq->exec_lock, flags);
> > > > + return;
> > > > + }
> > >
> > > If this case happen and just return without clearing irq status, the irq
> > > would keep triggering and system hang up. So just remove this checking
> > > and go down to clear irq status.
> >
> > This case is safe because irq status is cleared.
> > But, next if condition has the problem which you mentioned.
> >
> > I will change it as below.
> >
> > if (!(cmdq_thread_readl(thread, CMDQ_THR_ENABLE_TASK) &
> > CMDQ_THR_ENABLED)) {
> > cmdq_thread_writel(thread, ~value, CMDQ_THR_IRQ_STATUS);
> > spin_unlock_irqrestore(&cmdq->exec_lock, flags);
> > return;
> > }
> >
> > If thread is disabled, tasks must be all finished.
> > Therefore, just clear irq status and return.
> >
>
> For irq status checking part, if irq status & irq mask is zero, remove
> this checking and let it go down, it still do nothing because value &
> CMDQ_THR_IRQ_ERROR is zero and value & CMDQ_THR_IRQ_DONE is zero. So you
> can just remove this checking and get the same result.
>
> In general HW design, once a HW is not enable, it does not trigger
> interrupt any more. Be sure that it's necessary to clear irq status even
> though thread is disable.
>
I Will remove first if condition,
so rewrite first two if condition parts as below.
value = cmdq_thread_readl(thread, CMDQ_THR_IRQ_STATUS);
cmdq_thread_writel(thread, ~value, CMDQ_THR_IRQ_STATUS);
if (!(cmdq_thread_readl(thread, CMDQ_THR_ENABLE_TASK) &
CMDQ_THR_ENABLED))
value = 0;
> > > > +
> > > > + if (!(cmdq_thread_readl(thread, CMDQ_THR_ENABLE_TASK) &
> > > > + CMDQ_THR_ENABLED)) {
> > > > + spin_unlock_irqrestore(&cmdq->exec_lock, flags);
> > > > + return;
> > > > + }
> > > > +
> > > > + cmdq_thread_writel(thread, ~value, CMDQ_THR_IRQ_STATUS);
> > > > +
> > > > + if (value & CMDQ_THR_IRQ_ERROR)
> > > > + cmdq_handle_error_done(cmdq, thread, true);
> > > > + else if (value & CMDQ_THR_IRQ_DONE)
> > > > + cmdq_handle_error_done(cmdq, thread, false);
> > >
> > > These irq status checking and clearing code here is the same as those in
> > > cmdq_task_handle_error_result(). To move the checking and clearing code
> > > into cmdq_handle_error_done() and here just to call
> > > cmdq_handle_error_done(cmdq, thread) would reduce duplicated code.
> >
> > Will do.
> >
> > > > +
> > > > + spin_unlock_irqrestore(&cmdq->exec_lock, flags);
> > > > +}
> > ...
> > ...
> > >
> > > Regards,
> > > CK
> >
> > Thanks,
> > HS
> >
>
> Regards,
> CK
>
>
Thanks,
HS
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2016-05-27 5:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-23 12:23 [PATCH v7 0/4] Mediatek MT8173 CMDQ support HS Liao
[not found] ` <1464006190-344-1-git-send-email-hs.liao-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org>
2016-05-23 12:23 ` [PATCH v7 1/4] dt-bindings: soc: Add documentation for the MediaTek GCE unit HS Liao
2016-05-23 12:23 ` [PATCH v7 2/4] CMDQ: Mediatek CMDQ driver HS Liao
2016-05-24 3:05 ` CK Hu
2016-05-24 12:27 ` Horng-Shyang Liao
2016-05-26 7:28 ` CK Hu
2016-05-27 5:44 ` Horng-Shyang Liao [this message]
2016-05-23 12:23 ` [PATCH v7 3/4] arm64: dts: mt8173: Add GCE node HS Liao
2016-05-23 12:23 ` [PATCH v7 4/4] CMDQ: suspend/resume protection HS Liao
2016-05-24 9:16 ` CK Hu
2016-05-24 12:34 ` Horng-Shyang Liao
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=1464327858.8578.6.camel@mtksdaap41 \
--to=hs.liao-nus5lvnupcjwk0htik3j/w@public.gmane.org \
--cc=bibby.hsieh-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org \
--cc=cawa.cheng-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org \
--cc=ck.hu-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org \
--cc=damon.chu-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org \
--cc=daoyuan.huang-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=djkurtz-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org \
--cc=drinkcat-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org \
--cc=glory.hung-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org \
--cc=jiaguang.zhang-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org \
--cc=josh-yc.liu-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org \
--cc=kernel-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-mediatek-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=matthias.bgg-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=p.zabel-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org \
--cc=robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=s.hauer-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org \
--cc=srv_heupstream-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org \
--cc=yt.shen-NuS5LvNUpcJWk0Htik3J/w@public.gmane.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 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).