All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anton Vorontsov <avorontsov@ru.mvista.com>
To: Sean MacLennan <smaclennan@pikatech.com>
Cc: linuxppc-dev@ozlabs.org, devicetree-discuss@ozlabs.org,
	linux-mtd@lists.infradead.org
Subject: Re: [PATCH] ndfc driver
Date: Tue, 9 Dec 2008 05:11:15 +0300	[thread overview]
Message-ID: <20081209021115.GA13948@oksana.dev.rtsoft.ru> (raw)
In-Reply-To: <20081208193446.37e27e26@lappy.seanm.ca>

Hi Sean,

On Mon, Dec 08, 2008 at 07:34:46PM -0500, Sean MacLennan wrote:
> On Thu, 4 Dec 2008 09:01:07 -0500
> "Josh Boyer" <jwboyer@linux.vnet.ibm.com> wrote:
> 
> > In addition to an example DTS patch (probably to warp itself), could
> > you briefly write up a binding and put it in
> > Documentation/powerpc/dts-bindings/amcc (or similar)?  Also please CC
> > the devicetree-discuss list on that part.
> 
> Here is a start at the doc. I have sent it as a patch, but could just
> as easily send raw text.
> 
> The example comes from the warp dts, just with less partitions, so I
> have not included a warp dts patch here.
> 
> Cheers,
>    Sean
> 
> diff --git a/Documentation/powerpc/dts-bindings/amcc/ndfc.txt
> b/Documentation/powerpc/dts-bindings/amcc/ndfc.txt new file mode 100644
> index 0000000..668f4a9
> --- /dev/null
> +++ b/Documentation/powerpc/dts-bindings/amcc/ndfc.txt
> @@ -0,0 +1,31 @@
> +AMCC NDFC (NanD Flash Controller)
> +
> +Required properties:
> +- compatible : "amcc,ndfc".
> +- reg : should specify chip select and size used for the chip (0x2000).
> +
> +Optional properties:
> +- ccr : NDFC config and control register value (default 0).
> +- bank-settings : NDFC bank configuration register value (default 0).
> +- partition(s) - follows the OF MTD standard for partitions
> +
> +Example:
> +
> +nand@1,0 {
> +	compatible = "amcc,ndfc";

The first line in this file says that this is a controller...

> +	reg = <0x00000001 0x00000000 0x00002000>;
> +	ccr = <0x00001000>;
> +	bank-settings = <0x80002222>;
> +	#address-cells = <1>;
> +	#size-cells = <1>;
> +	partition@0 {

So this is a controller with partitions? ;-)

Recalling my own mistakes with the FSL UPM NAND controller bindings,
and Josh's comment:

http://www.mail-archive.com/linuxppc-dev@ozlabs.org/msg16572.html

I think the bindings should look like this:

nand-controller@.. {
	...controller's properties...

	nand-chip@... {
		...chip's properties...

		partition@... {
			...partition's properties...
		};
	};

	nand-chip@... {
		...
	};
};

Sure, I understand that there are plenty of boards with the "old"
scheme flashed into the firmware... Just something you might
want to consider for the future updates for the driver/bindings.

Thanks,

-- 
Anton Vorontsov
email: cbouatmailru@gmail.com
irc://irc.freenode.net/bd2

WARNING: multiple messages have this Message-ID (diff)
From: Anton Vorontsov <avorontsov@ru.mvista.com>
To: Sean MacLennan <smaclennan@pikatech.com>
Cc: linuxppc-dev@ozlabs.org, devicetree-discuss@ozlabs.org,
	linux-mtd@lists.infradead.org
Subject: Re: [PATCH] ndfc driver
Date: Tue, 9 Dec 2008 05:11:15 +0300	[thread overview]
Message-ID: <20081209021115.GA13948@oksana.dev.rtsoft.ru> (raw)
In-Reply-To: <20081208193446.37e27e26@lappy.seanm.ca>

Hi Sean,

On Mon, Dec 08, 2008 at 07:34:46PM -0500, Sean MacLennan wrote:
> On Thu, 4 Dec 2008 09:01:07 -0500
> "Josh Boyer" <jwboyer@linux.vnet.ibm.com> wrote:
> 
> > In addition to an example DTS patch (probably to warp itself), could
> > you briefly write up a binding and put it in
> > Documentation/powerpc/dts-bindings/amcc (or similar)?  Also please CC
> > the devicetree-discuss list on that part.
> 
> Here is a start at the doc. I have sent it as a patch, but could just
> as easily send raw text.
> 
> The example comes from the warp dts, just with less partitions, so I
> have not included a warp dts patch here.
> 
> Cheers,
>    Sean
> 
> diff --git a/Documentation/powerpc/dts-bindings/amcc/ndfc.txt
> b/Documentation/powerpc/dts-bindings/amcc/ndfc.txt new file mode 100644
> index 0000000..668f4a9
> --- /dev/null
> +++ b/Documentation/powerpc/dts-bindings/amcc/ndfc.txt
> @@ -0,0 +1,31 @@
> +AMCC NDFC (NanD Flash Controller)
> +
> +Required properties:
> +- compatible : "amcc,ndfc".
> +- reg : should specify chip select and size used for the chip (0x2000).
> +
> +Optional properties:
> +- ccr : NDFC config and control register value (default 0).
> +- bank-settings : NDFC bank configuration register value (default 0).
> +- partition(s) - follows the OF MTD standard for partitions
> +
> +Example:
> +
> +nand@1,0 {
> +	compatible = "amcc,ndfc";

The first line in this file says that this is a controller...

> +	reg = <0x00000001 0x00000000 0x00002000>;
> +	ccr = <0x00001000>;
> +	bank-settings = <0x80002222>;
> +	#address-cells = <1>;
> +	#size-cells = <1>;
> +	partition@0 {

So this is a controller with partitions? ;-)

Recalling my own mistakes with the FSL UPM NAND controller bindings,
and Josh's comment:

http://www.mail-archive.com/linuxppc-dev@ozlabs.org/msg16572.html

I think the bindings should look like this:

nand-controller@.. {
	...controller's properties...

	nand-chip@... {
		...chip's properties...

		partition@... {
			...partition's properties...
		};
	};

	nand-chip@... {
		...
	};
};

Sure, I understand that there are plenty of boards with the "old"
scheme flashed into the firmware... Just something you might
want to consider for the future updates for the driver/bindings.

Thanks,

-- 
Anton Vorontsov
email: cbouatmailru@gmail.com
irc://irc.freenode.net/bd2

______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/

  reply	other threads:[~2008-12-09  2:11 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-04  3:28 [PATCH] ndfc driver Sean MacLennan
2008-12-04 14:01 ` Josh Boyer
2008-12-04 17:17   ` Sean MacLennan
2008-12-09  0:34   ` Sean MacLennan
2008-12-09  2:11     ` Anton Vorontsov [this message]
2008-12-09  2:11       ` Anton Vorontsov
2008-12-09  2:45       ` Sean MacLennan
2008-12-09  2:45         ` Sean MacLennan
2008-12-09  3:32         ` Josh Boyer
2008-12-09  3:32           ` Josh Boyer
2008-12-09  4:54           ` Sean MacLennan
2008-12-09  4:54             ` Sean MacLennan
2008-12-09  7:57             ` Mitch Bradley
2008-12-09  7:57               ` Mitch Bradley
2008-12-09  7:57               ` Mitch Bradley
2008-12-10  4:01               ` Sean MacLennan
2008-12-10  4:01                 ` Sean MacLennan
2008-12-10  8:28                 ` Mitch Bradley
2008-12-10  8:28                   ` Mitch Bradley
2008-12-09  6:10     ` Stefan Roese
2008-12-09 11:24       ` Josh Boyer
2008-12-10 23:16       ` Sean MacLennan
2008-12-17  4:14         ` Sean MacLennan
2008-12-17  4:14           ` Sean MacLennan
2008-12-17 11:34           ` Josh Boyer
2008-12-17 11:34             ` Josh Boyer
2008-12-17 13:26         ` Josh Boyer
2008-12-09  0:51   ` Sean MacLennan
  -- strict thread matches above, loose matches on Subject: below --
2008-12-23 12:26 Kostas Nakos
2008-12-23 22:00 ` Sean MacLennan
2008-12-24  6:58   ` knakos
2008-12-27  1:56     ` Sean MacLennan
2008-12-29 10:58   ` Kostas Nakos
2009-01-06  1:23     ` Sean MacLennan
2009-01-07  9:51       ` Kostas Nakos
2009-01-07 17:21         ` Sean MacLennan
2009-01-08 15:37           ` Kostas Nakos
     [not found] <9293074.419171225391386417.JavaMail.nabble@isper.nabble.com>
     [not found] ` <20081030195858.28900ee5@lappy.seanm.ca>
     [not found]   ` <490D68A8.4060905@embedded-sol.com>
     [not found]     ` <20081102124804.15003002@lappy.seanm.ca>
     [not found]       ` <490E02D7.5050402@embedded-sol.com>
     [not found]         ` <20081102145811.6da10ef4@lappy.seanm.ca>
     [not found]           ` <490E074F.5050909@embedded-sol.com>
     [not found]             ` <20081102152958.42e88283@lappy.seanm.ca>
     [not found]               ` <490E4D0D.9060207@embedded-sol.com>
     [not found]                 ` <20081102204510.3d8e71f2@lappy.seanm.ca>
2008-11-03 10:56                   ` Felix Radensky
2008-10-30  6:08 Sean MacLennan

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=20081209021115.GA13948@oksana.dev.rtsoft.ru \
    --to=avorontsov@ru.mvista.com \
    --cc=devicetree-discuss@ozlabs.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=smaclennan@pikatech.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.