public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Maxime Ripard <maxime.ripard@bootlin.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/5] mmc: sunxi: add support for automatic delay calibration
Date: Mon, 1 Oct 2018 12:01:56 +0200	[thread overview]
Message-ID: <20181001100156.mt4copbpdxhaiwdn@flea> (raw)
In-Reply-To: <20181001094837.0332d966@donnerap.Emea.Arm.com>

On Mon, Oct 01, 2018 at 09:48:37AM +0100, Andre Przywara wrote:
> On Mon, 1 Oct 2018 10:09:55 +0200
> Maxime Ripard <maxime.ripard@bootlin.com> wrote:
> 
> > On Sun, Sep 30, 2018 at 04:16:36PM +0100, André Przywara wrote:
> > > On 9/30/18 12:45 AM, Vagrant Cascadian wrote:  
> > > > From: Vasily Khoruzhick <anarsoul@gmail.com>
> > > > 
> > > > A64 supports automatic delay calibration and Linux driver uses it
> > > > instead of hardcoded delays. Add support for it to u-boot
> > > > driver.  
> > > 
> > > So technically that should be derived from the node's compatible
> > > string, like we do in Linux. But I see that we are not there yet in
> > > U-Boot. Meanwhile I don't think you should introduce a new Kconfig
> > > option, you could keep the hacky U-Boot style and just add an
> > > #if defined(CONFIG_MACH_SUN50I) || defined(CONFIG_MACH_SUN50I_H6)
> > > to the two places instead.  
> > 
> > IIRC, the calibration is only needed for the eMMC though, so we'd need
> > to check that against the MMC number too.
> 
> Is that so? I was looking at the Linux driver, and that one sets
> can_calibrate for both the "normal" and eMMC A64 compatible strings.
> Isn't the difference between the two the new timing mode, which the
> eMMC doesn't have? This looks to be covered in U-Boot, though in a
> similar hacky way.

You're right, sorry for the noise...

Maxime

-- 
Maxime Ripard, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20181001/22d46f2a/attachment.sig>

  reply	other threads:[~2018-10-01 10:01 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-29 23:45 [U-Boot] [PATCH 0/5] Vagrant Cascadian
2018-09-29 23:45 ` [U-Boot] [PATCH 1/5] mmc: sunxi: add support for automatic delay calibration Vagrant Cascadian
2018-09-30 15:16   ` André Przywara
2018-10-01  8:09     ` Maxime Ripard
2018-10-01  8:48       ` Andre Przywara
2018-10-01 10:01         ` Maxime Ripard [this message]
2018-09-29 23:45 ` [U-Boot] [PATCH 2/5] dm: video: bridge: don't fail to activate bridge if sleep gpio is missing Vagrant Cascadian
2018-09-30  6:02   ` Vasily Khoruzhick
2018-09-30 17:48     ` Vagrant Cascadian
2018-09-30 20:15       ` Vasily Khoruzhick
2018-09-30 22:13   ` André Przywara
2018-09-29 23:45 ` [U-Boot] [PATCH 3/5] video: anx6345: don't fail if there's no sleep or reset GPIOs Vagrant Cascadian
2018-09-30 22:26   ` André Przywara
2018-09-29 23:45 ` [U-Boot] [PATCH 4/5] sun50i: a64: add support for R_I2C controller Vagrant Cascadian
2018-10-01  8:11   ` Maxime Ripard
2018-09-29 23:45 ` [U-Boot] [PATCH 5/5] sunxi: add support for Pinebook Vagrant Cascadian
2018-10-01  8:17   ` Maxime Ripard
2018-10-01  9:37     ` Icenowy Zheng
2018-10-01 10:00       ` Maxime Ripard

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=20181001100156.mt4copbpdxhaiwdn@flea \
    --to=maxime.ripard@bootlin.com \
    --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