lkml.org 
[lkml]   [2018]   [Oct]   [10]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRE: Pinmuxing and SDHC speeds on sdhci-esdhc-imx
Date
Hi Adam

Yes, MMC_DDR52 can use pins_100mhz. You can do that, thanks!

Best Regards
Bough Chen

> -----Original Message-----
> From: linux-mmc-owner@vger.kernel.org
> [mailto:linux-mmc-owner@vger.kernel.org] On Behalf Of Adam Ford
> Sent: 2018年10月9日 21:38
> To: linux-mmc@vger.kernel.org; Linux Kernel Mailing List
> <linux-kernel@vger.kernel.org>; A.s. Dong <aisheng.dong@nxp.com>;
> haibo.chen@freescale.com; Fabio Estevam <fabio.estevam@nxp.com>
> Subject: Pinmuxing and SDHC speeds on sdhci-esdhc-imx
>
> I have a question regarding the pinstate and the corresponding uhs_signaling.
>
> The uhs_signaling shows a variety of timing options,
>
> MMC_TIMING_UHS_SDR12, MMC_TIMING_UHS_SDR25:,
> MMC_TIMING_UHS_SDR50, MMC_TIMING_UHS_SDR104,
> MMC_TIMING_MMC_HS200, MMC_TIMING_UHS_DDR50,
> MMC_TIMING_MMC_DDR52, MMC_TIMING_MMC_HS400, and
> MMC_TIMING_LEGACY
>
> However the esdhc_change_pinstate function only lists
> MMC_TIMING_UHS_SDR50, MMC_TIMING_UHS_DDR50,
> MMC_TIMING_UHS_SDR104, MMC_TIMING_MMC_HS200, and
> MMC_TIMING_MMC_HS40, and a defaut.
>
> From what I can tell, this means that MMC_TIMING_MMC_DDR52 uses the
> default pinmux. I am wondering if it should use pins_100mhz. We have an
> eMMC part that we want to operate at this point and it seems like it missing.
> If so, I can submit a patch.
>
> It also seems like that SDR12, SDR25 use the default. I assume this is OK.
>
> adam
\
 
 \ /
  Last update: 2018-10-10 05:31    [W:0.113 / U:1.064 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site