Yocto / SPIDEV

Products Support DragonBoard410c
#1

I’m adding “SPIDEV” reference to the dtb as found here: EnableSPI

Any suggestions on how to make things happy?

Sep 23 22:26:28 dragonboard-410c kernel:
Sep 23 22:26:28 dragonboard-410c kernel: [[0;1;39mCPU: 0 PID: 1707 Comm: systemd-udevd Tainted: G W 4.4.9+linaro #1[[0m
Sep 23 22:26:28 dragonboard-410c kernel: [[0;1;39mHardware name: Qualcomm Technologies, Inc. APQ 8016 SBC (DT)[[0m
Sep 23 22:26:28 dragonboard-410c kernel: [[0;1;39mtask: ffffffc035ae6000 ti: ffffffc035a98000 task.ti: ffffffc035a98000[[0m
Sep 23 22:26:28 dragonboard-410c kernel: [[0;1;39mPC is at spidev_probe+0x1a4/0x210 [spidev][[0m
Sep 23 22:26:28 dragonboard-410c kernel: [[0;1;39mLR is at spidev_probe+0x1a0/0x210 [spidev][[0m
Sep 23 22:26:28 dragonboard-410c kernel: [[0;1;39mpc : [<ffffffbffc07932c>] lr : [<ffffffbffc079328>] pstate: 60000145[[0m
Sep 23 22:26:28 dragonboard-410c kernel: [[0;1;39msp : ffffffc035a9ba90[[0m
Sep 23 22:26:28 dragonboard-410c kernel: [[0;1;39mx29: ffffffc035a9ba90 x28: 0000000000000000 [[0m
Sep 23 22:26:28 dragonboard-410c kernel: [[0;1;39mx27: 0000000000000124 x26: ffffffc033963000 [[0m
Sep 23 22:26:28 dragonboard-410c kernel: [[0;1;39mx25: 0000000000000039 x24: ffffffbffc07ab00 [[0m
Sep 23 22:26:28 dragonboard-410c kernel: [[0;1;39mx23: ffffffc000dd5000 x22: ffffffc000d812a0 [[0m
Sep 23 22:26:28 dragonboard-410c kernel: [[0;1;39mx21: 0000000000000000 x20: ffffffc03620b800 [[0m
Sep 23 22:26:28 dragonboard-410c kernel: [[0;1;39mx19: ffffffbffc07a598 x18: ffffffc080dfb24f [[0m
Sep 23 22:26:28 dragonboard-410c kernel: [[0;1;39mx17: 00000000004b06c0 x16: 0000000000000000 [[0m
Sep 23 22:26:28 dragonboard-410c kernel: [[0;1;39mx15: ffffffc000dfb25d x14: 0000000000008000 [[0m
Sep 23 22:26:28 dragonboard-410c kernel: [[0;1;39mx13: ffffffc000e01688 x12: 0000000000000010 [[0m
Sep 23 22:26:28 dragonboard-410c kernel: [[0;1;39mx11: 0101010101010101 x10: ff7f7f7f7f7f7f7f [[0m
Sep 23 22:26:28 dragonboard-410c kernel: [[0;1;39mx9 : ca02feff02fefeff x8 : 7f7f7f7f7f7f7f7f [[0m
Sep 23 22:26:28 dragonboard-410c kernel: [[0;1;39mx7 : 01fefefefeff7564 x6 : 0000808080808000 [[0m
Sep 23 22:26:28 dragonboard-410c kernel: [[0;1;39mx5 : 0080808080800000 x4 : 0000000000000000 [[0m
Sep 23 22:26:28 dragonboard-410c kernel: [[0;1;39mx3 : ffffffbffc07a728 x2 : 000000000000aa66 [[0m
Sep 23 22:26:28 dragonboard-410c kernel: [[0;1;39mx1 : ffffffc035a98000 x0 : 0000000000000000 [[0m
Sep 23 22:26:28 dragonboard-410c kernel:
Sep 23 22:26:28 dragonboard-410c kernel: [[0;1;39m—[ end trace efcc8c39fab28eef ]—[[0m
Sep 23 22:26:28 dragonboard-410c kernel: [[0;1;31mCall trace:[[0m
Sep 23 22:26:28 dragonboard-410c kernel: [[0;1;39m[<ffffffbffc07932c>] spidev_probe+0x1a4/0x210 [spidev][[0m
Sep 23 22:26:28 dragonboard-410c kernel: [[0;1;39m[<ffffffc0004fcba4>] spi_drv_probe+0x6c/0xe0[[0m
Sep 23 22:26:28 dragonboard-410c kernel: [[0;1;39m[<ffffffc0004a00fc>] driver_probe_device+0x21c/0x480[[0m
Sep 23 22:26:28 dragonboard-410c kernel: [[0;1;39m[<ffffffc0004a03fc>] __driver_attach+0x9c/0xa0[[0m
Sep 23 22:26:28 dragonboard-410c kernel: [[0;1;39m[<ffffffc00049deb8>] bus_for_each_dev+0x60/0xa0[[0m
Sep 23 22:26:28 dragonboard-410c kernel: [[0;1;39m[<ffffffc00049f8b0>] driver_attach+0x20/0x28[[0m
Sep 23 22:26:28 dragonboard-410c kernel: [[0;1;39m[<ffffffc00049f420>] bus_add_driver+0x208/0x290[[0m
Sep 23 22:26:28 dragonboard-410c kernel: [[0;1;39m[<ffffffc0004a0bc0>] driver_register+0x60/0xf8[[0m
Sep 23 22:26:28 dragonboard-410c kernel: [[0;1;39m[<ffffffc0004fcae0>] __spi_register_driver+0x58/0x60[[0m
Sep 23 22:26:28 dragonboard-410c kernel: [[0;1;39m[<ffffffbffc07d088>] spidev_init+0x88/0xf0 [spidev][[0m
Sep 23 22:26:28 dragonboard-410c kernel: [[0;1;39m[<ffffffc000082980>] do_one_initcall+0xd0/0x1d8[[0m
Sep 23 22:26:28 dragonboard-410c kernel: [[0;1;39m[<ffffffc000157774>] do_init_module+0x60/0x1bc[[0m
Sep 23 22:26:28 dragonboard-410c kernel: [[0;1;39m[<ffffffc00012a39c>] load_module+0x1aac/0x2008[[0m
Sep 23 22:26:28 dragonboard-410c kernel: [[0;1;39m[<ffffffc00012abc0>] SyS_finit_module+0xe0/0x110[[0m
Sep 23 22:26:28 dragonboard-410c kernel: [[0;1;39m[<ffffffc000085cb0>] el0_svc_naked+0x24/0x28[[0m

#2

Hi @Joel:

There are a couple long involved discussions on getting SPI running under Debian in the forums, we do know that SPI now works under Debian (but it didn’t always). Take a look through the forums and see if any of the solutions and discussions apply to your case. Search the 96Boards forums for “ljking SPI” and you will find several discussions.

Full Disclosure: I am an employee of Qualcomm Canada, any opinions expressed in this or any other post may not reflect the opinions of my employer.

#3

Well SPI works despite the “alarming” output. Not sure how to suppress the errors in the system log, as it’s the first thing people look at when they review logs.