From: Zach Brown <zach.brown@ni.com>
To: <dwmw2@infradead.org>
Cc: <computersforpeace@gmail.com>,
<boris.brezillon@free-electrons.com>, <richard@nod.at>,
<dedekind1@gmail.com>, <linux-mtd@lists.infradead.org>,
<linux-kernel@vger.kernel.org>
Subject: [PATCH v3 2/5] mtd: ubi: use 'max_bad_blocks' to compute bad_peb_limit if available
Date: Fri, 28 Oct 2016 15:27:41 -0500 [thread overview]
Message-ID: <1477686464-7437-3-git-send-email-zach.brown@ni.com> (raw)
In-Reply-To: <1477686464-7437-1-git-send-email-zach.brown@ni.com>
From: Jeff Westfahl <jeff.westfahl@ni.com>
Use the MTD function 'max_bad_blocks' to compute the UBI bad_peb_limit,
if the function is implemented for an MTD and doesn't return an error.
Signed-off-by: Jeff Westfahl <jeff.westfahl@ni.com>
Signed-off-by: Zach Brown <zach.brown@ni.com>
---
drivers/mtd/ubi/build.c | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/drivers/mtd/ubi/build.c b/drivers/mtd/ubi/build.c
index 85d54f3..e9940a9 100644
--- a/drivers/mtd/ubi/build.c
+++ b/drivers/mtd/ubi/build.c
@@ -584,6 +584,10 @@ static int get_bad_peb_limit(const struct ubi_device *ubi, int max_beb_per1024)
int limit, device_pebs;
uint64_t device_size;
+ limit = mtd_max_bad_blocks(ubi->mtd, 0, ubi->mtd->size);
+ if (limit > 0)
+ return limit;
+
if (!max_beb_per1024)
return 0;
--
2.7.4
next prev parent reply other threads:[~2016-10-28 20:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-28 20:27 [PATCH v3 0/5] mtd: use ONFI bad blocks per LUN to calculate UBI bad PEB limit Zach Brown
2016-10-28 20:27 ` [PATCH v3 1/5] mtd: introduce function max_bad_blocks Zach Brown
2016-10-28 20:27 ` Zach Brown [this message]
2016-10-28 20:27 ` [PATCH v3 3/5] mtd: nand: Add bb_per_lun and blocks_per_lun fields to nand_chip Zach Brown
2016-11-01 13:50 ` Boris Brezillon
2016-11-01 18:32 ` Zach Brown
2016-11-06 17:53 ` Boris Brezillon
2016-10-28 20:27 ` [PATCH v3 4/5] mtd: nand: implement 'max_bad_blocks' mtd function Zach Brown
2016-10-28 20:27 ` [PATCH v3 5/5] mtd: nand: set bb_per_lun and blocks_per_lun for ONFI compliant chips Zach Brown
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=1477686464-7437-3-git-send-email-zach.brown@ni.com \
--to=zach.brown@ni.com \
--cc=boris.brezillon@free-electrons.com \
--cc=computersforpeace@gmail.com \
--cc=dedekind1@gmail.com \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=richard@nod.at \
/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).