From: Boris Brezillon <boris.brezillon@free-electrons.com>
To: Prabhakar Kushwaha <prabhakar.kushwaha@nxp.com>
Cc: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
"oss@buserror.net" <oss@buserror.net>,
"computersforpeace@gmail.com" <computersforpeace@gmail.com>,
Jagdish Gediya <jagdish.gediya@nxp.com>,
"dedekind1@gmail.com" <dedekind1@gmail.com>
Subject: Re: [PATCH][v2] driver: mtd: update struct map_info's swap as per map requirement.
Date: Thu, 21 Dec 2017 09:07:51 +0100 [thread overview]
Message-ID: <20171221090751.2e29ad0e@bbrezillon> (raw)
In-Reply-To: <HE1PR04MB12411FD6374970400B42696F970D0@HE1PR04MB1241.eurprd04.prod.outlook.com>
Hi,
On Thu, 21 Dec 2017 05:03:11 +0000
Prabhakar Kushwaha <prabhakar.kushwaha@nxp.com> wrote:
> Hi Boris,
>
You're lucky that I poll the MTD ML from time to time, because I'm not
even Cc-ed on this email.
>
> > -----Original Message-----
> > From: Prabhakar Kushwaha [mailto:prabhakar.kushwaha@nxp.com]
> > Sent: Wednesday, November 29, 2017 4:57 PM
> > To: linux-mtd@lists.infradead.org
> > Cc: dedekind1@gmail.com; oss@buserror.net; computersforpeace@gmail.com;
> > Jagdish Gediya <jagdish.gediya@nxp.com>; Prabhakar Kushwaha
> > <prabhakar.kushwaha@nxp.com>
> > Subject: [PATCH][v2] driver: mtd: update struct map_info's swap as per map
> > requirement.
> >
> > From: Jagdish Gediya <jagdish.gediya@nxp.com>
> >
> > It is not necessary for all device's maps to be CFI_HOST_ENDIAN.
> > Maps device can be Big endian or little endian.
> >
> > Currently it is being taken care using CONFIG_MTD_CFI_LE_BYTE_SWAP or
> > CONFIG_MTD_CFI_BE_BYTE_SWAP i.e. compile time.
> >
> > Now update struct map_info's swap field based on device characteristics
> > defined in device tree.
> >
> > Signed-off-by: Prabhakar Kushwaha <prabhakar.kushwaha@nxp.com>
> > Signed-off-by: Jagdish Gediya <jagdish.gediya@nxp.com>
> > ---
> > Changes for v2: Incorporated review comments from Boris Brezillon
> > https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fpatchw
> > ork.ozlabs.org%2Fpatch%2F758381%2F&data=02%7C01%7Cprabhakar.kushwah
> > a%40nxp.com%7C9050b00591c44afe1fcd08d5371c445a%7C686ea1d3bc2b4c6f
> > a92cd99c5c301635%7C0%7C0%7C636475516901200278&sdata=l6iFa15%2FxgO
> > fnmzmRgwFUbrwhY26ROw7rO1REh342mc%3D&reserved=0
> >
> > drivers/mtd/maps/physmap_of_core.c | 8 ++++++++
> > 1 file changed, 8 insertions(+)
> >
> > diff --git a/drivers/mtd/maps/physmap_of_core.c
> > b/drivers/mtd/maps/physmap_of_core.c
> > index b1bd4fa..27f44a0 100644
> > --- a/drivers/mtd/maps/physmap_of_core.c
> > +++ b/drivers/mtd/maps/physmap_of_core.c
> > @@ -20,6 +20,7 @@
> > #include <linux/mtd/map.h>
> > #include <linux/mtd/partitions.h>
> > #include <linux/mtd/concat.h>
> > +#include <linux/mtd/cfi_endian.h>
> > #include <linux/of.h>
> > #include <linux/of_address.h>
> > #include <linux/of_platform.h>
> > @@ -233,6 +234,13 @@ static int of_flash_probe(struct platform_device *dev)
> > info->list[i].map.bankwidth = be32_to_cpup(width);
> > info->list[i].map.device_node = dp;
> >
> > + if (of_property_read_bool(dp->parent, "big-endian"))
> > + info->list[i].map.swap = CFI_BIG_ENDIAN;
> > + else if (of_property_read_bool(dp->parent, "little-endian"))
> > + info->list[i].map.swap = CFI_LITTLE_ENDIAN;
> > + else if (of_property_read_bool(dp->parent, "host-endian"))
> > + info->list[i].map.swap = CFI_HOST_ENDIAN;
> > +
> > err = of_flash_probe_gemini(dev, dp, &info->list[i].map);
> > if (err)
> > goto err_out;
> > --
>
> As per the patchwork status, its state is "Change Requested"
>
> http://patchwork.ozlabs.org/patch/842542/
>
> I am not seeing any review comments on this patch.
> What kind of change is required.
The binding is still being discussed with Scott, and I won't merge the
code supposed to handle the new property until you've agreed on
something.
Regards,
Boris
prev parent reply other threads:[~2017-12-21 8:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-29 11:26 [PATCH][v2] driver: mtd: update struct map_info's swap as per map requirement Prabhakar Kushwaha
2017-12-21 5:03 ` Prabhakar Kushwaha
2017-12-21 8:07 ` Boris Brezillon [this message]
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=20171221090751.2e29ad0e@bbrezillon \
--to=boris.brezillon@free-electrons.com \
--cc=computersforpeace@gmail.com \
--cc=dedekind1@gmail.com \
--cc=jagdish.gediya@nxp.com \
--cc=linux-mtd@lists.infradead.org \
--cc=oss@buserror.net \
--cc=prabhakar.kushwaha@nxp.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