From: Boris Brezillon <boris.brezillon@bootlin.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: David Woodhouse <dwmw2@infradead.org>,
Brian Norris <computersforpeace@gmail.com>,
Boris Brezillon <boris.brezillon@free-electrons.com>,
Marek Vasut <marek.vasut@gmail.com>,
Richard Weinberger <richard@nod.at>,
linux-mtd@lists.infradead.org
Subject: Re: [PATCH 1/2 v3] mtd: maps: Leave assigned complex mappings
Date: Sun, 2 Dec 2018 09:47:49 +0100 [thread overview]
Message-ID: <20181202094749.07a9687e@bbrezillon> (raw)
In-Reply-To: <20181127205358.32502-1-linus.walleij@linaro.org>
On Tue, 27 Nov 2018 21:53:57 +0100
Linus Walleij <linus.walleij@linaro.org> wrote:
> The simple_map_init() may need to be called with some
> function pointers already assigned for complex mappings,
> just bail out if complex handlers have already been
> assigned.
The commit message no longer matches what the patch does.
How about:
"
mtd: maps: physmap: Leave assigned complex mappings
SoC-specific drivers might provide their own map->xxx() implementation,
and calling simple_map_init() unconditionally will override those
implementations.
Make sure map->read is NULL before calling simple_map_init().
"
If you're okay with this new commit message, I can fix it when applying.
Regards,
Boris
>
> Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
> ---
> ChangeLog v2->v3:
> - Move check for pre-initialized simple map into
> physmap-core.c
> ChangeLog v1->v2:
> - Rebase on latest MTD development branch
> - Use a new approach as the code changed under me
> ---
> drivers/mtd/maps/physmap-core.c | 10 ++++++++--
> 1 file changed, 8 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/mtd/maps/physmap-core.c b/drivers/mtd/maps/physmap-core.c
> index e8c3b250d842..ecca7784de06 100644
> --- a/drivers/mtd/maps/physmap-core.c
> +++ b/drivers/mtd/maps/physmap-core.c
> @@ -514,10 +514,16 @@ static int physmap_flash_probe(struct platform_device *dev)
> err = physmap_addr_gpios_map_init(&info->maps[i]);
> if (err)
> goto err_out;
> - } else {
> - simple_map_init(&info->maps[i]);
> }
>
> + /*
> + * Only use the simple_map implementation if map hooks are not
> + * implemented. Since map->read() is mandatory checking for its
> + * presence is enough.
> + */
> + if (!info->maps[i].read)
> + simple_map_init(&info->maps[i]);
> +
> if (info->probe_type) {
> info->mtds[i] = do_map_probe(info->probe_type,
> &info->maps[i]);
next prev parent reply other threads:[~2018-12-02 8:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-27 20:53 [PATCH 1/2 v3] mtd: maps: Leave assigned complex mappings Linus Walleij
2018-11-27 20:53 ` [PATCH 2/2 v3] mtd: physmap_of_gemini: Handle pin control Linus Walleij
2018-12-07 9:10 ` [2/2,v3] " Boris Brezillon
2018-12-02 8:47 ` Boris Brezillon [this message]
2018-12-04 13:09 ` [PATCH 1/2 v3] mtd: maps: Leave assigned complex mappings Linus Walleij
2018-12-07 9:10 ` [1/2,v3] " Boris Brezillon
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=20181202094749.07a9687e@bbrezillon \
--to=boris.brezillon@bootlin.com \
--cc=boris.brezillon@free-electrons.com \
--cc=computersforpeace@gmail.com \
--cc=dwmw2@infradead.org \
--cc=linus.walleij@linaro.org \
--cc=linux-mtd@lists.infradead.org \
--cc=marek.vasut@gmail.com \
--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