u-boot.lists.denx.de archive mirror
 help / color / mirror / Atom feed
From: Hector Palacios <hector.palacios@digi.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Are mmc open/close subcommands needed?
Date: Thu, 2 Jan 2014 17:53:00 +0100	[thread overview]
Message-ID: <52C5996C.4020803@digi.com> (raw)

Hi,

I saw commit 2a91c9134675140853577b565210458b5774e6cf that introduces mmc subcommands 
'open' and 'close' to access eMMC boot partitions and was wondering if they are really 
needed. Can't the same be achieved with already existing 'mmc dev [dev] [part]' command?

mmc open <dev> <boot_partition>
  is the same as
mmc dev <dev> <part>
  where <part> is the boot partition

mmc close <dev> <boot_partition>
  is the same as
mmc dev <dev> 0
  as a 0 will switch to partition 0 (user data).

Best regards,
--
Hector Palacios

             reply	other threads:[~2014-01-02 16:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-02 16:53 Hector Palacios [this message]
2014-01-02 23:36 ` [U-Boot] Are mmc open/close subcommands needed? Marek Vasut
2014-01-03 17:35   ` Otavio Salvador
2014-01-07  7:47     ` Hector Palacios
2014-01-09  8:45       ` Jaehoon Chung

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=52C5996C.4020803@digi.com \
    --to=hector.palacios@digi.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;
as well as URLs for NNTP newsgroup(s).