linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: marek.vasut@gmail.com (Marek Vasut)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/3] h1940: implement mmc_power function
Date: Tue, 24 Aug 2010 17:07:31 +0200	[thread overview]
Message-ID: <201008241707.31629.marek.vasut@gmail.com> (raw)
In-Reply-To: <201008241756.11529.anarsoul@gmail.com>

Dne ?t 24. srpna 2010 16:56:06 Vasily Khoruzhick napsal(a):
> ? ????????? ?? 24 ??????? 2010 17:41:57 ????? Marek Vasut ???????:
> > Dne ?t 24. srpna 2010 16:21:01 Vasily Khoruzhick napsal(a):
> > > ? ????????? ?? 24 ??????? 2010 17:01:12 ????? Marek Vasut ???????:
> > > > pr_err() and don't probe the device for which you couldn't request
> > > > GPIO.
> > > 
> > > Well, handling those errors in machine init functions doesn't make
> > > sense. PDA is not usable without basic hardware.
> > 
> > You can use PDA without LCD for example (there are such people, trust
> > me). So, this comment really isn't too valid. You can also use PDA
> > without MMC support, you still have onboard flash, etc. etc.
> 
> But error handling here just increases code size, and gpio_request in init
> function should always succeed. It means something's going really wrong
> (kernel bug or misconfiguration) if gpio_request fails. Btw, Ben suggested
> to use WARN_ON in machine init, look through init functions of qt2410,
> n30, rx1950, vr1000, etc.

See my previous response. It'd increase code size, but if you mark that code 
__init, it'll be freed after that function finishes so it doesn't matter.

If something wrong goes on, you can still debug it without for example MMC card 
(though if you continued probing the MMC driver, it might cause additional 
unwanted noise and make the debugging harder). That's the whole point.

Cheers
> 
> Regards
> Vasily

  reply	other threads:[~2010-08-24 15:07 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-19 15:00 [PATCH 0/3] h1940 series Vasily Khoruzhick
2010-08-19 15:00 ` [PATCH 1/3] h1940: use gpiolib for latch access Vasily Khoruzhick
2010-08-24 13:49   ` Marek Vasut
2010-08-24 14:04     ` Vasily Khoruzhick
2010-08-24 14:40       ` Marek Vasut
2010-08-24 14:50         ` Vasily Khoruzhick
2010-08-24 15:04           ` Marek Vasut
2010-09-02 10:53   ` Russell King - ARM Linux
2010-08-19 15:00 ` [PATCH 2/3] h1940: fix h1940-bluetooth compilation Vasily Khoruzhick
2010-08-24 13:50   ` Marek Vasut
2010-08-24 13:57     ` Vasily Khoruzhick
2010-08-24 14:00       ` Marek Vasut
2010-08-19 15:00 ` [PATCH 3/3] h1940: implement mmc_power function Vasily Khoruzhick
2010-08-24 13:52   ` Marek Vasut
2010-08-24 14:00     ` Vasily Khoruzhick
2010-08-24 14:01       ` Marek Vasut
2010-08-24 14:21         ` Vasily Khoruzhick
2010-08-24 14:41           ` Marek Vasut
2010-08-24 14:56             ` Vasily Khoruzhick
2010-08-24 15:07               ` Marek Vasut [this message]
2010-08-24 15:19                 ` Vasily Khoruzhick
2010-08-24 13:24 ` [PATCH 0/3] h1940 series Vasily Khoruzhick

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=201008241707.31629.marek.vasut@gmail.com \
    --to=marek.vasut@gmail.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;
as well as URLs for NNTP newsgroup(s).