From: Jeremy McNicoll <jmcnicol@redhat.com>
To: Ritesh Harjani <riteshh@codeaurora.org>
Cc: ulf.hansson@linaro.org, adrian.hunter@intel.com,
linux-mmc@vger.kernel.org, linux-kernel@vger.kernel.org,
shawn.lin@rock-chips.com, stummala@codeaurora.org,
georgi.djakov@linaro.org, linux-arm-msm@vger.kernel.org,
pramod.gurav@linaro.org, jeremymc@redhat.com,
venkatg@codeaurora.org, asutoshd@codeaurora.org,
subhashj@codeaurora.org
Subject: Re: [RFC PATCH 2/3] mmc: sdhci-msm: Implement platform_dumpregs callback in sdhci-msm
Date: Fri, 13 Jan 2017 14:31:17 -0800 [thread overview]
Message-ID: <20170113223117.GB22862@mini-rhel.redhat.com> (raw)
In-Reply-To: <1483097531-9991-3-git-send-email-riteshh@codeaurora.org>
On Fri, Dec 30, 2016 at 05:02:10PM +0530, Ritesh Harjani wrote:
> From: Sahitya Tummala <stummala@codeaurora.org>
>
> Implement ->platform_dumpregs host operation to print the
> platform specific registers in addition to standard SDHC
> register during error conditions.
>
> Signed-off-by: Sahitya Tummala <stummala@codeaurora.org>
> Signed-off-by: Ritesh Harjani <riteshh@codeaurora.org>
> ---
> drivers/mmc/host/sdhci-msm.c | 34 ++++++++++++++++++++++++++++++++++
> 1 file changed, 34 insertions(+)
>
> diff --git a/drivers/mmc/host/sdhci-msm.c b/drivers/mmc/host/sdhci-msm.c
> index 32879b8..1241dbd 100644
> --- a/drivers/mmc/host/sdhci-msm.c
> +++ b/drivers/mmc/host/sdhci-msm.c
> @@ -29,6 +29,11 @@
> #define CORE_VERSION_MAJOR_MASK (0xf << CORE_VERSION_MAJOR_SHIFT)
> #define CORE_VERSION_MINOR_MASK 0xff
>
> +#define CORE_MCI_DATA_CNT 0x30
> +#define CORE_MCI_STATUS 0x34
> +#define CORE_MCI_FIFO_CNT 0x44
> +#define CORE_MCI_STATUS2 0x6c
> +
> #define CORE_HC_MODE 0x78
> #define HC_MODE_EN 0x1
> #define CORE_POWER 0x0
> @@ -77,6 +82,10 @@
> #define CORE_HC_SELECT_IN_HS400 (6 << 19)
> #define CORE_HC_SELECT_IN_MASK (7 << 19)
>
> +#define CORE_VENDOR_SPEC_FUNC2 0x110
> +#define CORE_VENDOR_SPEC_ADMA_ERR_ADDR0 0x114
> +#define CORE_VENDOR_SPEC_ADMA_ERR_ADDR1 0x118
> +
> #define CORE_CSR_CDC_CTLR_CFG0 0x130
> #define CORE_SW_TRIG_FULL_CALIB BIT(16)
> #define CORE_HW_AUTOCAL_ENA BIT(17)
> @@ -658,6 +667,30 @@ static int sdhci_msm_hs400_dll_calibration(struct sdhci_host *host)
> return ret;
> }
>
> +static void sdhci_msm_dumpregs(struct sdhci_host *host)
> +{
> + struct sdhci_pltfm_host *pltfm_host = sdhci_priv(host);
> + struct sdhci_msm_host *msm_host = sdhci_pltfm_priv(pltfm_host);
> +
> + pr_err("----------- PLATFORM REGISTER DUMP -----------\n");
> +
> + pr_err("Data cnt: 0x%08x | Fifo cnt: 0x%08x | Int sts: 0x%08x | Int sts2: 0x%08x\n",
> + readl_relaxed(msm_host->core_mem + CORE_MCI_DATA_CNT),
> + readl_relaxed(msm_host->core_mem + CORE_MCI_FIFO_CNT),
> + readl_relaxed(msm_host->core_mem + CORE_MCI_STATUS),
> + readl_relaxed(msm_host->core_mem + CORE_MCI_STATUS2));
> + pr_err("DLL cfg: 0x%08x | DLL sts: 0x%08x | SDCC ver: 0x%08x\n",
> + readl_relaxed(host->ioaddr + CORE_DLL_CONFIG),
> + readl_relaxed(host->ioaddr + CORE_DLL_STATUS),
> + readl_relaxed(msm_host->core_mem + CORE_MCI_VERSION));
> + pr_err("Vndr func: 0x%08x | Vndr adma err : addr0: 0x%08x addr1: 0x%08x\n",
> + readl_relaxed(host->ioaddr + CORE_VENDOR_SPEC),
> + readl_relaxed(host->ioaddr + CORE_VENDOR_SPEC_ADMA_ERR_ADDR0),
> + readl_relaxed(host->ioaddr + CORE_VENDOR_SPEC_ADMA_ERR_ADDR1));
> + pr_err("Vndr func2: 0x%08x\n",
> + readl_relaxed(host->ioaddr + CORE_VENDOR_SPEC_FUNC2));
> +}
> +
Why did you omit the printing of CORE_TESTBUS_CONFIG like that of
https://patchwork.kernel.org/patch/9442449/
and sdhci_dump_state() was dropped too. Being able to dump the rpm_info
was very handy for issues I was running into.
-jeremy
> static int sdhci_msm_execute_tuning(struct sdhci_host *host, u32 opcode)
> {
> int tuning_seq_cnt = 3;
> @@ -1035,6 +1068,7 @@ static void sdhci_msm_set_clock(struct sdhci_host *host, unsigned int clock)
> .set_bus_width = sdhci_set_bus_width,
> .set_uhs_signaling = sdhci_msm_set_uhs_signaling,
> .voltage_switch = sdhci_msm_voltage_switch,
> + .platform_dumpregs = sdhci_msm_dumpregs,
> };
>
> static const struct sdhci_pltfm_data sdhci_msm_pdata = {
> --
> The Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
> a Linux Foundation Collaborative Project.
>
next prev parent reply other threads:[~2017-01-13 22:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-30 11:32 [RFC PATCH 0/3] mmc: sdhci: sdhci-msm: Add more debug logs Ritesh Harjani
2016-12-30 11:32 ` [RFC PATCH 1/3] mmc: sdhci: Add platform_dumpregs callback support to sdhci_ops Ritesh Harjani
2017-01-13 22:21 ` Jeremy McNicoll
2017-01-16 2:15 ` Ritesh Harjani
2017-01-16 5:21 ` Jeremy McNicoll
2016-12-30 11:32 ` [RFC PATCH 2/3] mmc: sdhci-msm: Implement platform_dumpregs callback in sdhci-msm Ritesh Harjani
2017-01-13 22:31 ` Jeremy McNicoll [this message]
2017-01-16 2:21 ` Ritesh Harjani
2017-01-16 5:20 ` Jeremy McNicoll
2016-12-30 11:32 ` [RFC PATCH 3/3] mmc: sdhci: Add more debug info in case of data error Ritesh Harjani
2017-01-17 1:09 ` [RFC PATCH 0/3] mmc: sdhci: sdhci-msm: Add more debug logs Jeremy McNicoll
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=20170113223117.GB22862@mini-rhel.redhat.com \
--to=jmcnicol@redhat.com \
--cc=adrian.hunter@intel.com \
--cc=asutoshd@codeaurora.org \
--cc=georgi.djakov@linaro.org \
--cc=jeremymc@redhat.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=pramod.gurav@linaro.org \
--cc=riteshh@codeaurora.org \
--cc=shawn.lin@rock-chips.com \
--cc=stummala@codeaurora.org \
--cc=subhashj@codeaurora.org \
--cc=ulf.hansson@linaro.org \
--cc=venkatg@codeaurora.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