All of lore.kernel.org
 help / color / mirror / Atom feed
From: Prabhakar Kushwaha <prabhakar.kushwaha@nxp.com>
To: linux-mtd@lists.infradead.org, devicetree@vger.kernel.org,
	robh@kernel.org, mark.rutland@arm.com, shawnguo@kernel.org
Cc: boris.brezillon@free-electrons.com, leoyang.li@nxp.com,
	oss@buserror.net, Prabhakar Kushwaha <prabhakar.kushwaha@nxp.com>,
	cyrille.pitchen@wedev4u.fr, computersforpeace@gmail.com,
	linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/4][v4][RESEND] dt-bindings: mtd-physmap: Add endianness supports
Date: Thu, 22 Feb 2018 15:45:06 +0530	[thread overview]
Message-ID: <20180222101511.29631-2-prabhakar.kushwaha@nxp.com> (raw)
In-Reply-To: <20180222101511.29631-1-prabhakar.kushwaha@nxp.com>

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.

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/

Resending as all patches of patchset never reaches to patchwork.

 Documentation/devicetree/bindings/mtd/mtd-physmap.txt | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/Documentation/devicetree/bindings/mtd/mtd-physmap.txt b/Documentation/devicetree/bindings/mtd/mtd-physmap.txt
index 4a0a48bf4ecb..961a8eed9d0d 100644
--- a/Documentation/devicetree/bindings/mtd/mtd-physmap.txt
+++ b/Documentation/devicetree/bindings/mtd/mtd-physmap.txt
@@ -41,6 +41,11 @@ 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 connection between controller and
+			flash. If this property is absent, flash is considered
+			to be host-endian.
+
 The device tree may optionally contain sub-nodes describing partitions of the
 address space. See partition.txt for more detail.
 
-- 
2.14.1

WARNING: multiple messages have this Message-ID (diff)
From: Prabhakar Kushwaha <prabhakar.kushwaha@nxp.com>
To: linux-mtd@lists.infradead.org, devicetree@vger.kernel.org,
	robh@kernel.org, mark.rutland@arm.com, shawnguo@kernel.org
Cc: linux-arm-kernel@lists.infradead.org,
	boris.brezillon@free-electrons.com, cyrille.pitchen@wedev4u.fr,
	computersforpeace@gmail.com, oss@buserror.net,
	leoyang.li@nxp.com,
	Prabhakar Kushwaha <prabhakar.kushwaha@nxp.com>
Subject: [PATCH 1/4][v4][RESEND] dt-bindings: mtd-physmap: Add endianness supports
Date: Thu, 22 Feb 2018 15:45:06 +0530	[thread overview]
Message-ID: <20180222101511.29631-2-prabhakar.kushwaha@nxp.com> (raw)
In-Reply-To: <20180222101511.29631-1-prabhakar.kushwaha@nxp.com>

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.

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/

Resending as all patches of patchset never reaches to patchwork.

 Documentation/devicetree/bindings/mtd/mtd-physmap.txt | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/Documentation/devicetree/bindings/mtd/mtd-physmap.txt b/Documentation/devicetree/bindings/mtd/mtd-physmap.txt
index 4a0a48bf4ecb..961a8eed9d0d 100644
--- a/Documentation/devicetree/bindings/mtd/mtd-physmap.txt
+++ b/Documentation/devicetree/bindings/mtd/mtd-physmap.txt
@@ -41,6 +41,11 @@ 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 connection between controller and
+			flash. If this property is absent, flash is considered
+			to be host-endian.
+
 The device tree may optionally contain sub-nodes describing partitions of the
 address space. See partition.txt for more detail.
 
-- 
2.14.1

WARNING: multiple messages have this Message-ID (diff)
From: prabhakar.kushwaha@nxp.com (Prabhakar Kushwaha)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/4][v4][RESEND] dt-bindings: mtd-physmap: Add endianness supports
Date: Thu, 22 Feb 2018 15:45:06 +0530	[thread overview]
Message-ID: <20180222101511.29631-2-prabhakar.kushwaha@nxp.com> (raw)
In-Reply-To: <20180222101511.29631-1-prabhakar.kushwaha@nxp.com>

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.

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/

