From: Mitch Bradley <wmb@firmworks.com>
To: Robert Sciuk <robert.sciuk@exfo.com>
Cc: devicetree-discuss@lists.ozlabs.org, linuxppc-dev@lists.ozlabs.org
Subject: Re: fpga driver on custom PPC target platform (P4080) ...
Date: Mon, 07 Nov 2011 11:31:16 -1000 [thread overview]
Message-ID: <4EB84E24.9000000@firmworks.com> (raw)
In-Reply-To: <2DD52030B5146141BEB762A11AE97C4C0100CB3D@SPQCEXC05.exfo.com>
On 11/7/2011 10:09 AM, Robert Sciuk wrote:
> In my continuing saga of dev/tree driver development, I have a problem which might be obvious to those who have more experience in such matters.
>
> I'm a bit perplexed on the tree nodes for the localbus/simplebus nodes for my FPGA. CS0 is reserved for booting (from NOR flash as required by our design), CS1 is tied to an FPGA which will always be present. CS2 actually is tied to both of two (optional) fpga's, which have been previously mapped by U-Boot (BRn/ORn configuration). Should I specify a ranges command as follows? This seems somehow wrong, to me, and I'm wondering if there is an alternative representation which would work better in this case. If you recall, the programming control lines are handled on the I2C bus, via a gpio controller. In an ideal world, the optional FPE1 and FPE2 fpgas will have the identical .bts stream, and should support the option to program both simultaneously, or each individually, but I'm at a
loss as how to best represent this in the tree.
I would be tempted to add another level of hierarchy as a container for
the two FPEs on CS2.
>
> localbus@ffe124000 {
> compatible = "fsl,p4080-elbc", "fsl,elbc", "simple-bus";
> reg =<0xf 0xfe124000 0 0x1000>;
> interrupts =<25 2 0 0>;
> interrupt-parent =<&mpic>;
> #address-cells =<2>;
> #size-cells =<1>;
>
> /* Local bus region mappings */
> ranges =<0 0 0xf 0xe8000000 0x08000000 /* CS0: Boot flash */
> 1 0 0xf 0xd0000000 0x7fff /* CS1: FPGA0 - LIM */
> 2 0 0xf 0xd1000000 0x7fff /* CS2: FPGA1 - FPE1 */
> 2 0 0xf 0xd2000000 0x7fff>; /* CS2: FPGA2 - FPE2 */
>
> flash@0,0 {
> compatible = "cfi-flash";
> reg =<0 0 0x08000000>;
> bank-width =<2>;
> device-width =<2>;
> #size-cells =<1>;
> #address-cells =<1>;
>
> partition@0 {
> label = "rcw";
> reg =<0x0 0x20000>;
> read-only;
> };
> partition@40000 {
> label = "saveenv";
> reg =<0x40000 0x20000>;
> };
> partition@7000000 {
> label = "fman-firmware";
> reg =<0x7000000 0x20000>;
> read-only;
> };
> partition@7f80000 {
> label = "u-boot";
> reg =<0x7f80000 0x80000>;
> read-only;
> };
> };
>
> lim: fpga@1, {
> }
>
> fpe1: fpga@2, {
> }
>
> fpe2: fpga@2, {
> }
>
> Again, any pointers here would be greatly appreciated ...
>
> Cheers,
> Rob Sciuk
> _______________________________________________
> devicetree-discuss mailing list
> devicetree-discuss@lists.ozlabs.org
> https://lists.ozlabs.org/listinfo/devicetree-discuss
>
next prev parent reply other threads:[~2011-11-07 21:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-03 22:12 fpga driver on custom PPC target platform (P4080) Robert Sciuk
2011-11-04 16:36 ` Tabi Timur-B04825
[not found] ` <CAOZdJXWjS4t9cOKRB3rxy0iCFAYRyEgg6kfQwvydUQSyO1ttoA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-11-04 16:42 ` Robert Sciuk
2011-11-04 18:19 ` Robert Sciuk
[not found] ` <2DD52030B5146141BEB762A11AE97C4C0100C8C1-OMuKRxKQdmAsN9D57aW0LdBPR1lH4CV8@public.gmane.org>
2011-11-05 0:40 ` David Gibson
2011-11-07 18:48 ` Robert Sciuk
[not found] ` <20111105004050.GA1384-MK4v0fQdeXQXU02nzanrWNbf9cGiqdzd@public.gmane.org>
2011-11-07 20:09 ` Robert Sciuk
2011-11-07 21:31 ` Mitch Bradley [this message]
[not found] ` <4EB84E24.9000000-D5eQfiDGL7eakBO8gow8eQ@public.gmane.org>
2011-11-07 21:50 ` Robert Sciuk
2011-11-07 22:14 ` Scott Wood
2011-11-07 23:07 ` Robert Sciuk
[not found] ` <4EB8582A.3070303-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
2011-11-07 23:29 ` Robert Sciuk
-- strict thread matches above, loose matches on Subject: below --
2011-11-02 22:43 Robert Sciuk
2011-11-03 21:22 ` Segher Boessenkool
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=4EB84E24.9000000@firmworks.com \
--to=wmb@firmworks.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=robert.sciuk@exfo.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).