From: Adrian Hunter <adrian.hunter@intel.com>
To: Shawn Lin <shawn.lin@rock-chips.com>,
Ulf Hansson <ulf.hansson@linaro.org>
Cc: linux-mmc@vger.kernel.org
Subject: Re: [RFC PATCH 6/6] mmc: sdhci: remove CONFIG_MMC_DEBUG from the driver
Date: Tue, 18 Jul 2017 12:38:20 +0300 [thread overview]
Message-ID: <b21d0902-826c-c4b2-0bf0-7ff453a9bfa6@intel.com> (raw)
In-Reply-To: <1500368503-160501-2-git-send-email-shawn.lin@rock-chips.com>
On 18/07/17 12:01, Shawn Lin wrote:
> sdhci uses CONFIG_MMC_DEBUG for showing ADMA descriptor
> when occurring ADMA error. And it's also used to dump the
> registers whenever calling sdhci_add_host.
>
> On one hand, I don't see any burden to always print the state
> ADMA descriptor as it's rare and will help folks better understand
> what was happening when seeing ADMA error.
>
> On the other, git-blame points out that CONFIG_MMC_DEBUG for
> sdhci_add_host was added since it's merged for the first time.
> I don't know what exactly the intention was, but I guess folks
> don't need it at all? IMHO, it's another all-or-none proposition.
> I'd prefer to remove this sdhci_dumpregs from sdhci_add_host totally.
>
> Signed-off-by: Shawn Lin <shawn.lin@rock-chips.com>
>
> ---
>
> drivers/mmc/host/sdhci.c | 8 --------
> 1 file changed, 8 deletions(-)
>
> diff --git a/drivers/mmc/host/sdhci.c b/drivers/mmc/host/sdhci.c
> index ecd0d43..82f1761 100644
> --- a/drivers/mmc/host/sdhci.c
> +++ b/drivers/mmc/host/sdhci.c
> @@ -2502,7 +2502,6 @@ static void sdhci_cmd_irq(struct sdhci_host *host, u32 intmask)
> sdhci_finish_command(host);
> }
>
> -#ifdef CONFIG_MMC_DEBUG
> static void sdhci_adma_show_error(struct sdhci_host *host)
> {
> void *desc = host->adma_table;
> @@ -2530,9 +2529,6 @@ static void sdhci_adma_show_error(struct sdhci_host *host)
> break;
> }
> }
> -#else
> -static void sdhci_adma_show_error(struct sdhci_host *host) { }
> -#endif
>
> static void sdhci_data_irq(struct sdhci_host *host, u32 intmask)
> {
> @@ -3747,10 +3743,6 @@ int __sdhci_add_host(struct sdhci_host *host)
> goto untasklet;
> }
>
> -#ifdef CONFIG_MMC_DEBUG
> - sdhci_dumpregs(host);
> -#endif
We should still DBG() the interesting registers like SDHCI_HOST_VERSION,
SDHCI_PRESENT_STATE, SDHCI_CAPABILITIES, SDHCI_CAPABILITIES_1. Better to do
it earlier on though, like in sdhci_setup_host() after checking
mmc_regulator_get_supply().
> -
> ret = sdhci_led_register(host);
> if (ret) {
> pr_err("%s: Failed to register LED device: %d\n",
>
next prev parent reply other threads:[~2017-07-18 9:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-18 8:59 [RFC PATCH 0/6] Try to get rid of CONFIG_MMC_DEBUG Shawn Lin
2017-07-18 8:59 ` [RFC PATCH 1/6] mmc: core: remove check of host->removed for rescan routine Shawn Lin
2017-07-18 8:59 ` [RFC PATCH 2/6] mmc: core: always check the length of sglist with total data size Shawn Lin
2017-07-18 8:59 ` [RFC PATCH 3/6] mmc: core: turn the pr_info under CONFIG_MMC_DEBUG into pr_debug Shawn Lin
2017-07-18 8:59 ` [RFC PATCH 4/6] mmc: Kconfig: downgrade CONFIG_MMC_DEBUG for host drivers only Shawn Lin
2017-07-18 9:01 ` [RFC PATCH 5/6] mmc: wbsd: remove CONFIG_MMC_DEBUG from the driver Shawn Lin
2017-07-18 9:01 ` [RFC PATCH 6/6] mmc: sdhci: " Shawn Lin
2017-07-18 9:38 ` Adrian Hunter [this message]
2017-07-19 0:32 ` Shawn Lin
2017-07-19 7:16 ` Adrian Hunter
2017-07-19 7:41 ` Shawn Lin
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=b21d0902-826c-c4b2-0bf0-7ff453a9bfa6@intel.com \
--to=adrian.hunter@intel.com \
--cc=linux-mmc@vger.kernel.org \
--cc=shawn.lin@rock-chips.com \
--cc=ulf.hansson@linaro.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox