Searched refs:spi_new_device (Results 1 – 13 of 13) sorted by relevance
/linux/drivers/spi/ |
H A D | spi-altera-platform.c | 127 if (!spi_new_device(host, pdata->devices + i)) in altera_spi_probe()
|
H A D | spi-cs42l43.c | 440 if (!spi_new_device(priv->ctlr, ampl_info)) in cs42l43_spi_probe() 444 if (!spi_new_device(priv->ctlr, ampr_info)) in cs42l43_spi_probe()
|
H A D | spi-altera-dfl.c | 175 if (!spi_new_device(host, &board_info)) { in dfl_spi_altera_probe()
|
H A D | spi-lm70llp.c | 267 pp->spidev_lm70 = spi_new_device(pp->bitbang.ctlr, &pp->info); in spi_lm70llp_attach() 272 dev_warn(&pd->dev, "spi_new_device failed\n"); in spi_lm70llp_attach()
|
H A D | spi-butterfly.c | 266 pp->dataflash = spi_new_device(pp->bitbang.ctlr, &pp->info[0]); in butterfly_attach()
|
H A D | spi-ch341.c | 208 ch341->spidev = spi_new_device(ctrl, &chip); in ch341_probe()
|
H A D | spi-kspi2.c | 317 struct spi_device *device = spi_new_device(kspi->host, &info[i]); in kspi2_register_devices()
|
H A D | spi-intel.c | 1396 if (!spi_new_device(ispi->host, &chip)) in intel_spi_populate_chip() 1425 if (!spi_new_device(ispi->host, &chip)) in intel_spi_populate_chip()
|
/linux/drivers/media/pci/netup_unidvb/ |
H A D | netup_unidvb_spi.c | 210 if (!spi_new_device(ctlr, &netup_spi_board)) { in netup_spi_init()
|
/linux/drivers/platform/x86/x86-android-tablets/ |
H A D | core.c | 265 spi_devs[idx] = spi_new_device(controller, &board_info); in x86_instantiate_spi_dev()
|
/linux/drivers/staging/greybus/ |
H A D | spilib.c | 478 spidev = spi_new_device(ctlr, &spi_board); in gb_spi_setup_device()
|
/linux/drivers/media/pci/mgb4/ |
H A D | mgb4_core.c | 247 spi_dev = spi_new_device(ctlr, &spi_info); in init_spi()
|
/linux/include/linux/spi/ |
H A D | spi.h | 1620 * by spi_new_device(), and otherwise depends on board wiring. 1637 * spi_new_device() call, which happens after those controller drivers 1695 * use spi_new_device() to describe each device. You can also call 1712 spi_new_device(struct spi_controller *, struct spi_board_info *);
|