From: Boris Brezillon <boris.brezillon@bootlin.com>
To: Prabhakar Kushwaha <prabhakar.kushwaha@nxp.com>
Cc: mark.rutland@arm.com, devicetree@vger.kernel.org,
boris.brezillon@free-electrons.com, poonam.aggrwal@nxp.com,
leoyang.li@nxp.com, oss@buserror.net,
linux-mtd@lists.infradead.org, computersforpeace@gmail.com,
shawnguo@kernel.org, robh@kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/2][v7] dt-bindings: mtd-physmap: Add endianness supports
Date: Wed, 28 Mar 2018 10:30:01 +0200 [thread overview]
Message-ID: <20180328103001.6f4b16d9@bbrezillon> (raw)
In-Reply-To: <20180328054443.2829-1-prabhakar.kushwaha@nxp.com>
On Wed, 28 Mar 2018 11:14:43 +0530
Prabhakar Kushwaha <prabhakar.kushwaha@nxp.com> wrote:
> Connection between flash and controller is not necessary to be always
> of same type. It may varies from platform to platform.
>
> Adding endianness (optional) property to provide connection type
> information.
You forgot to adjust your commit message.
If you're okay, I'll replace your message by:
"
Provides a way to specify the endianness to use when accessing a
memory-mapped flash.
"
>
> Signed-off-by: Prabhakar Kushwaha <prabhakar.kushwaha@nxp.com>
> Reviewed-by: Rob Herring <robh@kernel.org>
> ---
> Changes for v2: updated subject
> Changes for v3: fixed typo for "big-endian"
> Changes for v4: Moved binding definition in mtd-physmap.txt
> as discussed at https://patchwork.ozlabs.org/patch/842543/
> Changes for v5: Sending as it is
> Changes for v6: Updated binding when endianness property is absent
> Changes for v7: Updated binding details
>
> Documentation/devicetree/bindings/mtd/mtd-physmap.txt | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/mtd/mtd-physmap.txt b/Documentation/devicetree/bindings/mtd/mtd-physmap.txt
> index 4a0a48bf4ecb..232fa12e90ef 100644
> --- a/Documentation/devicetree/bindings/mtd/mtd-physmap.txt
> +++ b/Documentation/devicetree/bindings/mtd/mtd-physmap.txt
> @@ -41,6 +41,13 @@ additional (optional) property is defined:
>
> - erase-size : The chip's physical erase block size in bytes.
>
> + The device tree may optionally contain endianness property.
> + little-endian or big-endian : It Represents the endianness that should be used
> + by the controller to properly read/write data
> + from/to the flash. If this property is missing,
> + the endianness is chosen by the system
> + (potentially based on extra configuration options).
> +
> The device tree may optionally contain sub-nodes describing partitions of the
> address space. See partition.txt for more detail.
>
--
Boris Brezillon, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-03-28 8:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-28 5:44 [PATCH 1/2][v7] dt-bindings: mtd-physmap: Add endianness supports Prabhakar Kushwaha
2018-03-28 8:30 ` Boris Brezillon [this message]
2018-03-28 9:48 ` Prabhakar Kushwaha
2018-03-29 20:22 ` 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=20180328103001.6f4b16d9@bbrezillon \
--to=boris.brezillon@bootlin.com \
--cc=boris.brezillon@free-electrons.com \
--cc=computersforpeace@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=leoyang.li@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=oss@buserror.net \
--cc=poonam.aggrwal@nxp.com \
--cc=prabhakar.kushwaha@nxp.com \
--cc=robh@kernel.org \
--cc=shawnguo@kernel.org \
/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).