All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Warren <swarren@wwwdotorg.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] mmc: add wrappers for MMC block_{read, write, erase}
Date: Thu, 29 May 2014 12:51:34 -0600	[thread overview]
Message-ID: <538781B6.90703@wwwdotorg.org> (raw)
In-Reply-To: <5387753E.9060106@broadcom.com>

On 05/29/2014 11:58 AM, Steve Rae wrote:
> Hi, Stephen
> 
> On 14-05-29 09:25 AM, Stephen Warren wrote:
>> On 05/28/2014 04:15 PM, Steve Rae wrote:
>>> Each wrapper function:
>>> - switches to the specified physical partition, then
>>> - performs the original function, and then
>>> - switches back to the original physical partition
>>> where the physical partition (aka HW partition) is
>>>    0=User, 1=Boot1, 2=Boot2, etc.
>>
>> This feels wrong; why wouldn't mmc_get_dev() return a block_dev_desc_t
>> containing block_read/block_write functions that do the HW partition
>> switching. That way, this is all completely hidden, and all client code
>> only knows about block devices, rather than having to know about
>> MMC-specific mmc_block_read/write/erase_hwpart() functions.
>>
> This goes back to the initial discussion on this mailing list (which was
> never resolved):
>   http://lists.denx.de/pipermail/u-boot/2014-April/178171.html
> This issue is that the three callback functions defined in
> 'block_desc_t' do not accept the "partition number" as an argument.
> It was suggested that we could overwrite those functions; but the
> "partition number" still needs to be passed in by:
> (1) overloading the "int dev_num" argument, or
> (2) adding another argument to the callback functions
> I assumed that neither of these was acceptable, so I have proposed these
> wrappers...

Can't the data simply be stored in the block_desc_t itself?

  reply	other threads:[~2014-05-29 18:51 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-28 22:15 [U-Boot] [PATCH] mmc: add wrappers for MMC block_{read, write, erase} Steve Rae
2014-05-29  5:47 ` Jaehoon Chung
2014-05-29  7:03 ` Jaehoon Chung
2014-05-29 17:24   ` Steve Rae
2014-05-29 16:25 ` Stephen Warren
2014-05-29 17:58   ` Steve Rae
2014-05-29 18:51     ` Stephen Warren [this message]
2014-05-29 19:44       ` Steve Rae
2014-05-29 20:30         ` Stephen Warren
2014-05-29 22:03           ` Steve Rae
2014-05-30 15:58             ` Stephen Warren
2014-05-30 16:56               ` Steve Rae
2014-05-30 17:07                 ` Stephen Warren
2014-05-30 18:39                   ` Steve Rae
2014-06-02  6:42 ` Pantelis Antoniou
2014-06-02 16:30   ` Stephen Warren

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=538781B6.90703@wwwdotorg.org \
    --to=swarren@wwwdotorg.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.