From: Ezequiel Garcia <ezequiel@vanguardiasur.com.ar>
To: pekon <pekon@pek-sem.com>
Cc: "Brian Norris" <computersforpeace@gmail.com>,
"Tony Lindgren" <tony@atomide.com>,
linux-mtd@lists.infradead.org,
linux-omap <linux-omap@vger.kernel.org>,
"Guido Martínez" <guido@vanguardiasur.com.ar>,
"Roger Quadros" <rogerq@ti.com>
Subject: Re: [PATCH 2/3] nand: omap2: Remove horrible ifdefs to fix module probe
Date: Sun, 7 Sep 2014 12:16:56 -0300 [thread overview]
Message-ID: <20140907151656.GA1048@arch.cereza> (raw)
In-Reply-To: <540C26F7.7020005@pek-sem.com>
On 07 Sep 03:05 PM, pekon wrote:
[..]
> As ECC-scheme is selected in GPMC driver based on DTS settings, so
> any mis-match is easily handled there.
> Moreover, error will occur when we change ECC-scheme on-the-fly,
> which is still not supported by framework, and require many other
> updates if we plan to support that in near future.
> So considering ECC-scheme as static configuration is a safe assumption.
>
> But surely you can drop new check in omap2_nand_ecc_check(), which
> is already covered in @@gpmc_probe_nand_child(...)
>
> However, I leave it to you and rogerq@ti.com (as he currently
> maintains OMAP NAND driver from TI side) to decide how to go about it.
>
As far as I can see, your proposal only cover the devicetree-probed case
and it won't work for legacy boards.
Given it seems we still support legacy, I'd say your proposal would break
things.
Not to mention that I still prefer to fail at probe time if the driver cannot
deal with the selected ECC, and that's exactly what omap2_nand_ecc_check()
does.
--
Ezequiel Garcia, VanguardiaSur
www.vanguardiasur.com.ar
WARNING: multiple messages have this Message-ID (diff)
From: Ezequiel Garcia <ezequiel@vanguardiasur.com.ar>
To: pekon <pekon@pek-sem.com>
Cc: "Roger Quadros" <rogerq@ti.com>,
"Brian Norris" <computersforpeace@gmail.com>,
"Tony Lindgren" <tony@atomide.com>,
linux-mtd@lists.infradead.org,
"Guido Martínez" <guido@vanguardiasur.com.ar>,
linux-omap <linux-omap@vger.kernel.org>
Subject: Re: [PATCH 2/3] nand: omap2: Remove horrible ifdefs to fix module probe
Date: Sun, 7 Sep 2014 12:16:56 -0300 [thread overview]
Message-ID: <20140907151656.GA1048@arch.cereza> (raw)
In-Reply-To: <540C26F7.7020005@pek-sem.com>
On 07 Sep 03:05 PM, pekon wrote:
[..]
> As ECC-scheme is selected in GPMC driver based on DTS settings, so
> any mis-match is easily handled there.
> Moreover, error will occur when we change ECC-scheme on-the-fly,
> which is still not supported by framework, and require many other
> updates if we plan to support that in near future.
> So considering ECC-scheme as static configuration is a safe assumption.
>
> But surely you can drop new check in omap2_nand_ecc_check(), which
> is already covered in @@gpmc_probe_nand_child(...)
>
> However, I leave it to you and rogerq@ti.com (as he currently
> maintains OMAP NAND driver from TI side) to decide how to go about it.
>
As far as I can see, your proposal only cover the devicetree-probed case
and it won't work for legacy boards.
Given it seems we still support legacy, I'd say your proposal would break
things.
Not to mention that I still prefer to fail at probe time if the driver cannot
deal with the selected ECC, and that's exactly what omap2_nand_ecc_check()
does.
--
Ezequiel Garcia, VanguardiaSur
www.vanguardiasur.com.ar
next prev parent reply other threads:[~2014-09-07 15:18 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-06 19:56 [PATCH 0/3] nand: omap2: Two and a half improvements Ezequiel Garcia
2014-09-06 19:56 ` [PATCH 1/3] nand: omap2: Add support for a flash-based bad block table Ezequiel Garcia
2014-09-06 19:56 ` [PATCH 2/3] nand: omap2: Remove horrible ifdefs to fix module probe Ezequiel Garcia
2014-09-06 21:10 ` pekon
2014-09-06 21:10 ` pekon
2014-09-06 21:47 ` Ezequiel Garcia
2014-09-06 21:47 ` Ezequiel Garcia
2014-09-06 23:17 ` Ezequiel Garcia
2014-09-06 23:17 ` Ezequiel Garcia
2014-09-07 9:35 ` pekon
2014-09-07 9:35 ` pekon
2014-09-07 15:16 ` Ezequiel Garcia [this message]
2014-09-07 15:16 ` Ezequiel Garcia
2014-09-08 8:45 ` Roger Quadros
2014-09-08 10:53 ` Roger Quadros
2014-09-10 12:48 ` Ezequiel Garcia
2014-09-10 13:05 ` Roger Quadros
2014-09-17 8:33 ` Brian Norris
2014-09-17 9:54 ` Ezequiel Garcia
2014-09-18 2:54 ` Brian Norris
2014-09-10 20:15 ` pekon
2014-09-08 11:28 ` Ezequiel Garcia
2014-09-06 19:56 ` [PATCH 3/3] nand: omap2: Replace pr_err with dev_err Ezequiel Garcia
2014-09-08 8:30 ` [PATCH 0/3] nand: omap2: Two and a half improvements Roger Quadros
2014-09-08 11:31 ` Ezequiel Garcia
2014-09-08 11:47 ` Roger Quadros
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=20140907151656.GA1048@arch.cereza \
--to=ezequiel@vanguardiasur.com.ar \
--cc=computersforpeace@gmail.com \
--cc=guido@vanguardiasur.com.ar \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=pekon@pek-sem.com \
--cc=rogerq@ti.com \
--cc=tony@atomide.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 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.