From: Bough Chen <haibo.chen@nxp.com>
To: Adam Ford <aford173@gmail.com>,
"linux-mmc@vger.kernel.org" <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" <haibo.chen@freescale.com>,
Fabio Estevam <fabio.estevam@nxp.com>
Subject: RE: Pinmuxing and SDHC speeds on sdhci-esdhc-imx
Date: Wed, 10 Oct 2018 03:28:54 +0000 [thread overview]
Message-ID: <VI1PR04MB5040E64721C3B1EFBFC9A42C90E00@VI1PR04MB5040.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <CAHCN7xJnqbzyx=wFw4XY+NWRP_Y4RTVjeeyU3wSAsGtSUyG9Bw@mail.gmail.com>
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
prev parent reply other threads:[~2018-10-10 3:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-09 13:38 Pinmuxing and SDHC speeds on sdhci-esdhc-imx Adam Ford
2018-10-10 3:28 ` Bough Chen [this message]
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=VI1PR04MB5040E64721C3B1EFBFC9A42C90E00@VI1PR04MB5040.eurprd04.prod.outlook.com \
--to=haibo.chen@nxp.com \
--cc=aford173@gmail.com \
--cc=aisheng.dong@nxp.com \
--cc=fabio.estevam@nxp.com \
--cc=haibo.chen@freescale.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).