devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Grant Likely <grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org>
To: Michal Simek <monstr-pSz03upnqPeHXe+LvDLADg@public.gmane.org>,
	devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org,
	Rob Herring <rob.herring-bsGFqQB8/DxBDgjK7y7TUQ@public.gmane.org>,
	Josh Cartwright <josh.cartwright-acOepvfBmUk@public.gmane.org>,
	Soren Brinkmann
	<soren.brinkmann-gjFFaj9aHVfQT0dZR+AlfA@public.gmane.org>
Subject: Re: RFC: Static memory controller node description
Date: Fri, 08 Feb 2013 22:55:03 +0000	[thread overview]
Message-ID: <20130208225503.E93763E2C27@localhost> (raw)
In-Reply-To: <CAHTX3dJ+ii9dP7w860Or80NWOAPoYZt8ftUwNfAe6WkEoeQJXQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

On Thu, 10 Jan 2013 16:40:09 +0100, Michal Simek <monstr-pSz03upnqPeHXe+LvDLADg@public.gmane.org> wrote:
> Hi guys,
> 
> we want to add static memory controller driver for xilinx zynq to the
> linux kernel. (It will go to drivers/memory/ folder)
> Just need to clear dts fragment which describe it.
> 
> It is compatible with pl353 with 2 interfaces when only one interface
> can be used.
> Nand, nor and sram memories are supported. Driver will do additional
> setup for NAND and power management.
> 
> I am using extended compatible property based on
> Documentation/devicetree/bindings/arm/primecell.txt. Is it correct?
> 
> Nand case (we have special driver for nand) - interrupts are used only
> in connection with nand.
> 
> smc@0xe000e000 {
> 	#address-cells = <1>;
> 	#size-cells = <1>;
> 	compatible = "xlnx,ps7-smc", "arm,pl353", "arm,primecell";
> 	reg = <0xe000e000 0x1000>;
> 	interrupts = <0 18 4>;
> 	interrupt-parent = <&ps7_scugic_0>;
> 	ranges;
> 	nand@e1000000 {
> 		compatible = "xlnx,ps7-nand-1.00.a";
> 		reg = <0xe1000000 0x1000000>;
> 		xlnx,nand-width = <16>;
> 	}
> }
> 
> or this one for NOR
> 
> smc@0xe000e000 {
> 	#address-cells = <1>;
> 	#size-cells = <1>;
> 	compatible = "xlnx,ps7-smc", "arm,pl353", "arm,primecell";
> 	reg = <0xe000e000 0x1000>;
> 	ranges;
> 	nor: nor@e2000000 {
> 		compatible = "cfi-flash";
> 		reg = <0xE2000000 0x2000000>;
> 		bank-width = <1>;
> 	}
> }
> 
> Can you see any problem with these dts fragments?

Looks fine to me.

g.

  parent reply	other threads:[~2013-02-08 22:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-10 15:40 RFC: Static memory controller node description Michal Simek
     [not found] ` <CAHTX3dJ+ii9dP7w860Or80NWOAPoYZt8ftUwNfAe6WkEoeQJXQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-02-08 22:55   ` Grant Likely [this message]
2013-02-12 13:30   ` Ezequiel Garcia
     [not found]     ` <CALF0-+V8iJZGW1riVSEXv0PGThOHxRh7P6JZb_ESb9C=+OyPOQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-02-12 13:48       ` Michal Simek
     [not found]         ` <CAHTX3dJT40OC1vf-KYLshhiDNigZRKOBh6ieH8qPgbyCMcjwPA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-02-12 13:52           ` 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=20130208225503.E93763E2C27@localhost \
    --to=grant.likely-s3s/wqlpoipyb63q8fvjnq@public.gmane.org \
    --cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
    --cc=josh.cartwright-acOepvfBmUk@public.gmane.org \
    --cc=monstr-pSz03upnqPeHXe+LvDLADg@public.gmane.org \
    --cc=rob.herring-bsGFqQB8/DxBDgjK7y7TUQ@public.gmane.org \
    --cc=soren.brinkmann-gjFFaj9aHVfQT0dZR+AlfA@public.gmane.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).