From mboxrd@z Thu Jan 1 00:00:00 1970 From: Segher Boessenkool Subject: Re: fpga driver on custom PPC target platform (P4080) ... Date: Thu, 3 Nov 2011 22:22:13 +0100 Message-ID: References: <2DD52030B5146141BEB762A11AE97C4C0100C4AA@SPQCEXC05.exfo.com> Mime-Version: 1.0 (Apple Message framework v753.1) Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <2DD52030B5146141BEB762A11AE97C4C0100C4AA@SPQCEXC05.exfo.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: linuxppc-dev-bounces+glppe-linuxppc-embedded-2=m.gmane.org@lists.ozlabs.org Sender: linuxppc-dev-bounces+glppe-linuxppc-embedded-2=m.gmane.org@lists.ozlabs.org To: Robert Sciuk Cc: devicetree-discuss@lists.ozlabs.org, linuxppc-dev@lists.ozlabs.org List-Id: devicetree@vger.kernel.org > - How does one specify in the device tree an FPGA which uses > both I2c bus and localbus for programming? You have two device nodes, one on the localbus and one on the IIC bus. One of the nodes points to the other, or both do; you point to another node by having a property containing the phandle of that other node. It's probably easiest to make the IIC node point to the localbus node, because you will most likely always have exactly one of those, and you could have multiple IIC nodes on your FPGA, or none at all. But this is something you'll have to put in the device binding for your device, and it doesn't really matter what you choose -- it will work either way, some choices are more convenient than others though. Segher