All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Kocialkowski <contact@paulk.fr>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2 1/2] mmc: Board-specific MMC power initializations
Date: Wed, 05 Nov 2014 18:35:20 +0100	[thread overview]
Message-ID: <1415208920.2355.6.camel@collins> (raw)
In-Reply-To: <20141104183225.GI15133@bill-the-cat>

Hi there, thanks for the review,

Le mardi 04 novembre 2014 ? 13:32 -0500, Tom Rini a ?crit :
> On Tue, Nov 04, 2014 at 07:58:38PM +0200, Igor Grinberg wrote:
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> > 
> > Hi Tom,
> > 
> > On 11/04/14 17:56, Tom Rini wrote:
> > > On Sat, Nov 01, 2014 at 11:35:43AM +0100, Paul Kocialkowski wrote:
> > > 
> > >> Some devices may use non-standard combinations of regulators to power MMC:
> > >> this allows these devices to provide a board-specific MMC power init function
> > >> to set everything up in their own way.
> > >>
> > >> Signed-off-by: Paul Kocialkowski <contact@paulk.fr>
> > >> ---
> > >>  drivers/mmc/mmc.c | 8 ++++++++
> > >>  include/mmc.h     | 2 ++
> > >>  2 files changed, 10 insertions(+)
> > >>
> > >> diff --git a/drivers/mmc/mmc.c b/drivers/mmc/mmc.c
> > >> index 44a4feb..125f347 100644
> > >> --- a/drivers/mmc/mmc.c
> > >> +++ b/drivers/mmc/mmc.c
> > >> @@ -1277,6 +1277,12 @@ block_dev_desc_t *mmc_get_dev(int dev)
> > >>  }
> > >>  #endif
> > >>  
> > >> +/* board-specific MMC power initializations. */
> > >> +__weak int board_mmc_power_init(void)
> > >> +{
> > >> +	return -1;
> > >> +}
> > > 
> > > Since we don't check error return here which I think is fine just make
> > > this a void?  Thanks!
> > 
> > There is v3 posted a while ago...
> > We have also agreed on v4..

Note that v3 and v4 are the same, except that v3 didn't apply on top of
master.

> Yeah, oops, didn't delete these after catch-up.  I'm still not sure we
> should continue adding more unchecked return values "just because".

I agree that we shouldn't have an unchecked return value. So we could
either check the return value and print a warning, without aborting the
init sequence (what Igor proposed initially) or just make this return
void (what you both seem to agree on).

I'm fine with both solutions. I guess that enabling a regulator could
fail (say, because of an i2c error), so there is still sense in
returning int.

Let me know of what your definitive answer on this is. I'll make a new
patchset probably this friday (I'm running on a very tight schedule
until then).

-- 
Paul Kocialkowski, Replicant developer

Replicant is a fully free Android distribution

Website: http://www.replicant.us/
Redmine: http://redmine.replicant.us/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: This is a digitally signed message part
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20141105/a90469ed/attachment.pgp>

  reply	other threads:[~2014-11-05 17:35 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-28 17:25 [U-Boot] [PATCH] omap_hsmmc: Allow for board-specific MMC power init Paul Kocialkowski
2014-10-28 18:02 ` Igor Grinberg
2014-10-28 18:11   ` Paul Kocialkowski
2014-10-29 13:10     ` Igor Grinberg
2014-10-30 15:28 ` Pantelis Antoniou
2014-11-01 10:35 ` [U-Boot] [PATCH v2 1/2] mmc: Board-specific MMC power initializations Paul Kocialkowski
2014-11-01 10:35   ` [U-Boot] [PATCH v2 2/2] omap_hsmmc: Board-specific TWL4030 " Paul Kocialkowski
2014-11-04 15:56     ` Tom Rini
2014-11-05 17:37       ` Paul Kocialkowski
2014-11-04 15:56   ` [U-Boot] [PATCH v2 1/2] mmc: Board-specific " Tom Rini
2014-11-04 17:58     ` Igor Grinberg
2014-11-04 18:32       ` Tom Rini
2014-11-05 17:35         ` Paul Kocialkowski [this message]
2014-11-05 17:46           ` 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=1415208920.2355.6.camel@collins \
    --to=contact@paulk.fr \
    --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.