From: Tony Lindgren <tony@atomide.com>
To: Pekon Gupta <pekon@ti.com>
Cc: linux-omap <linux-omap@vger.kernel.org>,
Javier Martinez Canillas <javier@dowhile0.org>,
bcousson@baylibre.com
Subject: Re: [PATCH v5 1/4] ARM: dts: am335x-bone: add support for beaglebone NAND cape
Date: Mon, 12 May 2014 08:03:52 -0700 [thread overview]
Message-ID: <20140512150351.GE31772@atomide.com> (raw)
In-Reply-To: <1399895353-3663-2-git-send-email-pekon@ti.com>
Hi,
* Pekon Gupta <pekon@ti.com> [140512 04:50]:
> +
> +&gpmc {
> + pinctrl-names = "default";
> + pinctrl-0 = <&nand_flash_x16>;
> + ranges = <0 0 0 0x01000000>; /* CS0: min address-space configurable under GPMC chip-select = 16MB*/
> + nand@0,0 {
> + reg = <0 0 0x380>; /* CS0, offset=0x0, GPMC register-space size=0x380 */
Just a nitpick comment on the comments.. But as we've gotten them
wrong for almost every GPMC entry so far, we should fix it.
The "GPMC register-space" here can be a bit confusing still
as they are really the the device IO registers. I suggest we
standardize the comments like this for GPMC:
&gpmc {
pinctrl-names = "default";
pinctrl-0 = <&nand_flash_x16>;
ranges = <0 0 0 0x01000000>; /* 16MB GPMC partition */
nand@0,0 {
reg = <0 0 0x380>; /* device IO registers */
...
};
Regards,
Tony
next prev parent reply other threads:[~2014-05-12 15:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-12 11:49 [PATCH v5 0/4] add parallel NAND support for TI's new OMAPx and AMxx platforms (Part-2) Pekon Gupta
2014-05-12 11:49 ` [PATCH v5 1/4] ARM: dts: am335x-bone: add support for beaglebone NAND cape Pekon Gupta
2014-05-12 15:03 ` Tony Lindgren [this message]
2014-05-12 11:49 ` [PATCH v5 2/4] ARM: dts: am437x-gp-evm: add support for parallel NAND flash Pekon Gupta
2014-05-12 11:49 ` [PATCH v5 3/4] ARM: dts: dra7: " Pekon Gupta
2014-05-12 11:49 ` [PATCH v5 4/4] ARM: dts: am43xx: fix starting offset of NAND.filesystem MTD partition Pekon Gupta
2014-05-12 12:27 ` [PATCH v5 0/4] add parallel NAND support for TI's new OMAPx and AMxx platforms (Part-2) Javier Martinez Canillas
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=20140512150351.GE31772@atomide.com \
--to=tony@atomide.com \
--cc=bcousson@baylibre.com \
--cc=javier@dowhile0.org \
--cc=linux-omap@vger.kernel.org \
--cc=pekon@ti.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.