From: Frans Klaver <frans.klaver@xsens.com>
To: Ezequiel Garcia <ezequiel@vanguardiasur.com.ar>
Cc: linux-omap@vger.kernel.org,
Brian Norris <computersforpeace@gmail.com>,
linux-mtd@lists.infradead.org, Roger Quadros <rogerq@ti.com>
Subject: Re: [PATCH typo-resend] mtd: omap: fix mtd devices not showing up
Date: Tue, 28 Oct 2014 09:57:41 +0100 [thread overview]
Message-ID: <20141028085740.GG2383@ci00147.xsens-tech.local> (raw)
In-Reply-To: <544E9CB1.5020804@vanguardiasur.com.ar>
On Mon, Oct 27, 2014 at 04:27:45PM -0300, Ezequiel Garcia wrote:
>
> On 10/27/2014 10:56 AM, Roger Quadros wrote:
>
> > Alternatively we could fix either elm_config() or omap_nand_probe() to
> > return -EPROBE_DEFER in case the device is present but driver not yet probed.
> >
>
> Yes, that's a good idea. Can't we do both? Getting a systematic deferred
> probe sounds like a bit silly to me.
It may be. If we do both and something moves again, or something is
added that depends on omap_elm but is probed earlier, you won't be
noticing the new systematic probe deferral until you really start
looking at it.
There isn't a real dependency system in the drivers, is there?
Thanks,
Frans
next prev parent reply other threads:[~2014-10-28 8:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-27 13:32 [PATCH typo-resend] mtd: omap: fix mtd devices not showing up Frans Klaver
2014-10-27 13:56 ` Roger Quadros
2014-10-27 14:01 ` Frans Klaver
2014-10-27 19:27 ` Ezequiel Garcia
2014-10-28 8:57 ` Frans Klaver [this message]
2014-10-28 8:58 ` Ezequiel Garcia
2014-10-27 14:34 ` [PATCH v2] " Frans Klaver
2014-10-28 9:46 ` Roger Quadros
2014-10-29 11:36 ` Frans Klaver
2014-10-29 13:33 ` Roger Quadros
2014-10-29 13:34 ` Ezequiel Garcia
2014-10-30 1:47 ` Brian Norris
2014-10-30 6:02 ` Frans Klaver
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=20141028085740.GG2383@ci00147.xsens-tech.local \
--to=frans.klaver@xsens.com \
--cc=computersforpeace@gmail.com \
--cc=ezequiel@vanguardiasur.com.ar \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=rogerq@ti.com \
/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