You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am not sure if here is the right place to ask this. If I am in a wrong place, please advise me.
I have a Jetson Xavier NX that runs Yocto linux with the branch of oe4t-patches-l4t-r32.5 of linux-tegra-4.9.
And I have applied rt patches.
SPI master runs in the NX and needs to read multiple 2-byte registers one-by-one. To reduce whole transmission time, I hope to use ioctl(fd, SPI_IOC_MESSAGE(len), buf) call.
My problem is there is a big delay after transfer the data. It is about 100us for each 2 bytes data tranmission.
In the above, yellow is SCK and cyan is CS. First two transmissions use SPI_IOC_MESSAGE(1) in ioctl call and 3rd to 5th transmission uses SPI_IOC_MESSAGE(3) where each message is 2 bytes. The delay is too big.
I found this part of the code of spi-tegra114.c is one that takes long time:
I am not sure if here is the right place to ask this. If I am in a wrong place, please advise me.
I have a Jetson Xavier NX that runs Yocto linux with the branch of oe4t-patches-l4t-r32.5 of linux-tegra-4.9.
And I have applied rt patches.
SPI master runs in the NX and needs to read multiple 2-byte registers one-by-one. To reduce whole transmission time, I hope to use
ioctl(fd, SPI_IOC_MESSAGE(len), buf)
call.My problem is there is a big delay after transfer the data. It is about 100us for each 2 bytes data tranmission.
In the above, yellow is SCK and cyan is CS. First two transmissions use SPI_IOC_MESSAGE(1) in ioctl call and 3rd to 5th transmission uses SPI_IOC_MESSAGE(3) where each message is 2 bytes. The delay is too big.
I found this part of the code of spi-tegra114.c is one that takes long time:
I tried either way and they are the same. Why does this take a long time of more than 50 us?
I measured the time by
ktime_get_ns()
. This is the sample:The text was updated successfully, but these errors were encountered: