On Thu, Jan 20, 2011 at 1:24 AM, Nick Lee <[email protected]> wrote:
>> Make sure your using a dedicated interrupt for the mcp2515, the driver
>> won't work without an interrupt, and the at91 GPIO interrupts I messed
>> with, but couldn't get to work.
>
> Yes, I'd kind of come to the conclusion it was an interrupt issue too. Our
> board is wired up to use IRQ1, but the closest I can get to making it work
> (actually seeing the MCP assigned to an interrupt on /proc/interrupts and
> seeing it trigger) is to set the .irq value in the mcp setup structure to
> AT91SAM9260_ID_IRQ2 (which seems to come out as interrupt 31, which I'm sure
> isn't the one we want). What .irq value have you used?
>
> Ta,
>
> Nick
>
Nick, I'm using AT91SAM9260_ID_IRQ0 with something like this for the setup:
thanks,
Paul
static struct mcp251x_platform_data mcp251x_info = {
.oscillator_frequency = 20000000,
.model = CAN_MCP251X_MCP2515,
};
static struct spi_board_info ek_spi_devices[] = {
{
.modalias = "mcp251x",
.platform_data = &mcp251x_info1,
.max_speed_hz = 2*1000*1000,
.chip_select = 2,
.bus_num = 1,
.irq = AT91SAM9260_ID_IRQ0,
},
};
_______________________________________________
Socketcan-core mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/socketcan-core
