From: Boris Brezillon <boris.brezillon@free-electrons.com>
To: "William A. Kennington III" <wak@google.com>
Cc: linux-mtd@lists.infradead.org, Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
devicetree@vger.kernel.org
Subject: Re: [PATCH] mtd: powernv: Support MTD_NO_ERASE
Date: Thu, 21 Sep 2017 09:59:30 +0200 [thread overview]
Message-ID: <20170921095930.4b473f91@bbrezillon> (raw)
In-Reply-To: <20170905202339.20732-1-wak@google.com>
+the DT maintainers
On Tue, 5 Sep 2017 13:23:39 -0700
"William A. Kennington III" <wak@google.com> wrote:
> As of skiboot@ba99af9b149d02438347b055e6e7d6bd15e33551, we now support
I didn't find this commit in mainline.
> adding a device tree entry which marks a flash device as not needing
> erase. This patch adds support for setting MTD_NO_ERASE on powernvflash
> devices which have the property no-erase.
>
> Signed-off-by: William A. Kennington III <wak@google.com>
> ---
> drivers/mtd/devices/powernv_flash.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/drivers/mtd/devices/powernv_flash.c b/drivers/mtd/devices/powernv_flash.c
> index f5396f26ddb4..fab9f9121b4c 100644
> --- a/drivers/mtd/devices/powernv_flash.c
> +++ b/drivers/mtd/devices/powernv_flash.c
> @@ -196,6 +196,8 @@ static int powernv_flash_set_driver_info(struct device *dev,
> mtd->name = of_get_property(dev->of_node, "name", NULL);
> mtd->type = MTD_NORFLASH;
> mtd->flags = MTD_WRITEABLE;
> + if (of_property_read_bool(dev->of_node, "no-erase"))
> + mtd->flags |= MTD_NO_ERASE;
I don't see this property document in a DT binding doc, which is
mandatory. Actually, there's no DT bindings doc at all for the
'ibm,opal-flash' device in mainline, is this normal?
> mtd->size = size;
> mtd->erasesize = erase_size;
> mtd->writebufsize = mtd->writesize = 1;
next prev parent reply other threads:[~2017-09-21 8:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-05 20:23 [PATCH] mtd: powernv: Support MTD_NO_ERASE William A. Kennington III
2017-09-21 7:59 ` Boris Brezillon [this message]
[not found] ` <CAPnigKmBujCoKdtXwnK6YsU=YvXM+MaDvDvKpUXEVgHzOC-VEw@mail.gmail.com>
2017-09-22 4:13 ` Michael Ellerman
2017-10-16 15:55 ` Boris Brezillon
2017-10-17 13:21 ` Rob Herring
2017-10-18 5:11 ` Stewart Smith
2017-10-30 8:48 ` Boris Brezillon
2017-10-30 15:23 ` Rob Herring
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=20170921095930.4b473f91@bbrezillon \
--to=boris.brezillon@free-electrons.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=wak@google.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