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>, <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>, <george_davis@mentor.com>, <joshua_frkuska@mentor.com>, Eugeniu Rosca <erosca@de.adit-jv.com>, Eugeniu Rosca <roscaeugeniu@gmail.com> Subject: Re: [PATCH v4 0/2] thermal: rcar_gen3_thermal: fix IRQ issues Date: Wed, 24 Apr 2019 14:09:53 +0200 [thread overview] Message-ID: <20190424120953.GA26640@vmlxhi-102.adit-jv.com> (raw) In-Reply-To: <20190424051145.23072-1-jiada_wang@mentor.com> On Wed, Apr 24, 2019 at 02:11:43PM +0900, Jiada Wang wrote: > There are issues with interrupt handling in rcar_gen3_thermal driver. > > Currently IRQ is remain enabled after .remove, later if device is probed, > IRQ is requested before .thermal_init, this may cause IRQ function be > triggered but not able to clear IRQ status, thus cause system to hang. > > Since the irq line isn't shared between different devices, > so the proper interrupt type flag should be IRQF_ONESHOT. > > This patch-set fix these interrupt handling retated issues. > > --- > v4: remove 'spinlock_t lock' > add Fixes tag in ("thermal: rcar_gen3_thermal: fix interrupt type") > fix typos in ("thermal: rcar_gen3_thermal: disable interrupt in .remove") > > v3: fix to use correct code base > remove unused "flag" variable in rcar_gen3_thermal_irq > > v2: use irq type IRQF_ONESHOT instead of IRQF_SHARED > disable interrupt in .remove > > v1: initial version > > Jiada Wang (2): > thermal: rcar_gen3_thermal: fix interrupt type > thermal: rcar_gen3_thermal: disable interrupt in .remove > > drivers/thermal/rcar_gen3_thermal.c | 41 +++++++---------------------- > 1 file changed, 9 insertions(+), 32 deletions(-) > > -- > 2.19.2 For the record, below is the diff between v3 and v4 [1]. It accurately reflects my review comments in https://patchwork.kernel.org/patch/10913165/#22601305 . In addition, I made sure there are either false positives or no new issues reported by: - sparse v0.5.2-1-ga3c4716a703a - smatch v0.5.0-4785-g4968bcad1c08 - cppcheck 1.88 dev - make W=123 - make coccicheck I repeated the same test steps as described in https://patchwork.kernel.org/cover/10913163/#22602335 and the results were the same: Reviewed-and-Tested-by: Eugeniu Rosca <erosca@de.adit-jv.com> [1] diff --git a/drivers/thermal/rcar_gen3_thermal.c b/drivers/thermal/rcar_gen3_thermal.c index c63a86d3dac6..280230951dfe 100644 --- a/drivers/thermal/rcar_gen3_thermal.c +++ b/drivers/thermal/rcar_gen3_thermal.c @@ -14,7 +14,6 @@ #include <linux/of_device.h> #include <linux/platform_device.h> #include <linux/pm_runtime.h> -#include <linux/spinlock.h> #include <linux/sys_soc.h> #include <linux/thermal.h> @@ -82,7 +81,6 @@ struct rcar_gen3_thermal_tsc { struct rcar_gen3_thermal_priv { struct rcar_gen3_thermal_tsc *tscs[TSC_MAX_NUM]; unsigned int num_tscs; - spinlock_t lock; /* Protect interrupts on and off */ void (*thermal_init)(struct rcar_gen3_thermal_tsc *tsc); }; @@ -231,8 +229,8 @@ static void rcar_thermal_irq_set(struct rcar_gen3_thermal_priv *priv, bool on) static irqreturn_t rcar_gen3_thermal_irq(int irq, void *data) { struct rcar_gen3_thermal_priv *priv = data; - int i; u32 status; + int i; for (i = 0; i < priv->num_tscs; i++) { status = rcar_gen3_thermal_read(priv->tscs[i], REG_GEN3_IRQSTR); @@ -352,8 +350,6 @@ static int rcar_gen3_thermal_probe(struct platform_device *pdev) if (soc_device_match(r8a7795es1)) priv->thermal_init = rcar_gen3_thermal_init_r8a7795es1; - spin_lock_init(&priv->lock); - platform_set_drvdata(pdev, priv); /* -- 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, 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, george_davis@mentor.com, joshua_frkuska@mentor.com, Eugeniu Rosca <erosca@de.adit-jv.com>, Eugeniu Rosca <roscaeugeniu@gmail.com> Subject: Re: [PATCH v4 0/2] thermal: rcar_gen3_thermal: fix IRQ issues Date: Wed, 24 Apr 2019 14:09:53 +0200 [thread overview] Message-ID: <20190424120953.GA26640@vmlxhi-102.adit-jv.com> (raw) In-Reply-To: <20190424051145.23072-1-jiada_wang@mentor.com> On Wed, Apr 24, 2019 at 02:11:43PM +0900, Jiada Wang wrote: > There are issues with interrupt handling in rcar_gen3_thermal driver. > > Currently IRQ is remain enabled after .remove, later if device is probed, > IRQ is requested before .thermal_init, this may cause IRQ function be > triggered but not able to clear IRQ status, thus cause system to hang. > > Since the irq line isn't shared between different devices, > so the proper interrupt type flag should be IRQF_ONESHOT. > > This patch-set fix these interrupt handling retated issues. > > --- > v4: remove 'spinlock_t lock' > add Fixes tag in ("thermal: rcar_gen3_thermal: fix interrupt type") > fix typos in ("thermal: rcar_gen3_thermal: disable interrupt in .remove") > > v3: fix to use correct code base > remove unused "flag" variable in rcar_gen3_thermal_irq > > v2: use irq type IRQF_ONESHOT instead of IRQF_SHARED > disable interrupt in .remove > > v1: initial version > > Jiada Wang (2): > thermal: rcar_gen3_thermal: fix interrupt type > thermal: rcar_gen3_thermal: disable interrupt in .remove > > drivers/thermal/rcar_gen3_thermal.c | 41 +++++++---------------------- > 1 file changed, 9 insertions(+), 32 deletions(-) > > -- > 2.19.2 For the record, below is the diff between v3 and v4 [1]. It accurately reflects my review comments in https://patchwork.kernel.org/patch/10913165/#22601305 . In addition, I made sure there are either false positives or no new issues reported by: - sparse v0.5.2-1-ga3c4716a703a - smatch v0.5.0-4785-g4968bcad1c08 - cppcheck 1.88 dev - make W=123 - make coccicheck I repeated the same test steps as described in https://patchwork.kernel.org/cover/10913163/#22602335 and the results were the same: Reviewed-and-Tested-by: Eugeniu Rosca <erosca@de.adit-jv.com> [1] diff --git a/drivers/thermal/rcar_gen3_thermal.c b/drivers/thermal/rcar_gen3_thermal.c index c63a86d3dac6..280230951dfe 100644 --- a/drivers/thermal/rcar_gen3_thermal.c +++ b/drivers/thermal/rcar_gen3_thermal.c @@ -14,7 +14,6 @@ #include <linux/of_device.h> #include <linux/platform_device.h> #include <linux/pm_runtime.h> -#include <linux/spinlock.h> #include <linux/sys_soc.h> #include <linux/thermal.h> @@ -82,7 +81,6 @@ struct rcar_gen3_thermal_tsc { struct rcar_gen3_thermal_priv { struct rcar_gen3_thermal_tsc *tscs[TSC_MAX_NUM]; unsigned int num_tscs; - spinlock_t lock; /* Protect interrupts on and off */ void (*thermal_init)(struct rcar_gen3_thermal_tsc *tsc); }; @@ -231,8 +229,8 @@ static void rcar_thermal_irq_set(struct rcar_gen3_thermal_priv *priv, bool on) static irqreturn_t rcar_gen3_thermal_irq(int irq, void *data) { struct rcar_gen3_thermal_priv *priv = data; - int i; u32 status; + int i; for (i = 0; i < priv->num_tscs; i++) { status = rcar_gen3_thermal_read(priv->tscs[i], REG_GEN3_IRQSTR); @@ -352,8 +350,6 @@ static int rcar_gen3_thermal_probe(struct platform_device *pdev) if (soc_device_match(r8a7795es1)) priv->thermal_init = rcar_gen3_thermal_init_r8a7795es1; - spin_lock_init(&priv->lock); - platform_set_drvdata(pdev, priv); /* -- Best regards, Eugeniu.
next prev parent reply other threads:[~2019-04-24 12:10 UTC|newest] Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-04-24 5:11 [PATCH v4 0/2] thermal: rcar_gen3_thermal: fix IRQ issues Jiada Wang 2019-04-24 5:11 ` Jiada Wang 2019-04-24 5:11 ` [PATCH v4 1/2] thermal: rcar_gen3_thermal: fix interrupt type Jiada Wang 2019-04-24 5:11 ` Jiada Wang 2019-04-24 9:23 ` Simon Horman 2019-04-24 9:31 ` Daniel Lezcano 2019-04-24 12:28 ` Eugeniu Rosca 2019-04-24 12:28 ` Eugeniu Rosca 2019-04-24 5:11 ` [PATCH v4 2/2] thermal: rcar_gen3_thermal: disable interrupt in .remove Jiada Wang 2019-04-24 5:11 ` Jiada Wang 2019-04-24 9:23 ` Simon Horman 2019-04-24 9:38 ` Daniel Lezcano 2019-04-24 12:31 ` Eugeniu Rosca 2019-04-24 12:31 ` Eugeniu Rosca 2019-04-24 6:51 ` [PATCH v4 0/2] thermal: rcar_gen3_thermal: fix IRQ issues Niklas Söderlund 2019-04-24 12:09 ` Eugeniu Rosca [this message] 2019-04-24 12:09 ` Eugeniu Rosca 2019-05-07 23:54 ` Niklas Söderlund 2019-05-10 10:42 ` Eugeniu Rosca 2019-05-10 10:42 ` Eugeniu Rosca 2019-05-10 11:36 ` Niklas Söderlund 2019-05-10 15:50 ` Eugeniu Rosca 2019-05-10 15:50 ` Eugeniu Rosca
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=20190424120953.GA26640@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=george_davis@mentor.com \ --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=roscaeugeniu@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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.