From: Eugeniu Rosca <erosca@de.adit-jv.com>
To: Jiada Wang <jiada_wang@mentor.com>
Cc: rui.zhang@intel.com, edubezval@gmail.com,
daniel.lezcano@linaro.org, linux-pm@vger.kernel.org,
linux-kernel@vger.kernel.org, joshua_frkuska@mentor.com,
horms+renesas@verge.net.au,
niklas.soderlund+renesas@ragnatech.se, geert+renesas@glider.be,
sergei.shtylyov@cogentembedded.com,
marek.vasut+renesas@gmail.com, kuninori.morimoto.gx@renesas.com,
hien.dang.eb@renesas.com, fabrizio.castro@bp.renesas.com,
dien.pham.ry@renesas.com, biju.das@bp.renesas.com,
Eugeniu Rosca <erosca@de.adit-jv.com>,
Eugeniu Rosca <rosca.eugeniu@gmail.com>
Subject: Re: [PATCH v2 1/2] thermal: rcar_gen3_thermal: fix interrupt type
Date: Tue, 23 Apr 2019 15:07:24 +0200 [thread overview]
Message-ID: <20190423130724.GA10913@vmlxhi-102.adit-jv.com> (raw)
In-Reply-To: <20190423061218.29705-2-jiada_wang@mentor.com>
Hi Jiada,
On Tue, Apr 23, 2019 at 03:12:17PM +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.
>
> Signed-off-by: Jiada Wang <jiada_wang@mentor.com>
> ---
> drivers/thermal/rcar_gen3_thermal.c | 40 ++++++++---------------------
> 1 file changed, 10 insertions(+), 30 deletions(-)
>
[..]
I might be doing something wrong, but I couldn't apply this patch on top
of v5.1-rc6-4-g7142eaa58b49. All below commands failed (git v2.21.0):
- git am this.patch
- git apply this.patch
- patch -p1 < this.patch
--
Best regards,
Eugeniu.
WARNING: multiple messages have this Message-ID (diff)
From: Eugeniu Rosca <erosca@de.adit-jv.com>
To: Jiada Wang <jiada_wang@mentor.com>
Cc: <rui.zhang@intel.com>, <edubezval@gmail.com>,
<daniel.lezcano@linaro.org>, <linux-pm@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <joshua_frkuska@mentor.com>,
<horms+renesas@verge.net.au>,
<niklas.soderlund+renesas@ragnatech.se>,
<geert+renesas@glider.be>, <sergei.shtylyov@cogentembedded.com>,
<marek.vasut+renesas@gmail.com>,
<kuninori.morimoto.gx@renesas.com>, <hien.dang.eb@renesas.com>,
<fabrizio.castro@bp.renesas.com>, <dien.pham.ry@renesas.com>,
<biju.das@bp.renesas.com>, Eugeniu Rosca <erosca@de.adit-jv.com>,
Eugeniu Rosca <rosca.eugeniu@gmail.com>
Subject: Re: [PATCH v2 1/2] thermal: rcar_gen3_thermal: fix interrupt type
Date: Tue, 23 Apr 2019 15:07:24 +0200 [thread overview]
Message-ID: <20190423130724.GA10913@vmlxhi-102.adit-jv.com> (raw)
Message-ID: <20190423130724.7kzJjHg5RaCf5qZQuOT3lXF-vcscnhIRLR8PpSW4Gp4@z> (raw)
In-Reply-To: <20190423061218.29705-2-jiada_wang@mentor.com>
Hi Jiada,
On Tue, Apr 23, 2019 at 03:12:17PM +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.
>
> Signed-off-by: Jiada Wang <jiada_wang@mentor.com>
> ---
> drivers/thermal/rcar_gen3_thermal.c | 40 ++++++++---------------------
> 1 file changed, 10 insertions(+), 30 deletions(-)
>
[..]
I might be doing something wrong, but I couldn't apply this patch on top
of v5.1-rc6-4-g7142eaa58b49. All below commands failed (git v2.21.0):
- git am this.patch
- git apply this.patch
- patch -p1 < this.patch
--
Best regards,
Eugeniu.
next prev parent reply other threads:[~2019-04-23 13:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-23 6:12 [PATCH v2 0/2] thermal: rcar_gen3_thermal: fix IRQ issues Jiada Wang
2019-04-23 6:12 ` Jiada Wang
2019-04-23 6:12 ` [PATCH v2 1/2] thermal: rcar_gen3_thermal: fix interrupt type Jiada Wang
2019-04-23 6:12 ` Jiada Wang
2019-04-23 13:07 ` Eugeniu Rosca [this message]
2019-04-23 13:07 ` Eugeniu Rosca
2019-04-23 13:09 ` Jiada Wang
2019-04-23 13:09 ` Jiada Wang
2019-04-23 6:12 ` [PATCH v2 2/2] thermal: rcar_gen3_thermal: disable interrupt in .remove Jiada Wang
2019-04-23 6:12 ` Jiada Wang
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=20190423130724.GA10913@vmlxhi-102.adit-jv.com \
--to=erosca@de.adit-jv.com \
--cc=biju.das@bp.renesas.com \
--cc=daniel.lezcano@linaro.org \
--cc=dien.pham.ry@renesas.com \
--cc=edubezval@gmail.com \
--cc=fabrizio.castro@bp.renesas.com \
--cc=geert+renesas@glider.be \
--cc=hien.dang.eb@renesas.com \
--cc=horms+renesas@verge.net.au \
--cc=jiada_wang@mentor.com \
--cc=joshua_frkuska@mentor.com \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=marek.vasut+renesas@gmail.com \
--cc=niklas.soderlund+renesas@ragnatech.se \
--cc=rosca.eugeniu@gmail.com \
--cc=rui.zhang@intel.com \
--cc=sergei.shtylyov@cogentembedded.com \
/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