From: Aisheng Dong <aisheng.dong@nxp.com>
To: BOUGH CHEN <haibo.chen@nxp.com>, Stefan Agner <stefan@agner.ch>
Cc: Christina Quast <cquast@hanoverdisplays.com>,
"festevam@gmail.com" <festevam@gmail.com>,
"shawnguo@kernel.org" <shawnguo@kernel.org>,
"kernel@pengutronix.de" <kernel@pengutronix.de>,
"linus.walleij@linaro.org" <linus.walleij@linaro.org>,
"robh+dt@kernel.org" <robh+dt@kernel.org>,
"mark.rutland@arm.com" <mark.rutland@arm.com>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH] Document: dt: binding: imx: Fix PAD_CTL_DSE_X*
Date: Wed, 6 Mar 2019 13:36:42 +0000 [thread overview]
Message-ID: <AM0PR04MB42118ED0DB09896BB860AF7C80730@AM0PR04MB4211.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <VI1PR04MB504036C9FA56673680279BB190730@VI1PR04MB5040.eurprd04.prod.outlook.com>
[...]
> > > Btw, I saw that imx7d-sdb.dts (and probably other i.MX 7 boards too)
> > > use three different settings for usdhc pinctrl: 0x59, 0x5a and 0x5b
> > > (for default, 100MHz and 200MHz respectively). One would expect that
> > > higher frequency use higher driver strength (and this is the case for i.MX 6).
> > > But with this new/corrected pad values this means we use x4, x2 and
> > > x6 for default, 100MHz and 200MHz respectively. This hardly seems right..?
> > > Probably needs fixing too?
> > >
> >
> > Yes, that's true.
> > Especially 100Mhz setting should be updated.
> >
> > Haibo,
> > Can you please help double check if X2 for 50Mhz and X4 for 100Mhz can
> > work stably on MX7D SDB?
> > If yes, we'd like to update the pad setting according to new RM version.
> >
>
> X2 for high speed and x4 for ddr50/ddr52 can work stable on MX7D SDB.
> I think all the 7D related dts need to fix this. Not sure whether 7S need this fix,
> can you confirm?
>
Yes, please make a patch to test board maintainer.
Regards
Dong Aisheng
> Best Regards
> Haibo Chen
prev parent reply other threads:[~2019-03-06 13:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-22 17:00 Christina Quast
2019-02-26 12:21 ` Aisheng Dong
2019-02-26 13:21 ` Stefan Agner
2019-03-05 3:34 ` Aisheng Dong
2019-03-06 10:11 ` BOUGH CHEN
2019-03-06 13:36 ` Aisheng Dong [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=AM0PR04MB42118ED0DB09896BB860AF7C80730@AM0PR04MB4211.eurprd04.prod.outlook.com \
--to=aisheng.dong@nxp.com \
--cc=cquast@hanoverdisplays.com \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=haibo.chen@nxp.com \
--cc=kernel@pengutronix.de \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=shawnguo@kernel.org \
--cc=stefan@agner.ch \
/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
all inboxes | Powered by JetHome®