From: Grant Likely <grant.likely@secretlab.ca>
To: Rob Herring <rob.herring@calxeda.com>,
Tony Lindgren <tony@atomide.com>,
Benoit Cousson <b-cousson@ti.com>
Cc: device-tree <devicetree-discuss@lists.ozlabs.org>,
linux-omap <linux-omap@vger.kernel.org>,
linux-arm <linux-arm-kernel@lists.infradead.org>,
Daniel Mack <zonque@gmail.com>,
Ezequiel Garcia <elezegarcia@gmail.com>,
Mark Jackson <mpfj-list@mimc.co.uk>,
Jon Hunter <jon-hunter@ti.com>
Subject: Re: [PATCH V4 10/18] ARM: OMAP2+: Add function to read GPMC settings from device-tree
Date: Mon, 15 Apr 2013 14:27:37 +0100 [thread overview]
Message-ID: <20130415132737.A2A6E3E0AA8@localhost> (raw)
In-Reply-To: <1363710956-26773-11-git-send-email-jon-hunter@ti.com>
On Tue, 19 Mar 2013 11:35:48 -0500, Jon Hunter <jon-hunter@ti.com> wrote:
> Adds a function to read the various GPMC chip-select settings from
> device-tree and store them in the gpmc_settings structure.
>
> Update the GPMC device-tree binding documentation to describe these
> options.
>
> Signed-off-by: Jon Hunter <jon-hunter@ti.com>
> Tested-by: Ezequiel Garcia <ezequiel.garcia@free-electrons.com>
> ---
> Documentation/devicetree/bindings/bus/ti-gpmc.txt | 23 ++++++++++++
> arch/arm/mach-omap2/gpmc.c | 40 +++++++++++++++++++++
> arch/arm/mach-omap2/gpmc.h | 2 ++
> 3 files changed, 65 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/bus/ti-gpmc.txt b/Documentation/devicetree/bindings/bus/ti-gpmc.txt
> index 5ddb2e9..6fde1cf 100644
> --- a/Documentation/devicetree/bindings/bus/ti-gpmc.txt
> +++ b/Documentation/devicetree/bindings/bus/ti-gpmc.txt
> @@ -65,6 +65,29 @@ The following are only applicable to OMAP3+ and AM335x:
> - gpmc,wr-access
> - gpmc,wr-data-mux-bus
>
> +GPMC chip-select settings properties for child nodes. All are optional.
> +
> +- gpmc,burst-length Page/burst length. Must be 4, 8 or 16.
> +- gpmc,burst-wrap Enables wrap bursting
> +- gpmc,burst-read Enables read page/burst mode
> +- gpmc,burst-write Enables write page/burst mode
> +- gpmc,device-nand Device is NAND
> +- gpmc,device-width Total width of device(s) connected to a GPMC
> + chip-select in bytes. The GPMC supports 8-bit
> + and 16-bit devices and so this property must be
> + 1 or 2.
I would suggest specifying the actual number of bits. ie. 8 or 16. There is some
precidence for that already in DT bindings.
> +- gpmc,mux-add-data Address and data multiplexing configuration.
> + Valid values are 1 for address-address-data
> + multiplexing mode and 2 for address-data
> + multiplexing mode.
> +- gpmc,sync-read Enables synchronous read. Defaults to asynchronous
> + is this is not set.
'if'?
> +- gpmc,sync-write Enables synchronous writes. Defaults to asynchronous
> + is this is not set.
> +- gpmc,wait-pin Wait-pin used by client. Must be less than
> + "gpmc,num-waitpins".
> +- gpmc,wait-on-read Enables wait monitoring on reads.
> +- gpmc,wait-on-write Enables wait monitoring on writes.
Otherwise looks okay to me.
g.
next prev parent reply other threads:[~2013-04-15 13:27 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-19 16:35 [PATCH V4 00/18] ARM: OMAP2+: GPMC clean-up and DT update Jon Hunter
2013-03-19 16:35 ` [PATCH V4 01/18] ARM: OMAP2+: Simplify code configuring ONENAND devices Jon Hunter
2013-03-19 16:35 ` [PATCH V4 02/18] ARM: OMAP2+: Add variable to store number of GPMC waitpins Jon Hunter
2013-03-19 16:35 ` [PATCH V4 03/18] ARM: OMAP2+: Add structure for storing GPMC settings Jon Hunter
2013-03-19 16:35 ` [PATCH V4 04/18] ARM: OMAP2+: Add function for configuring " Jon Hunter
2013-03-19 16:35 ` [PATCH V4 05/18] ARM: OMAP2+: Convert ONENAND to use gpmc_cs_program_settings() Jon Hunter
2013-03-19 16:35 ` [PATCH V4 06/18] ARM: OMAP2+: Convert NAND " Jon Hunter
2013-03-19 16:35 ` [PATCH V4 07/18] ARM: OMAP2+: Convert SMC91x " Jon Hunter
2013-03-19 16:35 ` [PATCH V4 08/18] ARM: OMAP2+: Convert TUSB " Jon Hunter
2013-03-19 16:35 ` [PATCH V4 09/18] ARM: OMAP2+: Don't configure of chip-select options in gpmc_cs_configure() Jon Hunter
2013-03-19 16:35 ` [PATCH V4 10/18] ARM: OMAP2+: Add function to read GPMC settings from device-tree Jon Hunter
2013-04-15 13:27 ` Grant Likely [this message]
2013-04-15 16:54 ` Jon Hunter
2013-03-19 16:35 ` [PATCH V4 11/18] ARM: OMAP2+: Add additional GPMC timing parameters Jon Hunter
2013-03-19 16:35 ` [PATCH V4 12/18] ARM: OMAP2+: Add device-tree support for NOR flash Jon Hunter
2013-03-19 16:35 ` [PATCH V4 13/18] ARM: OMAP2+: Convert NAND to retrieve GPMC settings from DT Jon Hunter
2013-03-19 16:35 ` [PATCH V4 14/18] ARM: OMAP2+: Convert ONENAND " Jon Hunter
2013-03-19 16:35 ` [PATCH V4 15/18] ARM: OMAP2+: Detect incorrectly aligned GPMC base address Jon Hunter
2013-03-19 16:35 ` [PATCH V4 16/18] ARM: OMAP2+: Remove unnecesssary GPMC definitions and variable Jon Hunter
2013-03-19 16:35 ` [PATCH V4 17/18] ARM: OMAP2+: Allow GPMC probe to complete even if CS mapping fails Jon Hunter
2013-03-19 16:35 ` [PATCH V4 18/18] ARM: OMAP2+: return -ENODEV if GPMC child device creation fails Jon Hunter
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=20130415132737.A2A6E3E0AA8@localhost \
--to=grant.likely@secretlab.ca \
--cc=b-cousson@ti.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=elezegarcia@gmail.com \
--cc=jon-hunter@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=mpfj-list@mimc.co.uk \
--cc=rob.herring@calxeda.com \
--cc=tony@atomide.com \
--cc=zonque@gmail.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).