RE: SocketCAN on Intel Edison with MCP 2515

["Rost, Martin" <Martin.Rost@tonfunk.de>]

Hi,
	
> However, can0 is not recognized:
> 
> can0: ERROR while getting interface flags: No such device
> 
> One thing I am confused about is how the socketCAN drivers know which
> SPI bus to use? I see that this information is provided in the
> bcm2708.c source file for the RPI_CANBUS
> (http://www.elinux.org/RPi_CANBus) project in the config_spi function.
> Is there something similar I would need to do?
> 
Well, I don't know about Yocto or the RPI, but on our Tegra t30 we have a 
board file arch/arm/mach_tegra/board-colibri_t30.c which contains:

static struct mcp251x_platform_data mcp251x_pdata = {
	.board_specific_setup	= colibri_t20_mcp2515_setup,
	.oscillator_frequency	= 16000000,
	.power_enable		= NULL,
	.transceiver_enable	= NULL
};

static struct spi_board_info mcp251x_board_info[] = {
	{
		.bus_num		= 0,
		.chip_select		= 0,
		.max_speed_hz		= 10000000,
		.modalias		= "mcp2515",
		.platform_data		= &mcp251x_pdata,
	},
};

You probably want to use .bus_num=4 or 5.

> #SSP5_RXD
> #SSP5_CLK
> #SSP5_TXD
> #SSP5_CS

For us, these are configured in arch/arm/mach_tegra/board-colibri_t30-pinmux.c

> So in short I think something is breaking in my SPI communication
> configuration but I'm not sure exactly where to start. Anything you
> could do to point me in the right direction towards the appropriate
> documentation would be appreciated.

Maybe that's how it works in Yocto, too?

Regards,
M.