It now works, in the dts
interrupt-controller = < &gpt6 >; // Use GPT6 as
should have been
interrupt-parent = < &gpt6 >; // Use GPT6 as
On Tue, Jul 7, 2009 at 5:57 PM, Grant Likely wrote:
> On Tue, Jul 7, 2009 at 8:31 AM, Henk Stegeman wrote:
>> I tried to make use of the irq-controller
On Tue, Jul 7, 2009 at 8:31 AM, Henk Stegeman wrote:
> I tried to make use of the irq-controller mode of the GPT as
> suggested, however I'm not getting the IRQ.
> Does anyone have an idea what I could be missing? (I've been testing
> with 2.6.30).
Make sure the 5200 general purpose timer driver i
I tried to make use of the irq-controller mode of the GPT as
suggested, however I'm not getting the IRQ.
Does anyone have an idea what I could be missing? (I've been testing
with 2.6.30).
The driver reports from it's probe:
[1.502853] spi_master spi32766.0 Unable to get sample IRQ from of
My
Now my driver gets probed.
This "modalias" error was due to wrong "compatible" attribute of
my of node.
But I still need to have the call to of_register_spi_devices().
The attached patch shows what I mean.
rg
kd
Grant Likely wrote:
On Mon, Jun 15, 2009 at 10:36 AM, Kári
Davíðsson wrote:
Is
On Mon, Jun 15, 2009 at 10:36 AM, Kári
Davíðsson wrote:
> Is this true?
>
> Grant Likely wrote:
>>
>> Yes, this is right. The psc_spi driver automatically registers all
>> spi children that it finds in the device tree onto the SPI bus.
>> Therefore registering an spi_driver() is the right thing to
Is this true?
Grant Likely wrote:
Yes, this is right. The psc_spi driver automatically registers all
spi children that it finds in the device tree onto the SPI bus.
Therefore registering an spi_driver() is the right thing to do.
I am writing an SPI protocol driver and I find that my driver
i
I'm trying to do the same sort of thing
On Fri, Feb 13, 2009 at 3:40 AM, Henk Stegeman https://ozlabs.org/mailman/listinfo/linuxppc-dev>> wrote:
> I'm busy adding support for slave deviced behind mpc52xx-psc-spi.
> One complication I have is that my SPI slave device has an interrupt output
> to
Thanks Greg,
I'm having success more success with the driver now,
The device gets nicely probed and the probe function gets the properties
from the device tree,
The following patch from Anton Vorontsov:
http://kerneltrap.org/mailarchive/linux-kernel/2008/5/23/1922744
Was very useful as exampl
On Fri, Feb 13, 2009 at 3:40 AM, Henk Stegeman wrote:
> I'm busy adding support for slave deviced behind mpc52xx-psc-spi.
> One complication I have is that my SPI slave device has an interrupt output
> to the CPU.
> My idea is to add it as a gpios property in the slave device's
> configuration:
>
I'm busy adding support for slave deviced behind mpc52xx-psc-spi.
One complication I have is that my SPI slave device has an interrupt output
to the CPU.
My idea is to add it as a gpios property in the slave device's
configuration:
s...@2400 {// PSC3 (SPI IF to the IO-controller )
On Wed, Oct 29, 2008 at 7:43 AM, Henk Stegeman <[EMAIL PROTECTED]> wrote:
> ..
> ..
> In my dts
>
> I have my chipselect defined as follows:
>
> gpt4: [EMAIL PROTECTED] {// General Purpose Timer GPT4 in GPIO
> mode for
> SMC4000IO chip select.
> compatible = "fsl,mpc5200b-g
..
..
In my dts
I have my chipselect defined as follows:
gpt4: [EMAIL PROTECTED] {// General Purpose Timer GPT4 in GPIO mode
for
SMC4000IO chip select.
compatible = "fsl,mpc5200b-gpt-gpio","fsl,mpc5200-gpt-gpio";
cell-index = <4>;
reg = <0x640 0x10
12 matches
Mail list logo
