From: Daniel Walker <danielwa@cisco.com>
To: Raghav Dogra <raghav.dogra@nxp.com>,
Brian Norris <computersforpeace@gmail.com>,
Jaiprakash Singh <b44839@freescale.com>,
Scott Wood <scottwood@freescale.com>,
Lijun Pan <Lijun.Pan@freescale.com>,
linuxppc-dev@lists.ozlabs.org,
"xe-kernel@external.cisco.com" <xe-kernel@external.cisco.com>
Subject: t1040 IFC flash driver Extended Chip Select
Date: Wed, 6 Jul 2016 13:23:20 -0700 [thread overview]
Message-ID: <577D68B8.8020305@cisco.com> (raw)
Hi,
We are using the t1040 platform, and we have found that we need to
populate this register. In the Technical Reference Manual it's
description is section 24.3.2. This option appears in the driver, but it
doesn't appears to be used anyplace.
We we're considered adding something to the device tree to allow
populating this value, but I'm wondering if any of you have specific
considerations on how this is done. Or maybe it's not needed at all, and
we're just missing something.
(not a good patch, just an example.)
diff --git
a/Documentation/devicetree/bindings/memory-controllers/fsl/ifc.txt
b/Documentation/devicetree/bindings/memory-controllers/fsl/ifc.txt
index 89427b0..b506001 100644
--- a/Documentation/devicetree/bindings/memory-controllers/fsl/ifc.txt
+++ b/Documentation/devicetree/bindings/memory-controllers/fsl/ifc.txt
@@ -24,6 +24,8 @@ Properties:
- ranges : Each range corresponds to a single chipselect, and covers
the entire access window as configured.
+- cspr_ext : This value sets the extended chip select for all banks.
+
Child device nodes describe the devices connected to IFC such as NOR (e.g.
cfi-flash) and NAND (fsl,ifc-nand). There might be board specific devices
like FPGAs, CPLDs, etc.
Daniel
next reply other threads:[~2016-07-06 20:33 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-06 20:23 Daniel Walker [this message]
2016-07-07 0:57 ` t1040 IFC flash driver Extended Chip Select Scott Wood
2016-07-07 15:48 ` Daniel Walker
2016-07-07 19:26 ` Scott Wood
2016-07-07 19:44 ` Daniel Walker
2016-07-07 20:34 ` Scott Wood
2016-07-07 20:52 ` Daniel Walker
2016-07-07 21:23 ` Scott Wood
2016-07-07 21:49 ` Daniel Walker
2016-07-07 21:59 ` Scott Wood
2016-07-07 22:01 ` Daniel Walker
2016-07-07 22:37 ` Scott Wood
2016-07-07 23:48 ` Daniel Walker
2016-07-09 1:12 ` Scott Wood
2016-07-11 16:36 ` Daniel Walker
2016-07-11 16:55 ` Scott Wood
2016-07-11 17:10 ` Daniel Walker
2016-07-11 18:27 ` Scott Wood
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=577D68B8.8020305@cisco.com \
--to=danielwa@cisco.com \
--cc=Lijun.Pan@freescale.com \
--cc=b44839@freescale.com \
--cc=computersforpeace@gmail.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=raghav.dogra@nxp.com \
--cc=scottwood@freescale.com \
--cc=xe-kernel@external.cisco.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;
as well as URLs for NNTP newsgroup(s).