From: Lukasz Luba <lukasz.luba@arm.com>
To: Bernard Zhao <bernard@vivo.com>, Kukjin Kim <kgene@kernel.org>,
Krzysztof Kozlowski <krzk@kernel.org>,
linux-pm@vger.kernel.org, linux-samsung-soc@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Cc: opensource.kernel@vivo.com
Subject: Re: [PATCH v3] memory/samsung: reduce protected code area in IRQ
Date: Tue, 12 May 2020 13:52:58 +0100 [thread overview]
Message-ID: <99adbca2-7f8f-b255-8538-8819f83d1991@arm.com> (raw)
In-Reply-To: <20200512123149.40162-1-bernard@vivo.com>
On 5/12/20 1:31 PM, Bernard Zhao wrote:
> This change will speed-up a bit this IRQ processing and there
> is no need to protect return value or printing.
>
> Signed-off-by: Bernard Zhao <bernard@vivo.com>
LGTM
Acked-by: Lukasz Luba <lukasz.luba@arm.com>
> ---
> Changes since v1:
> *change release lock before the if statement.
> *revert dmc->df->lock mutex lock to protect function
> exynos5_dmc_perf_events_check
>
> Changes since v2:
> *Improve subject and commit message
>
> Link for V1:
> *https://lore.kernel.org/patchwork/patch/1238888/
> ---
> drivers/memory/samsung/exynos5422-dmc.c | 6 ++----
> 1 file changed, 2 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/memory/samsung/exynos5422-dmc.c b/drivers/memory/samsung/exynos5422-dmc.c
> index 22a43d662833..25196d6268e2 100644
> --- a/drivers/memory/samsung/exynos5422-dmc.c
> +++ b/drivers/memory/samsung/exynos5422-dmc.c
> @@ -1346,15 +1346,13 @@ static irqreturn_t dmc_irq_thread(int irq, void *priv)
> struct exynos5_dmc *dmc = priv;
>
> mutex_lock(&dmc->df->lock);
> -
> exynos5_dmc_perf_events_check(dmc);
> -
> res = update_devfreq(dmc->df);
> + mutex_unlock(&dmc->df->lock);
> +
> if (res)
> dev_warn(dmc->dev, "devfreq failed with %d\n", res);
>
> - mutex_unlock(&dmc->df->lock);
> -
> return IRQ_HANDLED;
> }
>
>
next prev parent reply other threads:[~2020-05-12 12:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-12 12:31 [PATCH v3] memory/samsung: reduce protected code area in IRQ Bernard Zhao
2020-05-12 12:52 ` Lukasz Luba [this message]
2020-05-12 13:16 ` Krzysztof Kozlowski
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=99adbca2-7f8f-b255-8538-8819f83d1991@arm.com \
--to=lukasz.luba@arm.com \
--cc=bernard@vivo.com \
--cc=kgene@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=opensource.kernel@vivo.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;
as well as URLs for NNTP newsgroup(s).