From: Jon Hunter <jon-hunter@ti.com>
To: Ezequiel Garcia <ezequiel.garcia@free-electrons.com>
Cc: Rob Herring <rob.herring@calxeda.com>,
Grant Likely <grant.likely@secretlab.ca>,
Tony Lindgren <tony@atomide.com>,
Benoit Cousson <b-cousson@ti.com>,
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>
Subject: Re: [PATCH V3 10/18] ARM: OMAP2+: Add function to read GPMC settings from device-tree
Date: Mon, 18 Mar 2013 08:43:26 -0500 [thread overview]
Message-ID: <514719FE.4030607@ti.com> (raw)
In-Reply-To: <20130317052401.GA9796@localhost>
On 03/17/2013 12:24 AM, Ezequiel Garcia wrote:
> Hi Jon,
>
> I have some tiny nitpicks...
>
> On Fri, Mar 15, 2013 at 10:21:08AM -0500, Jon Hunter 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>
>> ---
>> Documentation/devicetree/bindings/bus/ti-gpmc.txt | 23 ++++++++++
>> arch/arm/mach-omap2/gpmc.c | 49 +++++++++++++++++++++
>> arch/arm/mach-omap2/gpmc.h | 2 +
>> 3 files changed, 74 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.
>> +- 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.
>> +- 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.
>>
>> Example for an AM33xx board:
>>
>> diff --git a/arch/arm/mach-omap2/gpmc.c b/arch/arm/mach-omap2/gpmc.c
>> index 3ec1937..1e7eef3 100644
>> --- a/arch/arm/mach-omap2/gpmc.c
>> +++ b/arch/arm/mach-omap2/gpmc.c
>> @@ -1190,6 +1190,55 @@ static struct of_device_id gpmc_dt_ids[] = {
>> };
>> MODULE_DEVICE_TABLE(of, gpmc_dt_ids);
>>
>> +/**
>> + * gpmc_read_settings_dt - read gpmc settings from device-tree
>> + * @np: pointer to device-tree node for a gpmc child device
>> + * @p: pointer to gpmc settings structure
>> + *
>> + * Reads the GPMC settings for a GPMC child device from device-tree and
>> + * stores them in the GPMC settings structure passed. The GPMC settings
>> + * structure is initialise to zero by this function and so any previously
>
> s/initialise/initialized ?
Thanks will add the "d". However, "initialise" is correct British
English ;-)
>> + * stored settings will be clearer.
>
> s/clearer/cleared ?
>
> I'm not an english native speaker,
> so please bare with me if I'm wrong on these...
You are right here too. Will fix thanks!
Jon
WARNING: multiple messages have this Message-ID (diff)
From: jon-hunter@ti.com (Jon Hunter)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V3 10/18] ARM: OMAP2+: Add function to read GPMC settings from device-tree
Date: Mon, 18 Mar 2013 08:43:26 -0500 [thread overview]
Message-ID: <514719FE.4030607@ti.com> (raw)
In-Reply-To: <20130317052401.GA9796@localhost>
On 03/17/2013 12:24 AM, Ezequiel Garcia wrote:
> Hi Jon,
>
> I have some tiny nitpicks...
>
> On Fri, Mar 15, 2013 at 10:21:08AM -0500, Jon Hunter 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>
>> ---
>> Documentation/devicetree/bindings/bus/ti-gpmc.txt | 23 ++++++++++
>> arch/arm/mach-omap2/gpmc.c | 49 +++++++++++++++++++++
>> arch/arm/mach-omap2/gpmc.h | 2 +
>> 3 files changed, 74 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.
>> +- 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.
>> +- 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.
>>
>> Example for an AM33xx board:
>>
>> diff --git a/arch/arm/mach-omap2/gpmc.c b/arch/arm/mach-omap2/gpmc.c
>> index 3ec1937..1e7eef3 100644
>> --- a/arch/arm/mach-omap2/gpmc.c
>> +++ b/arch/arm/mach-omap2/gpmc.c
>> @@ -1190,6 +1190,55 @@ static struct of_device_id gpmc_dt_ids[] = {
>> };
>> MODULE_DEVICE_TABLE(of, gpmc_dt_ids);
>>
>> +/**
>> + * gpmc_read_settings_dt - read gpmc settings from device-tree
>> + * @np: pointer to device-tree node for a gpmc child device
>> + * @p: pointer to gpmc settings structure
>> + *
>> + * Reads the GPMC settings for a GPMC child device from device-tree and
>> + * stores them in the GPMC settings structure passed. The GPMC settings
>> + * structure is initialise to zero by this function and so any previously
>
> s/initialise/initialized ?
Thanks will add the "d". However, "initialise" is correct British
English ;-)
>> + * stored settings will be clearer.
>
> s/clearer/cleared ?
>
> I'm not an english native speaker,
> so please bare with me if I'm wrong on these...
You are right here too. Will fix thanks!
Jon
next prev parent reply other threads:[~2013-03-18 13:43 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-15 15:20 [PATCH V3 00/18] ARM: OMAP2+: GPMC clean-up and DT update Jon Hunter
2013-03-15 15:20 ` Jon Hunter
2013-03-15 15:20 ` [PATCH V3 01/18] ARM: OMAP2+: Simplify code configuring ONENAND devices Jon Hunter
2013-03-15 15:20 ` Jon Hunter
2013-03-15 15:21 ` [PATCH V3 02/18] ARM: OMAP2+: Add variable to store number of GPMC waitpins Jon Hunter
2013-03-15 15:21 ` Jon Hunter
2013-03-16 20:59 ` Ezequiel Garcia
2013-03-16 20:59 ` Ezequiel Garcia
2013-03-18 13:43 ` Jon Hunter
2013-03-18 13:43 ` Jon Hunter
2013-03-15 15:21 ` [PATCH V3 03/18] ARM: OMAP2+: Add structure for storing GPMC settings Jon Hunter
2013-03-15 15:21 ` Jon Hunter
2013-03-15 15:21 ` [PATCH V3 04/18] ARM: OMAP2+: Add function for configuring " Jon Hunter
2013-03-15 15:21 ` Jon Hunter
2013-03-15 15:21 ` [PATCH V3 05/18] ARM: OMAP2+: Convert ONENAND to use gpmc_cs_program_settings() Jon Hunter
2013-03-15 15:21 ` Jon Hunter
2013-03-15 15:21 ` [PATCH V3 06/18] ARM: OMAP2+: Convert NAND " Jon Hunter
2013-03-15 15:21 ` Jon Hunter
2013-03-15 15:21 ` [PATCH V3 07/18] ARM: OMAP2+: Convert SMC91x " Jon Hunter
2013-03-15 15:21 ` Jon Hunter
2013-03-15 15:21 ` [PATCH V3 08/18] ARM: OMAP2+: Convert TUSB " Jon Hunter
2013-03-15 15:21 ` Jon Hunter
2013-03-15 15:21 ` [PATCH V3 09/18] ARM: OMAP2+: Don't configure of chip-select options in gpmc_cs_configure() Jon Hunter
2013-03-15 15:21 ` Jon Hunter
2013-03-15 15:21 ` [PATCH V3 10/18] ARM: OMAP2+: Add function to read GPMC settings from device-tree Jon Hunter
2013-03-15 15:21 ` Jon Hunter
2013-03-17 5:24 ` Ezequiel Garcia
2013-03-17 5:24 ` Ezequiel Garcia
2013-03-18 13:43 ` Jon Hunter [this message]
2013-03-18 13:43 ` Jon Hunter
2013-03-15 15:21 ` [PATCH V3 11/18] ARM: OMAP2+: Add device-tree support for NOR flash Jon Hunter
2013-03-15 15:21 ` Jon Hunter
2013-03-15 15:21 ` [PATCH V3 12/18] ARM: OMAP2+: Add additional GPMC timing parameters Jon Hunter
2013-03-15 15:21 ` Jon Hunter
2013-03-18 14:07 ` Rob Herring
2013-03-18 14:07 ` Rob Herring
2013-03-18 14:32 ` Jon Hunter
2013-03-18 14:32 ` Jon Hunter
2013-03-18 15:59 ` Jon Hunter
2013-03-18 15:59 ` Jon Hunter
2013-03-15 15:21 ` [PATCH V3 13/18] ARM: OMAP2+: Convert NAND to retrieve GPMC settings from DT Jon Hunter
2013-03-15 15:21 ` Jon Hunter
2013-03-15 15:21 ` [PATCH V3 14/18] ARM: OMAP2+: Convert ONENAND " Jon Hunter
2013-03-15 15:21 ` Jon Hunter
2013-03-15 15:21 ` [PATCH V3 15/18] ARM: OMAP2+: Detect incorrectly aligned GPMC base address Jon Hunter
2013-03-15 15:21 ` Jon Hunter
2013-03-15 15:21 ` [PATCH V3 16/18] ARM: OMAP2+: Remove unnecesssary GPMC definitions and variable Jon Hunter
2013-03-15 15:21 ` Jon Hunter
2013-03-15 15:21 ` [PATCH V3 17/18] ARM: OMAP2+: Allow GPMC probe to complete even if CS mapping fails Jon Hunter
2013-03-15 15:21 ` Jon Hunter
2013-03-15 15:21 ` [PATCH V3 18/18] ARM: OMAP2+: return -ENODEV if GPMC child device creation fails Jon Hunter
2013-03-15 15:21 ` Jon Hunter
2013-03-17 5:34 ` [PATCH V3 00/18] ARM: OMAP2+: GPMC clean-up and DT update Ezequiel Garcia
2013-03-17 5:34 ` Ezequiel Garcia
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=514719FE.4030607@ti.com \
--to=jon-hunter@ti.com \
--cc=b-cousson@ti.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=elezegarcia@gmail.com \
--cc=ezequiel.garcia@free-electrons.com \
--cc=grant.likely@secretlab.ca \
--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 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.