[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190424122805.GA22366@vmlxhi-102.adit-jv.com>
Date: Wed, 24 Apr 2019 14:28:05 +0200
From: Eugeniu Rosca <erosca@...adit-jv.com>
To: Jiada Wang <jiada_wang@...tor.com>
CC: <rui.zhang@...el.com>, <edubezval@...il.com>,
<daniel.lezcano@...aro.org>, <linux-pm@...r.kernel.org>,
<linux-kernel@...r.kernel.org>, <horms+renesas@...ge.net.au>,
<niklas.soderlund+renesas@...natech.se>, <geert+renesas@...der.be>,
<sergei.shtylyov@...entembedded.com>,
<marek.vasut+renesas@...il.com>,
<kuninori.morimoto.gx@...esas.com>, <hien.dang.eb@...esas.com>,
<fabrizio.castro@...renesas.com>, <dien.pham.ry@...esas.com>,
<biju.das@...renesas.com>, <george_davis@...tor.com>,
<joshua_frkuska@...tor.com>, Eugeniu Rosca <erosca@...adit-jv.com>,
Eugeniu Rosca <roscaeugeniu@...il.com>
Subject: Re: [PATCH v4 1/2] thermal: rcar_gen3_thermal: fix interrupt type
On Wed, Apr 24, 2019 at 02:11:44PM +0900, Jiada Wang wrote:
> Currently IRQF_SHARED type interrupt line is allocated, but it
> is not appropriate, as the interrupt line isn't shared between
> different devices, instead IRQF_ONESHOT is the proper type.
>
> By changing interrupt type to IRQF_ONESHOT, now irq handler is
> no longer needed, as clear of interrupt status can be done in
> threaded interrupt context.
>
> Because IRQF_ONESHOT type interrupt line is kept disabled until
> the threaded handler has been run, so there is no need to protect
> read/write of REG_GEN3_IRQSTR with lock.
>
> Fixes: 7d4b269776ec6 ("enable hardware interrupts for trip points")
> Signed-off-by: Jiada Wang <jiada_wang@...tor.com>
Based on https://patchwork.kernel.org/cover/10914079/#22603533 :
Reviewed-and-Tested-by: Eugeniu Rosca <erosca@...adit-jv.com>
Thanks!
--
Best regards,
Eugeniu.
Powered by blists - more mailing lists