linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: grant.likely@secretlab.ca (Grant Likely)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] Documentation: dt: update properties in TI GPMC NAND example
Date: Tue, 16 Apr 2013 11:01:24 +0100	[thread overview]
Message-ID: <20130416100124.78A3B3E14C0@localhost> (raw)
In-Reply-To: <1365528215-5030-1-git-send-email-jon-hunter@ti.com>

On Tue, 9 Apr 2013 12:23:35 -0500, Jon Hunter <jon-hunter@ti.com> wrote:
> The GPMC timing properties for device-tree have been updated
> by adding a "-ns" or "-ps" suffix to indicate the units of
> time the property represents. Therefore, update the timing
> property names for TI GPMC NAND example.
> 
> Signed-off-by: Jon Hunter <jon-hunter@ti.com>

Acked-by: Grant Likely <grant.likely@secretlab.ca>

> ---
>  .../devicetree/bindings/mtd/gpmc-nand.txt          |   28 ++++++++++----------
>  1 file changed, 14 insertions(+), 14 deletions(-)
> 
> diff --git a/Documentation/devicetree/bindings/mtd/gpmc-nand.txt b/Documentation/devicetree/bindings/mtd/gpmc-nand.txt
> index e7f8d7e..6a983c1 100644
> --- a/Documentation/devicetree/bindings/mtd/gpmc-nand.txt
> +++ b/Documentation/devicetree/bindings/mtd/gpmc-nand.txt
> @@ -56,20 +56,20 @@ Example for an AM33xx board:
>  			nand-bus-width = <16>;
>  			ti,nand-ecc-opt = "bch8";
>  
> -			gpmc,sync-clk = <0>;
> -			gpmc,cs-on = <0>;
> -			gpmc,cs-rd-off = <44>;
> -			gpmc,cs-wr-off = <44>;
> -			gpmc,adv-on = <6>;
> -			gpmc,adv-rd-off = <34>;
> -			gpmc,adv-wr-off = <44>;
> -			gpmc,we-off = <40>;
> -			gpmc,oe-off = <54>;
> -			gpmc,access = <64>;
> -			gpmc,rd-cycle = <82>;
> -			gpmc,wr-cycle = <82>;
> -			gpmc,wr-access = <40>;
> -			gpmc,wr-data-mux-bus = <0>;
> +			gpmc,sync-clk-ps = <0>;
> +			gpmc,cs-on-ns = <0>;
> +			gpmc,cs-rd-off-ns = <44>;
> +			gpmc,cs-wr-off-ns = <44>;
> +			gpmc,adv-on-ns = <6>;
> +			gpmc,adv-rd-off-ns = <34>;
> +			gpmc,adv-wr-off-ns = <44>;
> +			gpmc,we-off-ns = <40>;
> +			gpmc,oe-off-ns = <54>;
> +			gpmc,access-ns = <64>;
> +			gpmc,rd-cycle-ns = <82>;
> +			gpmc,wr-cycle-ns = <82>;
> +			gpmc,wr-access-ns = <40>;
> +			gpmc,wr-data-mux-bus-ns = <0>;
>  
>  			#address-cells = <1>;
>  			#size-cells = <1>;
> -- 
> 1.7.10.4
> 
> 
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

-- 
Grant Likely, B.Sc, P.Eng.
Secret Lab Technologies, Ltd.

      reply	other threads:[~2013-04-16 10:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-09 17:23 [PATCH] Documentation: dt: update properties in TI GPMC NAND example Jon Hunter
2013-04-16 10:01 ` Grant Likely [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=20130416100124.78A3B3E14C0@localhost \
    --to=grant.likely@secretlab.ca \
    --cc=linux-arm-kernel@lists.infradead.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).