For a SPI device with
chipselect C on bus B, you should see:

/dev/spidevB.C ... character special device, major number 153 with
a dynamically chosen minor device number. This is the node
that userspace programs will open, created by "udev" or "mdev".

/sys/devices/.../spiB.C ... as usual, the SPI device node will
be a child of its SPI master controller.

/sys/class/spidev/spidevB.C ... created when the "spidev" driver
binds to that device. (Directory or symlink, based on whether
or not you enabled the "deprecated sysfs files" Kconfig option.)

Do not try to manage the /dev character device special file nodes by hand.
That's error prone, and you'd need to pay careful attention to system
security issues; udev/mdev should already be configured securely.

static struct spi_board_info ek_spi_devices[] = {
#if !defined(CONFIG_MMC_AT91)
{ /* DataFlash chip */
.modalias = "mtd_dataflash",
.chip_select = 1,
.max_speed_hz = 15 * 1000 * 1000,
.bus_num = 0,
},
#if defined(CONFIG_MTD_AT91_DATAFLASH_CARD)
{ /* DataFlash card */
.modalias = "mtd_dataflash",
.chip_select = 0,
.max_speed_hz = 15 * 1000 * 1000,
.bus_num = 0,
},
#endif
#endif


#if defined(CONFIG_SND_AT73C213) || defined(CONFIG_SND_AT73C213_MODULE)
{ /* AT73C213 DAC */
.modalias = "at73c213",
.chip_select = 0,
.max_speed_hz = 10 * 1000 * 1000,
.bus_num = 1,
.mode = SPI_MODE_1,
.platform_data = &at73c213_data,
},
#endif
{ /* my SPI*/
.modalias = "spidev",
.chip_select = 2,
.controller_data = AT91_PIN_PC5,
.max_speed_hz = 1 * 1000 * 1000,
.bus_num = 1,
},
};

armets:~# ls /dev/sp* -l
crw-rw---- 1 root root 153, 0 Jan 1 00:00 /dev/spidev1.2