From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v4] mmc: socfpga_dw_mmc: Enable calibration for drvsel and smplsel
Date: Wed, 2 Dec 2015 16:43:33 +0100 [thread overview]
Message-ID: <201512021643.33996.marex@denx.de> (raw)
In-Reply-To: <1449069019.2091.1.camel@altera.com>
On Wednesday, December 02, 2015 at 04:10:19 PM, Chin Liang See wrote:
> On Wed, 2015-12-02 at 15:39 +0100, Marek Vasut wrote:
> > On Wednesday, December 02, 2015 at 06:52:17 AM, Chin Liang See wrote:
> >
> > [...]
> >
> > > > OK, this is bad. Originally, if we didn't specify these in the
> > > > DT, we
> > > > would
> > > > use the default values of 0x3 and 0x0 , but now we do the
> > > > calibration. I wonder,
> > > > do we care about DT ABI compatibility on the U-Boot level or not
> > > > ?
> > >
> > > If the compatibility failed, it will still invoke the calibration
> > > to
> > > get the correct value. Just that its in the cost of boot time.
> >
> > Hopefully the calibration does it's job then.
> >
> > > At same time, I am rethinking another email thread on suggesting to
> > > put
> > > this into common dw_mmc code. Here are my proposal
> >
> > Having this in common code would make sense.
> >
> > > 1. Put back the correct default value for DT ABI compatiblity
> > > 2. Adding a node to enable calibration. If node not exist,
> > > calibration
> > > will disabled as default.
> >
> > But "enable calibration" is not really a hardware property, so it
> > shouldn't
> > be in the DT. The DT is purely a hardware description and only the
> > smplsel
> > and drvsel fit into this, some "enable-calibration" does not.
>
> Sound reasonable. In this case, I can put this into KConfig where user
> can configure this easily through menuconfig.
OK, this would be much better.
Best regards,
Marek Vasut
next prev parent reply other threads:[~2015-12-02 15:43 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-27 7:22 [U-Boot] [PATCH v4] mmc: socfpga_dw_mmc: Enable calibration for drvsel and smplsel Chin Liang See
2015-11-27 18:36 ` Simon Glass
2015-11-27 19:41 ` Marek Vasut
2015-11-29 1:59 ` Simon Glass
2015-11-29 2:05 ` Marek Vasut
2015-11-29 20:19 ` Simon Glass
2015-11-29 20:41 ` Marek Vasut
2015-11-29 13:39 ` Marek Vasut
2015-12-01 15:32 ` Chin Liang See
2015-12-01 15:38 ` Marek Vasut
2015-12-02 5:52 ` Chin Liang See
2015-12-02 14:39 ` Marek Vasut
2015-12-02 15:10 ` Chin Liang See
2015-12-02 15:43 ` Marek Vasut [this message]
2015-12-03 18:17 ` Pavel Machek
2016-01-27 0:01 ` Trent Piepho
2016-01-27 13:13 ` Chin Liang See
2016-01-27 18:58 ` Trent Piepho
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=201512021643.33996.marex@denx.de \
--to=marex@denx.de \
--cc=u-boot@lists.denx.de \
/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