From: khilman@baylibre.com (Kevin Hilman)
To: linus-amlogic@lists.infradead.org
Subject: [PATCH v2 5/9] mmc: meson-gx: improve interrupt handling
Date: Fri, 03 Feb 2017 10:10:27 -0800 [thread overview]
Message-ID: <7hzii3uovg.fsf@baylibre.com> (raw)
In-Reply-To: <23e1aac3-5761-944a-f3ca-cb88a9e44ad8@gmail.com> (Heiner Kallweit's message of "Wed, 1 Feb 2017 07:48:58 +0100")
Heiner Kallweit <hkallweit1@gmail.com> writes:
> Disabling and immediately re-enabling interrupts in meson_mmc_request
> doesn't provide a benefit. Instead enable interrupts in probe already.
> And disable interrupts in remove, this was missing so far.
>
> Signed-off-by: Heiner Kallweit <hkallweit1@gmail.com>
This isn't quite functionaly equivalent...
> ---
> v2:
> - no changes
> ---
> drivers/mmc/host/meson-gx-mmc.c | 10 ++++------
> 1 file changed, 4 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/mmc/host/meson-gx-mmc.c b/drivers/mmc/host/meson-gx-mmc.c
> index 4ce4c640..0fba23d2 100644
> --- a/drivers/mmc/host/meson-gx-mmc.c
> +++ b/drivers/mmc/host/meson-gx-mmc.c
> @@ -546,11 +546,6 @@ static void meson_mmc_request(struct mmc_host *mmc, struct mmc_request *mrq)
> /* Stop execution */
> writel(0, host->regs + SD_EMMC_START);
>
> - /* clear, ack, enable all interrupts */
> - writel(0, host->regs + SD_EMMC_IRQ_EN);
> - writel(IRQ_EN_MASK, host->regs + SD_EMMC_STATUS);
> - writel(IRQ_EN_MASK, host->regs + SD_EMMC_IRQ_EN);
> -
> host->mrq = mrq;
>
> if (mrq->sbc)
> @@ -777,8 +772,8 @@ static int meson_mmc_probe(struct platform_device *pdev)
> writel(0, host->regs + SD_EMMC_START);
>
> /* clear, ack, enable all interrupts */
> - writel(0, host->regs + SD_EMMC_IRQ_EN);
I'm not sure about this part. Without the "disable all" here...
> writel(IRQ_EN_MASK, host->regs + SD_EMMC_STATUS);
... this ack could cause an interrupt to fire, if one was pending based
on boot firmware activity. I did notice this during driver development
on some boards, which is why the "disable all" was added.
That may have been an artifact of a buggy driver during development, but
I left it in anyways.
> + writel(IRQ_EN_MASK, host->regs + SD_EMMC_IRQ_EN);
>
> ret = devm_request_threaded_irq(&pdev->dev, host->irq,
> meson_mmc_irq, meson_mmc_irq_thread,
> @@ -816,6 +811,9 @@ static int meson_mmc_remove(struct platform_device *pdev)
> if (WARN_ON(!host))
> return 0;
>
> + /* disable interrupts */
> + writel(0, host->regs + SD_EMMC_IRQ_EN);
> +
> if (host->bounce_buf)
> dma_free_coherent(host->dev, host->bounce_buf_size,
> host->bounce_buf, host->bounce_dma_addr);
Other than the nit above, the rest of the cleanup looks fine.
If you leave in the "disable all" during probe,
Reviewed-by: Kevin Hilman <khilman@baylibre.com>
Kevin
WARNING: multiple messages have this Message-ID (diff)
From: Kevin Hilman <khilman@baylibre.com>
To: Heiner Kallweit <hkallweit1@gmail.com>
Cc: Ulf Hansson <ulf.hansson@linaro.org>,
Carlo Caione <carlo@caione.org>,
linux-mmc@vger.kernel.org, linux-amlogic@lists.infradead.org
Subject: Re: [PATCH v2 5/9] mmc: meson-gx: improve interrupt handling
Date: Fri, 03 Feb 2017 10:10:27 -0800 [thread overview]
Message-ID: <7hzii3uovg.fsf@baylibre.com> (raw)
In-Reply-To: <23e1aac3-5761-944a-f3ca-cb88a9e44ad8@gmail.com> (Heiner Kallweit's message of "Wed, 1 Feb 2017 07:48:58 +0100")
Heiner Kallweit <hkallweit1@gmail.com> writes:
> Disabling and immediately re-enabling interrupts in meson_mmc_request
> doesn't provide a benefit. Instead enable interrupts in probe already.
> And disable interrupts in remove, this was missing so far.
>
> Signed-off-by: Heiner Kallweit <hkallweit1@gmail.com>
This isn't quite functionaly equivalent...
> ---
> v2:
> - no changes
> ---
> drivers/mmc/host/meson-gx-mmc.c | 10 ++++------
> 1 file changed, 4 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/mmc/host/meson-gx-mmc.c b/drivers/mmc/host/meson-gx-mmc.c
> index 4ce4c640..0fba23d2 100644
> --- a/drivers/mmc/host/meson-gx-mmc.c
> +++ b/drivers/mmc/host/meson-gx-mmc.c
> @@ -546,11 +546,6 @@ static void meson_mmc_request(struct mmc_host *mmc, struct mmc_request *mrq)
> /* Stop execution */
> writel(0, host->regs + SD_EMMC_START);
>
> - /* clear, ack, enable all interrupts */
> - writel(0, host->regs + SD_EMMC_IRQ_EN);
> - writel(IRQ_EN_MASK, host->regs + SD_EMMC_STATUS);
> - writel(IRQ_EN_MASK, host->regs + SD_EMMC_IRQ_EN);
> -
> host->mrq = mrq;
>
> if (mrq->sbc)
> @@ -777,8 +772,8 @@ static int meson_mmc_probe(struct platform_device *pdev)
> writel(0, host->regs + SD_EMMC_START);
>
> /* clear, ack, enable all interrupts */
> - writel(0, host->regs + SD_EMMC_IRQ_EN);
I'm not sure about this part. Without the "disable all" here...
> writel(IRQ_EN_MASK, host->regs + SD_EMMC_STATUS);
... this ack could cause an interrupt to fire, if one was pending based
on boot firmware activity. I did notice this during driver development
on some boards, which is why the "disable all" was added.
That may have been an artifact of a buggy driver during development, but
I left it in anyways.
> + writel(IRQ_EN_MASK, host->regs + SD_EMMC_IRQ_EN);
>
> ret = devm_request_threaded_irq(&pdev->dev, host->irq,
> meson_mmc_irq, meson_mmc_irq_thread,
> @@ -816,6 +811,9 @@ static int meson_mmc_remove(struct platform_device *pdev)
> if (WARN_ON(!host))
> return 0;
>
> + /* disable interrupts */
> + writel(0, host->regs + SD_EMMC_IRQ_EN);
> +
> if (host->bounce_buf)
> dma_free_coherent(host->dev, host->bounce_buf_size,
> host->bounce_buf, host->bounce_dma_addr);
Other than the nit above, the rest of the cleanup looks fine.
If you leave in the "disable all" during probe,
Reviewed-by: Kevin Hilman <khilman@baylibre.com>
Kevin
next prev parent reply other threads:[~2017-02-03 18:10 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <584e5061-d359-1436-05ee-3767a5a4b10f@gmail.com>
2017-02-01 6:48 ` [PATCH v2 2/9] mmc: meson-gx: minor improvements in meson_mmc_set_ios Heiner Kallweit
2017-02-01 6:48 ` Heiner Kallweit
2017-02-01 6:48 ` [PATCH v2 3/9] mmc: meson-gx: improve meson_mmc_clk_set Heiner Kallweit
2017-02-01 6:48 ` Heiner Kallweit
2017-02-01 6:48 ` [PATCH v2 4/9] mmc: meson-gx: improve meson_mmc_irq_thread Heiner Kallweit
2017-02-01 6:48 ` Heiner Kallweit
2017-02-03 18:03 ` Kevin Hilman
2017-02-03 18:03 ` Kevin Hilman
2017-02-01 6:48 ` [PATCH v2 5/9] mmc: meson-gx: improve interrupt handling Heiner Kallweit
2017-02-01 6:48 ` Heiner Kallweit
2017-02-03 18:10 ` Kevin Hilman [this message]
2017-02-03 18:10 ` Kevin Hilman
2017-02-01 6:49 ` [PATCH v2 6/9] mmc: meson-gx: set max block count and request size Heiner Kallweit
2017-02-01 6:49 ` Heiner Kallweit
2017-02-01 6:49 ` [PATCH v2 7/9] mmc: meson-gx: reduce bounce buffer size Heiner Kallweit
2017-02-01 6:49 ` Heiner Kallweit
2017-02-03 18:18 ` Kevin Hilman
2017-02-03 18:18 ` Kevin Hilman
2017-02-01 6:49 ` [PATCH v2 8/9] mmc: meson-gx: remove unneeded checks in remove Heiner Kallweit
2017-02-01 6:49 ` Heiner Kallweit
2017-02-03 18:20 ` Kevin Hilman
2017-02-03 18:20 ` Kevin Hilman
2017-02-01 6:49 ` [PATCH v2 9/9] mmc: meson-gx: add support for HS400 mode Heiner Kallweit
2017-02-01 6:49 ` Heiner Kallweit
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=7hzii3uovg.fsf@baylibre.com \
--to=khilman@baylibre.com \
--cc=linus-amlogic@lists.infradead.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 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.