public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Tom Rini <trini@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] eMMC boot partition booting and SMDK5250 support
Date: Tue, 28 Jan 2014 14:31:17 -0500	[thread overview]
Message-ID: <20140128193117.GL3277@bill-the-cat> (raw)
In-Reply-To: <20140128172502.GJ3277@bill-the-cat>

On Tue, Jan 28, 2014 at 12:25:02PM -0500, Tom Rini wrote:
> Hey guys,
> 
> I've posted a patch to support the eMMC boot partitions found on the TI
> DRA7xx EVM the other day, and I've been looking at what exactly happens
> with the 'mmc open ...' and 'mmc close ...' commands the
> CONFIG_SUPPORT_EMMC_BOOT enables.  I've got a few questions about how
> exactly the support works on the SMDK5250 and what your platform
> requirements are, so we can re-work the code to be a bit more generic.
> 
> Why do we have it as "open" and "close" ?  Is this because it's a
> version 4.2[1] style device?  I'm working with 4.3-compatible (it's
> actually 4.41, but same method just larger partitions) one and that can
> be done with setting EXT_CSD[179] (BOOT_CONFIG / Boot configuration) _and_
> EXT_CSD[177] to a specific and different value than we've hard-coded
> now.
> 
> I would like to change things to be:
> "mmc open <device>" - Note required for eMMC 4.2 boot method.
> "mmc close <device>" - Same
> "mmc bootpart <device> <partition>" - Used for eMMC 4.3 and later boot
> sequence option 1/2
> "mmc bootbus <device> <value>" - Note used in all boot sequences
> 
> This would make the SMDK5250 sequence be (based on how I think it works
> today):
> mmc dev ...
> mmc open
> mmc write ...
> mmc bootpart ...
> mmc bootbus ...
> mmc close
> 
> And the DRA7xx sequence be:
> mmc dev ...
> mmc write ...
> mmc bootpart ...
> mmc bootbus ...

Oh!  And I forgot the current 'bootpart' which appears to be a resize
operation would become 'bootpart-resize'.

-- 
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20140128/555abd66/attachment.pgp>

  reply	other threads:[~2014-01-28 19:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-28 17:25 [U-Boot] eMMC boot partition booting and SMDK5250 support Tom Rini
2014-01-28 19:31 ` Tom Rini [this message]
2014-01-29  0:48   ` Minkyu Kang
2014-01-28 21:56 ` Tom Rini

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=20140128193117.GL3277@bill-the-cat \
    --to=trini@ti.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