public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: maxime.ripard@bootlin.com (Maxime Ripard)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] mmc: sunxi: Use new timing mode for A64 eMMC controller
Date: Tue, 17 Jul 2018 17:15:58 +0200	[thread overview]
Message-ID: <20180717151558.wn7v33whtljqt53w@flea> (raw)
In-Reply-To: <CAGb2v65rE2nQbyeiSPAyTzw-n-EQsUwQABx3nrvXTu4JogFPBQ@mail.gmail.com>

On Thu, Jul 12, 2018 at 06:17:23PM +0800, Chen-Yu Tsai wrote:
> On Thu, Jul 12, 2018 at 3:19 PM, Maxime Ripard
> <maxime.ripard@bootlin.com> wrote:
> > Hi,
> >
> > On Thu, Jul 12, 2018 at 11:02:25AM +0800, Chen-Yu Tsai wrote:
> >> The eMMC controller is also a new timing mode controller, but it doesn't
> >> have the timing mode switch. It does however have signal delay and
> >> calibration controls, typical of Allwinner MMC controllers that support
> >> the new timing mode.
> >>
> >> Enable the new timing mode setting for the A64 eMMC controller. This
> >> also enables MMC HS-DDR modes, which gives higher throughput for eMMC
> >> chips that support it, and can deliver such throughput.
> >>
> >> Signed-off-by: Chen-Yu Tsai <wens@csie.org>
> >
> > That doesn't look right. The datasheet explicitly mentions that this
> > bit doesn't apply to the eMMC controller, and the BSP is doing the same:
> > https://github.com/longsleep/linux-pine64/blob/lichee-dev-v3.10.65/drivers/mmc/host/sunxi-mmc-sun50iw1p1-1.c
> >
> > vs
> > https://github.com/longsleep/linux-pine64/blob/lichee-dev-v3.10.65/drivers/mmc/host/sunxi-mmc-sun50iw1p1-2.c
> 
> You mean the bit in SDXC_REG_SD_NTSR? Yes I know that doesn't exist
> for the eMMC controller. I mentioned this in the commit message. It
> doesn't exist, and writes to it become a no-op.
> 
> Would a comment, or comments, help with making this clear?

Ah right. Maybe we should move the calibration under can_calibrate
though, or create another boolean for this?

Putting it under has_new_timings while the SoC doesn't use it looks
very confusing.

Maxime

-- 
Maxime Ripard, Bootlin (formerly Free Electrons)
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.infradead.org/pipermail/linux-arm-kernel/attachments/20180717/b9e9ebd4/attachment.sig>

  reply	other threads:[~2018-07-17 15:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-12  3:02 [PATCH] mmc: sunxi: Use new timing mode for A64 eMMC controller Chen-Yu Tsai
2018-07-12  7:19 ` Maxime Ripard
2018-07-12 10:17   ` Chen-Yu Tsai
2018-07-17 15:15     ` Maxime Ripard [this message]
2018-07-17 15:43       ` Chen-Yu Tsai
2018-07-18 15:22         ` Maxime Ripard
2018-07-30  9:27           ` Chen-Yu Tsai
2018-07-31 14:19             ` 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=20180717151558.wn7v33whtljqt53w@flea \
    --to=maxime.ripard@bootlin.com \
    --cc=linux-arm-kernel@lists.infradead.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