Resending as all patches of patchset never reaches to patchwork.

 Documentation/devicetree/bindings/mtd/mtd-physmap.txt | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/Documentation/devicetree/bindings/mtd/mtd-physmap.txt b/Documentation/devicetree/bindings/mtd/mtd-physmap.txt
index 4a0a48bf4ecb..961a8eed9d0d 100644
--- a/Documentation/devicetree/bindings/mtd/mtd-physmap.txt
+++ b/Documentation/devicetree/bindings/mtd/mtd-physmap.txt
@@ -41,6 +41,11 @@ 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 connection between controller and
+			flash. If this property is absent, flash is considered
+			to be host-endian.
+
 The device tree may optionally contain sub-nodes describing partitions of the
 address space. See partition.txt for more detail.
 
-- 
2.14.1

  reply	other threads:[~2018-02-22 10:15 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-22 10:15 [PATCH 0/4][v4][RESEND] dt-bindings: mtd-physmap: Add endianness supports Prabhakar Kushwaha
2018-02-22 10:15 ` Prabhakar Kushwaha
2018-02-22 10:15 ` Prabhakar Kushwaha
2018-02-22 10:15 ` Prabhakar Kushwaha [this message]
2018-02-22 10:15   ` [PATCH 1/4][v4][RESEND] " Prabhakar Kushwaha
2018-02-22 10:15   ` Prabhakar Kushwaha
2018-02-22 10:15 ` [PATCH 2/4][v4][RESEND] driver: mtd: update struct map_info's swap as per map requirement Prabhakar Kushwaha
2018-02-22 10:15   ` Prabhakar Kushwaha
2018-02-22 10:15   ` Prabhakar Kushwaha
2018-02-22 10:15 ` [PATCH 3/4][v4][RESEND] ARM: dts: Add NOR connection type with IFC Prabhakar Kushwaha
2018-02-22 10:15   ` Prabhakar Kushwaha
2018-02-22 10:15   ` Prabhakar Kushwaha
2018-02-22 10:15 ` [PATCH 4/4][v4][RESEND] ARM64: " Prabhakar Kushwaha
2018-02-22 10:15   ` Prabhakar Kushwaha
2018-02-22 10:15   ` Prabhakar Kushwaha
2018-02-22 10:15 ` [PATCH 1/2][v2][RESEND] ARM: dts: Add big-endian for IFC on LS1021A Prabhakar Kushwaha
2018-02-22 10:15   ` Prabhakar Kushwaha
2018-02-22 10:15   ` Prabhakar Kushwaha
2018-02-22 10:31   ` Boris Brezillon
2018-02-22 10:31     ` Boris Brezillon
2018-02-22 10:31     ` Boris Brezillon
2018-02-22 10:15 ` [PATCH 2/2][v2][RESEND] ARM: dts: ls1021aqds: Add nand node for ifc controller Prabhakar Kushwaha
2018-02-22 10:15   ` Prabhakar Kushwaha
2018-02-22 10:15   ` Prabhakar Kushwaha
2018-02-22 10:28 ` [PATCH 0/4][v4][RESEND] dt-bindings: mtd-physmap: Add endianness supports Boris Brezillon
2018-02-22 10:28   ` Boris Brezillon
2018-02-22 10:28   ` Boris Brezillon
2018-02-24  9:09   ` Shawn Guo
2018-02-24  9:09     ` Shawn Guo
2018-02-24  9:09     ` Shawn Guo

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=20180222101511.29631-2-prabhakar.kushwaha@nxp.com \
    --to=prabhakar.kushwaha@nxp.com \
    --cc=boris.brezillon@free-electrons.com \
    --cc=computersforpeace@gmail.com \
    --cc=cyrille.pitchen@wedev4u.fr \
    --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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.