Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1652354
| From | Boris Brezillon <boris.brezillon@free-electrons.com> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH v4 3/5] mtd: handle partitioning on devices with 0 erasesize |
| Date | 2017-05-29 11:20 +0200 |
| Message-ID | <tMp0g-6bg-71@gated-at.bofh.it> (permalink) |
| References | <tKOm5-tO-7@gated-at.bofh.it> <tKOm6-tO-17@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Thu, 25 May 2017 11:49:14 +1200
Chris Packham <chris.packham@alliedtelesis.co.nz> wrote:
> erasesize is meaningful for flash devices but for SRAM there is no
> concept of an erase block so erasesize is set to 0. When partitioning
> these devices instead of ensuring partitions fall on erasesize
> boundaries we ensure they fall on writesize boundaries.
>
> Helped-by: Boris Brezillon <boris.brezillon@free-electrons.com>
> Signed-off-by: Chris Packham <chris.packham@alliedtelesis.co.nz>
Acked-by: Boris Brezillon <boris.brezillon@free-electrons.com>
> ---
> Changes in v3:
> - new
> Changes in v4:
> - None
>
> drivers/mtd/mtdpart.c | 25 ++++++++++++++++---------
> 1 file changed, 16 insertions(+), 9 deletions(-)
>
> diff --git a/drivers/mtd/mtdpart.c b/drivers/mtd/mtdpart.c
> index ea5e5307f667..5cef1247806c 100644
> --- a/drivers/mtd/mtdpart.c
> +++ b/drivers/mtd/mtdpart.c
> @@ -393,8 +393,11 @@ static struct mtd_part *allocate_partition(struct mtd_info *master,
> const struct mtd_partition *part, int partno,
> uint64_t cur_offset)
> {
> + int wr_alignment = master->erasesize ? : master->writesize;
> struct mtd_part *slave;
> + u32 remainder;
> char *name;
> + u64 tmp;
>
> /* allocate the partition structure */
> slave = kzalloc(sizeof(*slave), GFP_KERNEL);
> @@ -499,10 +502,11 @@ static struct mtd_part *allocate_partition(struct mtd_info *master,
> if (slave->offset == MTDPART_OFS_APPEND)
> slave->offset = cur_offset;
> if (slave->offset == MTDPART_OFS_NXTBLK) {
> + tmp = cur_offset;
> slave->offset = cur_offset;
> - if (mtd_mod_by_eb(cur_offset, master) != 0) {
> - /* Round up to next erasesize */
> - slave->offset = (mtd_div_by_eb(cur_offset, master) + 1) * master->erasesize;
> + remainder = do_div(tmp, wr_alignment);
> + if (remainder) {
> + slave->offset += wr_alignment - remainder;
> printk(KERN_NOTICE "Moving partition %d: "
> "0x%012llx -> 0x%012llx\n", partno,
> (unsigned long long)cur_offset, (unsigned long long)slave->offset);
> @@ -567,19 +571,22 @@ static struct mtd_part *allocate_partition(struct mtd_info *master,
> slave->mtd.erasesize = master->erasesize;
> }
>
> - if ((slave->mtd.flags & MTD_WRITEABLE) &&
> - mtd_mod_by_eb(slave->offset, &slave->mtd)) {
> + tmp = slave->offset;
> + remainder = do_div(tmp, wr_alignment);
> + if ((slave->mtd.flags & MTD_WRITEABLE) && remainder) {
> /* Doesn't start on a boundary of major erase size */
> /* FIXME: Let it be writable if it is on a boundary of
> * _minor_ erase size though */
> slave->mtd.flags &= ~MTD_WRITEABLE;
> - printk(KERN_WARNING"mtd: partition \"%s\" doesn't start on an erase block boundary -- force read-only\n",
> + printk(KERN_WARNING"mtd: partition \"%s\" doesn't start on an erase/write block boundary -- force read-only\n",
> part->name);
> }
> - if ((slave->mtd.flags & MTD_WRITEABLE) &&
> - mtd_mod_by_eb(slave->mtd.size, &slave->mtd)) {
> +
> + tmp = slave->mtd.size;
> + remainder = do_div(tmp, wr_alignment);
> + if ((slave->mtd.flags & MTD_WRITEABLE) && remainder) {
> slave->mtd.flags &= ~MTD_WRITEABLE;
> - printk(KERN_WARNING"mtd: partition \"%s\" doesn't end on an erase block -- force read-only\n",
> + printk(KERN_WARNING"mtd: partition \"%s\" doesn't end on an erase/write block -- force read-only\n",
> part->name);
> }
>
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
[PATCH v4 0/5] mtd: mchp23k256: device tree and mchp23lcv1024 Chris Packham <chris.packham@alliedtelesis.co.nz> - 2017-05-25 02:00 +0200
[PATCH v4 3/5] mtd: handle partitioning on devices with 0 erasesize Chris Packham <chris.packham@alliedtelesis.co.nz> - 2017-05-25 02:00 +0200
Re: [PATCH v4 3/5] mtd: handle partitioning on devices with 0 erasesize Boris Brezillon <boris.brezillon@free-electrons.com> - 2017-05-29 11:20 +0200
[PATCH v4 2/5] mtd: mchp23k256: switch to mtd_device_register() Chris Packham <chris.packham@alliedtelesis.co.nz> - 2017-05-25 02:00 +0200
Re: [PATCH v4 2/5] mtd: mchp23k256: switch to mtd_device_register() Boris Brezillon <boris.brezillon@free-electrons.com> - 2017-05-29 11:20 +0200
[PATCH v4 5/5] mtd: mchp23k256: Add support for mchp23lcv1024 Chris Packham <chris.packham@alliedtelesis.co.nz> - 2017-05-25 02:00 +0200
Re: [PATCH v4 5/5] mtd: mchp23k256: Add support for mchp23lcv1024 Boris Brezillon <boris.brezillon@free-electrons.com> - 2017-05-29 11:20 +0200
Re: [PATCH v4 5/5] mtd: mchp23k256: Add support for mchp23lcv1024 Rob Herring <robh@kernel.org> - 2017-05-31 20:00 +0200
[PATCH v4 4/5] mtd: mchp23k256: add partitioning support Chris Packham <chris.packham@alliedtelesis.co.nz> - 2017-05-25 02:00 +0200
Re: [PATCH v4 4/5] mtd: mchp23k256: add partitioning support Boris Brezillon <boris.brezillon@free-electrons.com> - 2017-05-29 11:20 +0200
Re: [PATCH v4 4/5] mtd: mchp23k256: add partitioning support Brian Norris <computersforpeace@gmail.com> - 2017-06-01 20:50 +0200
[PATCH v4 1/5] mtd: mchp23k256: Add OF device ID table Chris Packham <chris.packham@alliedtelesis.co.nz> - 2017-05-25 02:00 +0200
Re: [PATCH v4 1/5] mtd: mchp23k256: Add OF device ID table Boris Brezillon <boris.brezillon@free-electrons.com> - 2017-05-29 11:20 +0200
Re: [PATCH v4 1/5] mtd: mchp23k256: Add OF device ID table Rob Herring <robh@kernel.org> - 2017-05-31 20:00 +0200
Re: [PATCH v4 0/5] mtd: mchp23k256: device tree and mchp23lcv1024 Brian Norris <computersforpeace@gmail.com> - 2017-06-01 20:50 +0200
csiph-web