Ah, my compatible attribute was wrong:
Compatible = nxp,pca9539;
Should have been:
Compatible = nxp,pca953x;
The tree now seems to bind the i2c gpio drivers properly ... on to
the localbus mappings!
Ah. In that case the drivers should probably be extended to
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
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
-Original Message-
From: Mitch Bradley [mailto:w...@firmworks.com]
I would be tempted to add another level of hierarchy as a container for
the two FPEs on CS2.
Hi, Mitch.
As a long time Forth(er), I'm somewhat honoured to have this exchange with you
8-)
Do you mean something
On 11/07/2011 02:09 PM, 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
...
switched-bank@2,0 {
// no simple-bus here
compatible = something specific to your board's setup;
ranges = 0 0 2 0 0x8000;
// reg is here just to make the unit-addres valid
reg = 2 0 0;
-Original Message-
From: Scott Wood [mailto:scottw...@freescale.com]
Sent: Monday, November 07, 2011 5:14 PM
To: Robert Sciuk
Cc: linuxppc-dev@lists.ozlabs.org; devicetree-disc...@lists.ozlabs.org
Subject: Re: fpga driver on custom PPC target platform (P4080) ...
...
If you
On Thu, Nov 3, 2011 at 5:12 PM, Robert Sciuk robert.sc...@exfo.com wrote:
lim_r: gpio@e8 {
compatible = nxp,pca9539;
reg = 0xe8;
#gpio-cells = 2;
It appears that I'm not correctly creating the pca9539 nodes as of
yet (I'll be adding the phandles shortly). Any pointers for pca9539
driver nodes would be appreciated, as I took these from a similar tree,
but not the 95xx driver. I'll match them up with the code in the
morning ...
I
I *believe* you are not supposed to create separate nodes for reading
and writing. I know that's how I2C works, but I think the I2C layer
takes care of that for you.
If you look at other device trees, you'll see they only have one node
for any particular I2C device.
--
Timur
On Fri, Nov 04, 2011 at 02:19:36PM -0400, Robert Sciuk wrote:
I *believe* you are not supposed to create separate nodes for reading
and writing. I know that's how I2C works, but I think the I2C layer
takes care of that for you.
If you look at other device trees, you'll see they
- 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
-Original Message-
From: Segher Boessenkool [mailto:seg...@kernel.crashing.org]
Sent: Thursday, November 03, 2011 5:22 PM
To: Robert Sciuk
Cc: devicetree-disc...@lists.ozlabs.org; linuxppc-dev@lists.ozlabs.org
Subject: Re: fpga driver on custom PPC target platform (P4080
13 matches
Mail list logo
