linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Roese <sr@denx.de>
To: linuxppc-dev@ozlabs.org
Cc: linux-mtd@lists.infradead.org, devicetree-discuss@ozlabs.org,
	Sean MacLennan <smaclennan@pikatech.com>
Subject: Re: [PATCH] ndfc driver
Date: Tue, 9 Dec 2008 07:10:27 +0100	[thread overview]
Message-ID: <200812090710.27781.sr@denx.de> (raw)
In-Reply-To: <20081208193446.37e27e26@lappy.seanm.ca>

On Tuesday 09 December 2008, 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".

The 4xx NAND controller was first implemented on the 440EP, IIRC. So I'm 
pretty sure that this controller is an IBM core and not am AMCC core. So this 
should be "ibm,ndfc".

And with this change it makes no sense to put this file "ndfc.txt" into the 
amcc directory.

Josh, where should this go then?

Best regards,
Stefan

  parent reply	other threads:[~2008-12-09  6:10 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20081203222832.3fc77d28@lappy.seanm.ca>
2008-12-04 14:01 ` [PATCH] ndfc driver Josh Boyer
2008-12-04 17:17   ` Sean MacLennan
2008-12-09  0:34   ` Sean MacLennan
2008-12-09  2:11     ` Anton Vorontsov
2008-12-09  2:45       ` Sean MacLennan
2008-12-09  3:32         ` Josh Boyer
2008-12-09  4:54           ` Sean MacLennan
2008-12-09  7:57             ` Mitch Bradley
2008-12-10  4:01               ` Sean MacLennan
2008-12-10  8:28                 ` Mitch Bradley
2008-12-09  6:10     ` Stefan Roese [this message]
2008-12-09 11:24       ` Josh Boyer
2008-12-10 23:16       ` Sean MacLennan
2008-12-17  4:14         ` Sean MacLennan
2008-12-17 11:34           ` Josh Boyer
2008-12-17 13:26         ` Josh Boyer
2008-12-09  0:51   ` Sean MacLennan
     [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=200812090710.27781.sr@denx.de \
    --to=sr@denx.de \
    --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 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).