From mboxrd@z Thu Jan 1 00:00:00 1970 From: Scott Wood Subject: Re: [PATCH v4 4/6] tegra: fdt: Add NAND definitions to fdt Date: Mon, 30 Jul 2012 17:49:07 -0500 Message-ID: <50170F63.70403@freescale.com> References: <1343631210-22278-1-git-send-email-sjg@chromium.org> <1343631210-22278-5-git-send-email-sjg@chromium.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1343631210-22278-5-git-send-email-sjg-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: devicetree-discuss-bounces+gldd-devicetree-discuss=m.gmane.org-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org Sender: "devicetree-discuss" To: Simon Glass Cc: Stephen Warren , Devicetree Discuss , U-Boot Mailing List , Jerry Van Baren , Tom Warren List-Id: devicetree@vger.kernel.org On 07/30/2012 01:53 AM, Simon Glass wrote: > Add a flash node to handle the NAND, including memory timings and > page / block size information. > > Signed-off-by: Simon Glass > --- > Changes in v2: > - Update NAND binding to add "nvidia," prefix > > Changes in v3: > - Add reg property for unit address (should be used for chip select) > - Update fdt binding to make everything Nvidia-specific > > Changes in v4: > - Remove fdt bindings related to page structure > > board/nvidia/dts/tegra20-seaboard.dts | 10 ++++++++++ > 1 files changed, 10 insertions(+), 0 deletions(-) > > diff --git a/board/nvidia/dts/tegra20-seaboard.dts b/board/nvidia/dts/tegra20-seaboard.dts > index 3352539..25a63a0 100644 > --- a/board/nvidia/dts/tegra20-seaboard.dts > +++ b/board/nvidia/dts/tegra20-seaboard.dts > @@ -153,4 +153,14 @@ > 0x1f04008a>; > linux,fn-keymap = <0x05040002>; > }; > + > + nand-controller@70008000 { > + nvidia,wp-gpios = <&gpio 59 0>; /* PH3 */ > + nvidia,width = <8>; > + nvidia,timing = <26 100 20 80 20 10 12 10 70>; > + nand@0 { > + reg = <0>; > + compatible = "hynix,hy27uf4g2b", "nand-flash"; > + }; > + }; Are #address-cells, #size-cells, and reg on the controller node provided by an /include/? -Scott