linux-kernel - RE: Pinmuxing and SDHC speeds on sdhci-esdhc-imx

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:   Wed, 10 Oct 2018 03:28:54 +0000
From:   Bough Chen <haibo.chen@....com>
To:     Adam Ford <aford173@...il.com>,
        "linux-mmc@...r.kernel.org" <linux-mmc@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        "A.s. Dong" <aisheng.dong@....com>,
        "haibo.chen@...escale.com" <haibo.chen@...escale.com>,
        Fabio Estevam <fabio.estevam@....com>
Subject: RE: Pinmuxing and SDHC speeds on sdhci-esdhc-imx

Hi Adam

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

Best Regards
Bough Chen

> -----Original Message-----
> From: linux-mmc-owner@...r.kernel.org
> [mailto:linux-mmc-owner@...r.kernel.org] On Behalf Of Adam Ford
> Sent: 2018年10月9日 21:38
> To: linux-mmc@...r.kernel.org; Linux Kernel Mailing List
> <linux-kernel@...r.kernel.org>; A.s. Dong <aisheng.dong@....com>;
> haibo.chen@...escale.com; Fabio Estevam <fabio.estevam@....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