From: Jon Hunter <jon-hunter@ti.com>
To: Javier Martinez Canillas <javier.martinez@collabora.co.uk>
Cc: Benoit Cousson <b-cousson@ti.com>,
Tony Lindgren <tony@atomide.com>,
linux-omap <linux-omap@vger.kernel.org>
Subject: Re: [PATCH 1/1] Documentation: dt: update TI GPMC ethernet binding properties
Date: Tue, 9 Apr 2013 11:26:57 -0500 [thread overview]
Message-ID: <51644151.2080200@ti.com> (raw)
In-Reply-To: <1365509490-26991-1-git-send-email-javier.martinez@collabora.co.uk>
On 04/09/2013 07:11 AM, Javier Martinez Canillas 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 ethernet binding.
>
> Signed-off-by: Javier Martinez Canillas <javier.martinez@collabora.co.uk>
> ---
>
> Jon, Benoit:
>
> Sorry that I didn't send this patch before but I just realized
> that the GPMC timing properties changed after
>
> commit 5330dc16 ("ARM: OMAP2+: Add GPMC DT support for Ethernet child nodes")
>
> got queued.
Thanks, I missed this one too. Looks like I need to update the gpmc-nand
documentation as well :-(
> Tony,
>
> Is still possible to queue this patch on your omap-for-v3.10/gpmc branch
> or it is too late?
If it is I think that this could be queued as a fix. Tony?
> Thanks a lot and best regards,
> Javier
>
> Documentation/devicetree/bindings/net/gpmc-eth.txt | 56 ++++++++++----------
> 1 files changed, 28 insertions(+), 28 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/net/gpmc-eth.txt b/Documentation/devicetree/bindings/net/gpmc-eth.txt
> index 24cb4e4..ace4a64 100644
> --- a/Documentation/devicetree/bindings/net/gpmc-eth.txt
> +++ b/Documentation/devicetree/bindings/net/gpmc-eth.txt
> @@ -26,16 +26,16 @@ Required properties:
> - bank-width: Address width of the device in bytes. GPMC supports 8-bit
> and 16-bit devices and so must be either 1 or 2 bytes.
> - compatible: Compatible string property for the ethernet child device.
> -- gpmc,cs-on: Chip-select assertion time
> -- gpmc,cs-rd-off: Chip-select de-assertion time for reads
> -- gpmc,cs-wr-off: Chip-select de-assertion time for writes
> -- gpmc,oe-on: Output-enable assertion time
> -- gpmc,oe-off Output-enable de-assertion time
> -- gpmc,we-on: Write-enable assertion time
> -- gpmc,we-off: Write-enable de-assertion time
> -- gpmc,access: Start cycle to first data capture (read access)
> -- gpmc,rd-cycle: Total read cycle time
> -- gpmc,wr-cycle: Total write cycle time
> +- gpmc,cs-on-ns: Chip-select assertion time
> +- gpmc,cs-rd-off-ns: Chip-select de-assertion time for reads
> +- gpmc,cs-wr-off-ns: Chip-select de-assertion time for writes
> +- gpmc,oe-on-ns: Output-enable assertion time
> +- gpmc,oe-off-ns: Output-enable de-assertion time
> +- gpmc,we-on-ns: Write-enable assertion time
> +- gpmc,we-off-ns: Write-enable de-assertion time
> +- gpmc,access-ns: Start cycle to first data capture (read access)
> +- gpmc,rd-cycle-ns: Total read cycle time
> +- gpmc,wr-cycle-ns: Total write cycle time
> - reg: Chip-select, base address (relative to chip-select)
> and size of the memory mapped for the device.
> Note that base address will be typically 0 as this
> @@ -65,24 +65,24 @@ gpmc: gpmc@6e000000 {
> bank-width = <2>;
>
> gpmc,mux-add-data;
> - gpmc,cs-on = <0>;
> - gpmc,cs-rd-off = <186>;
> - gpmc,cs-wr-off = <186>;
> - gpmc,adv-on = <12>;
> - gpmc,adv-rd-off = <48>;
> - gpmc,adv-wr-off = <48>;
> - gpmc,oe-on = <54>;
> - gpmc,oe-off = <168>;
> - gpmc,we-on = <54>;
> - gpmc,we-off = <168>;
> - gpmc,rd-cycle = <186>;
> - gpmc,wr-cycle = <186>;
> - gpmc,access = <114>;
> - gpmc,page-burst-access = <6>;
> - gpmc,bus-turnaround = <12>;
> - gpmc,cycle2cycle-delay = <18>;
> - gpmc,wr-data-mux-bus = <90>;
> - gpmc,wr-access = <186>;
> + gpmc,cs-on-ns = <0>;
> + gpmc,cs-rd-off-ns = <186>;
> + gpmc,cs-wr-off-ns = <186>;
> + gpmc,adv-on-ns = <12>;
> + gpmc,adv-rd-off-ns = <48>;
> + gpmc,adv-wr-off-ns = <48>;
> + gpmc,oe-on-ns = <54>;
> + gpmc,oe-off-ns = <168>;
> + gpmc,we-on-ns = <54>;
> + gpmc,we-off-ns = <168>;
> + gpmc,rd-cycle-ns = <186>;
> + gpmc,wr-cycle-ns = <186>;
> + gpmc,access-ns = <114>;
> + gpmc,page-burst-access-ns = <6>;
> + gpmc,bus-turnaround-ns = <12>;
> + gpmc,cycle2cycle-delay-ns = <18>;
> + gpmc,wr-data-mux-bus-ns = <90>;
> + gpmc,wr-access-ns = <186>;
> gpmc,cycle2cycle-samecsen;
> gpmc,cycle2cycle-diffcsen;
Acked-by: Jon Hunter <jon-hunter@ti.com>
Cheers
Jon
next prev parent reply other threads:[~2013-04-09 16:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-09 12:11 [PATCH 1/1] Documentation: dt: update TI GPMC ethernet binding properties Javier Martinez Canillas
2013-04-09 16:26 ` Jon Hunter [this message]
2013-04-09 16:58 ` Tony Lindgren
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=51644151.2080200@ti.com \
--to=jon-hunter@ti.com \
--cc=b-cousson@ti.com \
--cc=javier.martinez@collabora.co.uk \
--cc=linux-omap@vger.kernel.org \
--cc=tony@atomide.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 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.