On Tue, Aug 16, 2016 at 4:41 AM, Ritesh Harjani <riteshh@xxxxxxxxxxxxxx> wrote:
[..]
> diff --git a/drivers/mmc/host/sdhci-msm.c b/drivers/mmc/host/sdhci-msm.c
[..]
> @@ -316,6 +325,15 @@ static int msm_init_cm_dll(struct sdhci_host *host)
> writel_relaxed((readl_relaxed(host->ioaddr + CORE_VENDOR_SPEC)
> & ~CORE_CLK_PWRSAVE), host->ioaddr + CORE_VENDOR_SPEC);
>
> + if (msm_host->use_updated_dll_reset) {
> + writel_relaxed((readl_relaxed(host->ioaddr + CORE_DLL_CONFIG)
> + & ~CORE_CK_OUT_EN),
> + host->ioaddr + CORE_DLL_CONFIG);
> + writel_relaxed((readl_relaxed(host->ioaddr + CORE_DLL_CONFIG_2)
> + | CORE_DLL_CLOCK_DISABLE),
> + host->ioaddr + CORE_DLL_CONFIG_2);
I know that this follows the pattern of this function, but it's
terrible to read. Please unroll each one of these to:
val = readl();
val &= ~mask;
val |= new-bits;
writel(val);
To not mix the style I would suggest that you inject a patch in your
series before this one that unrolls the exiting code and then add
this.
> + }
> +
> /* Write 1 to DLL_RST bit of DLL_CONFIG register */
> writel_relaxed((readl_relaxed(host->ioaddr + CORE_DLL_CONFIG)
> | CORE_DLL_RST), host->ioaddr + CORE_DLL_CONFIG);
> @@ -325,6 +343,22 @@ static int msm_init_cm_dll(struct sdhci_host *host)
> | CORE_DLL_PDN), host->ioaddr + CORE_DLL_CONFIG);
> msm_cm_dll_set_freq(host);
>
> + if (msm_host->use_updated_dll_reset) {
> + u32 mclk_freq = 0;
> +
> + if ((readl_relaxed(host->ioaddr + CORE_DLL_CONFIG_2)
> + & CORE_FLL_CYCLE_CNT))
> + mclk_freq = (u32) ((host->clock / TCXO_FREQ) * 8);
> + else
> + mclk_freq = (u32) ((host->clock / TCXO_FREQ) * 4);
> +
> + writel_relaxed(((readl_relaxed(host->ioaddr + CORE_DLL_CONFIG_2)
> + & ~(0xFF << 10)) | (mclk_freq << 10)),
> + host->ioaddr + CORE_DLL_CONFIG_2);
Dito
> + /* wait for 5us before enabling DLL clock */
> + udelay(5);
> + }
> +
> /* Write 0 to DLL_RST bit of DLL_CONFIG register */
> writel_relaxed((readl_relaxed(host->ioaddr + CORE_DLL_CONFIG)
> & ~CORE_DLL_RST), host->ioaddr + CORE_DLL_CONFIG);
> @@ -333,6 +367,14 @@ static int msm_init_cm_dll(struct sdhci_host *host)
> writel_relaxed((readl_relaxed(host->ioaddr + CORE_DLL_CONFIG)
> & ~CORE_DLL_PDN), host->ioaddr + CORE_DLL_CONFIG);
>
> + if (msm_host->use_updated_dll_reset) {
> + msm_cm_dll_set_freq(host);
> + /* Enable the DLL clock */
> + writel_relaxed((readl_relaxed(host->ioaddr + CORE_DLL_CONFIG_2)
> + & ~CORE_DLL_CLOCK_DISABLE),
> + host->ioaddr + CORE_DLL_CONFIG_2);
Dito
> + }
> +
> /* Set DLL_EN bit to 1. */
> writel_relaxed((readl_relaxed(host->ioaddr + CORE_DLL_CONFIG)
> | CORE_DLL_EN), host->ioaddr + CORE_DLL_CONFIG);
> @@ -631,6 +673,9 @@ static int sdhci_msm_probe(struct platform_device *pdev)
> dev_dbg(&pdev->dev, "MCI Version: 0x%08x, major: 0x%04x, minor: 0x%02x\n",
> core_version, core_major, core_minor);
>
> + if ((core_major == 1) && (core_minor >= 0x42))
> + msm_host->use_updated_dll_reset = true;
> +
Is it possible to come up with a better name than the "updated DLL
sequence", just in case there are future updates to this sequence.
Regards,
Bjorn
--
To unsubscribe from this list: send the line "unsubscribe linux-mmc" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
