From: Sowjanya Komatineni <skomatineni@nvidia.com> To: adrian.hunter@intel.com, ulf.hansson@linaro.org, robh+dt@kernel.org, mark.rutland@arm.com, riteshh@codeaurora.org Cc: thierry.reding@gmail.com, jonathanh@nvidia.com, anrao@nvidia.com, linux-tegra@vger.kernel.org, linux-kernel@vger.kernel.org, linux-mmc@vger.kernel.org, devicetree@vger.kernel.org, Sowjanya Komatineni <skomatineni@nvidia.com> Subject: [PATCH V1 08/11] mmc: tegra: add Tegra186 WAR for CQE Date: Fri, 1 Mar 2019 21:20:22 -0800 [thread overview] Message-ID: <1551504025-3541-8-git-send-email-skomatineni@nvidia.com> (raw) In-Reply-To: <1551504025-3541-1-git-send-email-skomatineni@nvidia.com> Tegra186 design has a known bug where CQE does not generated task complete interrupt for data transfer tasks issued after DCMD task with R1b response type and results in timeout. SW WAR is to set CMD_TIMING to 1 in task descriptor for DCMDs with R1b response type. This bug and SW WAR is applicable only for Tegra186 and not for Tegra194. This patch adds this WAR to Tegra186. Signed-off-by: Sowjanya Komatineni <skomatineni@nvidia.com> --- drivers/mmc/host/sdhci-tegra.c | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/drivers/mmc/host/sdhci-tegra.c b/drivers/mmc/host/sdhci-tegra.c index 2086e0eced88..2b63626dc2fa 100644 --- a/drivers/mmc/host/sdhci-tegra.c +++ b/drivers/mmc/host/sdhci-tegra.c @@ -116,6 +116,7 @@ struct sdhci_tegra_soc_data { u32 nvquirks; u8 min_tap_delay; u8 max_tap_delay; + u32 cqequirks; }; /* Magic pull up and pull down pad calibration offsets */ @@ -1354,6 +1355,7 @@ static const struct sdhci_tegra_soc_data soc_data_tegra186 = { NVQUIRK_ENABLE_SDR104, .min_tap_delay = 84, .max_tap_delay = 136, + .cqequirks = CQHCI_QUIRK_CMD_TIMING_R1B_DCMD, }; static const struct sdhci_tegra_soc_data soc_data_tegra194 = { @@ -1383,6 +1385,7 @@ static int sdhci_tegra_add_host(struct sdhci_host *host) { struct sdhci_pltfm_host *pltfm_host = sdhci_priv(host); struct sdhci_tegra *tegra_host = sdhci_pltfm_priv(pltfm_host); + const struct sdhci_tegra_soc_data *soc_data = tegra_host->soc_data; struct cqhci_host *cq_host; bool dma64; int ret; @@ -1407,6 +1410,7 @@ static int sdhci_tegra_add_host(struct sdhci_host *host) cq_host->mmio = host->ioaddr + SDHCI_TEGRA_CQE_BASE_ADDR; cq_host->ops = &sdhci_tegra_cqhci_ops; + cq_host->quirks = soc_data->cqequirks; dma64 = host->flags & SDHCI_USE_64_BIT_DMA; if (dma64) -- 2.7.4
WARNING: multiple messages have this Message-ID (diff)
From: Sowjanya Komatineni <skomatineni@nvidia.com> To: <adrian.hunter@intel.com>, <ulf.hansson@linaro.org>, <robh+dt@kernel.org>, <mark.rutland@arm.com>, <riteshh@codeaurora.org> Cc: <thierry.reding@gmail.com>, <jonathanh@nvidia.com>, <anrao@nvidia.com>, <linux-tegra@vger.kernel.org>, <linux-kernel@vger.kernel.org>, <linux-mmc@vger.kernel.org>, <devicetree@vger.kernel.org>, Sowjanya Komatineni <skomatineni@nvidia.com> Subject: [PATCH V1 08/11] mmc: tegra: add Tegra186 WAR for CQE Date: Fri, 1 Mar 2019 21:20:22 -0800 [thread overview] Message-ID: <1551504025-3541-8-git-send-email-skomatineni@nvidia.com> (raw) In-Reply-To: <1551504025-3541-1-git-send-email-skomatineni@nvidia.com> Tegra186 design has a known bug where CQE does not generated task complete interrupt for data transfer tasks issued after DCMD task with R1b response type and results in timeout. SW WAR is to set CMD_TIMING to 1 in task descriptor for DCMDs with R1b response type. This bug and SW WAR is applicable only for Tegra186 and not for Tegra194. This patch adds this WAR to Tegra186. Signed-off-by: Sowjanya Komatineni <skomatineni@nvidia.com> --- drivers/mmc/host/sdhci-tegra.c | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/drivers/mmc/host/sdhci-tegra.c b/drivers/mmc/host/sdhci-tegra.c index 2086e0eced88..2b63626dc2fa 100644 --- a/drivers/mmc/host/sdhci-tegra.c +++ b/drivers/mmc/host/sdhci-tegra.c @@ -116,6 +116,7 @@ struct sdhci_tegra_soc_data { u32 nvquirks; u8 min_tap_delay; u8 max_tap_delay; + u32 cqequirks; }; /* Magic pull up and pull down pad calibration offsets */ @@ -1354,6 +1355,7 @@ static const struct sdhci_tegra_soc_data soc_data_tegra186 = { NVQUIRK_ENABLE_SDR104, .min_tap_delay = 84, .max_tap_delay = 136, + .cqequirks = CQHCI_QUIRK_CMD_TIMING_R1B_DCMD, }; static const struct sdhci_tegra_soc_data soc_data_tegra194 = { @@ -1383,6 +1385,7 @@ static int sdhci_tegra_add_host(struct sdhci_host *host) { struct sdhci_pltfm_host *pltfm_host = sdhci_priv(host); struct sdhci_tegra *tegra_host = sdhci_pltfm_priv(pltfm_host); + const struct sdhci_tegra_soc_data *soc_data = tegra_host->soc_data; struct cqhci_host *cq_host; bool dma64; int ret; @@ -1407,6 +1410,7 @@ static int sdhci_tegra_add_host(struct sdhci_host *host) cq_host->mmio = host->ioaddr + SDHCI_TEGRA_CQE_BASE_ADDR; cq_host->ops = &sdhci_tegra_cqhci_ops; + cq_host->quirks = soc_data->cqequirks; dma64 = host->flags & SDHCI_USE_64_BIT_DMA; if (dma64) -- 2.7.4
next prev parent reply other threads:[~2019-03-02 5:20 UTC|newest] Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-03-02 5:20 [PATCH V1 01/11] mmc: tegra: fix ddr signaling for non-ddr modes Sowjanya Komatineni 2019-03-02 5:20 ` Sowjanya Komatineni 2019-03-02 5:20 ` [PATCH V1 02/11] mmc: sdhci: allow host to specify maximum tuning loops Sowjanya Komatineni 2019-03-02 5:20 ` Sowjanya Komatineni 2019-03-08 11:50 ` Adrian Hunter 2019-03-02 5:20 ` [PATCH V1 03/11] mmc: sdhci: add support for post tuning process Sowjanya Komatineni 2019-03-02 5:20 ` Sowjanya Komatineni 2019-03-08 11:55 ` Adrian Hunter 2019-03-02 5:20 ` [PATCH V1 04/11] mmc: tegra: update hw " Sowjanya Komatineni 2019-03-02 5:20 ` Sowjanya Komatineni 2019-03-08 12:07 ` Adrian Hunter 2019-03-02 5:20 ` [PATCH V1 05/11] dt-bindings: mmc: tegra: document Tegra194 compatible string Sowjanya Komatineni 2019-03-02 5:20 ` Sowjanya Komatineni 2019-03-02 5:20 ` [PATCH V1 06/11] arm64: tegra: fix default tap and trim values Sowjanya Komatineni 2019-03-02 5:20 ` Sowjanya Komatineni 2019-03-02 5:20 ` [PATCH V1 07/11] mmc: cqhci: add quirk for setting DCMD CMD_TIMING Sowjanya Komatineni 2019-03-02 5:20 ` Sowjanya Komatineni 2019-03-06 13:00 ` Adrian Hunter 2019-03-07 2:43 ` Ritesh Harjani 2019-03-07 18:16 ` Sowjanya Komatineni 2019-03-08 12:29 ` Adrian Hunter 2019-03-09 5:14 ` Sowjanya Komatineni 2019-03-13 2:31 ` Ritesh Harjani 2019-03-13 9:56 ` Hunter, Adrian 2019-03-13 15:47 ` Sowjanya Komatineni 2019-03-02 5:20 ` Sowjanya Komatineni [this message] 2019-03-02 5:20 ` [PATCH V1 08/11] mmc: tegra: add Tegra186 WAR for CQE Sowjanya Komatineni 2019-03-02 5:20 ` [PATCH V1 09/11] mmc: cqhci: add CQHCI_SSC1 register CBC field mask Sowjanya Komatineni 2019-03-02 5:20 ` Sowjanya Komatineni 2019-03-08 12:14 ` Adrian Hunter 2019-03-02 5:20 ` [PATCH V1 10/11] mmc: tegra: fix CQE resume sequence Sowjanya Komatineni 2019-03-02 5:20 ` Sowjanya Komatineni 2019-03-08 12:59 ` Adrian Hunter 2019-03-02 5:20 ` [PATCH V1 11/11] arm64: tegra: enable command queue for tegra186 sdmmc4 Sowjanya Komatineni 2019-03-02 5:20 ` Sowjanya Komatineni 2019-03-07 21:31 ` [PATCH V1 01/11] mmc: tegra: fix ddr signaling for non-ddr modes Jon Hunter 2019-03-07 21:31 ` Jon Hunter 2019-03-08 11:44 ` Adrian Hunter
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=1551504025-3541-8-git-send-email-skomatineni@nvidia.com \ --to=skomatineni@nvidia.com \ --cc=adrian.hunter@intel.com \ --cc=anrao@nvidia.com \ --cc=devicetree@vger.kernel.org \ --cc=jonathanh@nvidia.com \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-mmc@vger.kernel.org \ --cc=linux-tegra@vger.kernel.org \ --cc=mark.rutland@arm.com \ --cc=riteshh@codeaurora.org \ --cc=robh+dt@kernel.org \ --cc=thierry.reding@gmail.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: 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.