> // interrupt-parent = <>;
> // interrupts = <0 24 IRQ_TYPE_EDGE_FALLING>;
Not sure if you did represent these values correctly?!
I have for enc28j60:something like this:
interrupt-parent = <>;
interrupts = <1 IRQ_TYPE_EDGE_FALLING>;
Where <> is gpio chip name (the gpio port 2),
and <1
Using '_make nconfig_' I selected the following options:
(_Keep in mind I using an Altera/Intel Arria 10 SoC which uses
DesignWare hard SPI controllers. BUT the SPI controllers I'm concerned
with now are soft controllers defined in the FPGA code)_.
.config - Linux/arm
Hello John,
It seems that your target is configured correctly. Since you have all
the components you should and must have as SPI framework.
Namely I was looking for /sys/bus (since you must have an SPI bus
driver), and then /sys/class (since as my best understanding is that
SPI is a master/slave
But there are NO udev files for the SPI devices defined in the DTSI
file.
On 2021-03-18 17:12, jchludzinski via lists.yoctoproject.org wrote:
That's with:
root@arria10:~# lsmod
Module Size Used by
spi_altera 16384 0
spidev 20480 0
On
That's with:
root@arria10:~# lsmod
Module Size Used by
spi_altera 16384 0
spidev 20480 0
On 2021-03-18 17:07, jchludzinski via lists.yoctoproject.org wrote:
root@arria10:~# find /sys/ -name 'spi*'
/sys/kernel/debug/clk/spi_m_clk
root@arria10:~# find /sys/ -name 'spi*'
/sys/kernel/debug/clk/spi_m_clk
/sys/kernel/debug/tracing/events/spi
/sys/kernel/debug/tracing/events/spi/spi_controller_idle
/sys/kernel/debug/tracing/events/spi/spi_controller_busy
/sys/kernel/debug/tracing/events/spi/spi_message_submit
I am guessing here But what do you have while executing the
following command being in /sys
as root?
root@arm:/sys# find . -name spi*
Zee
___
On Wed, Mar 17, 2021 at 5:41 PM jchludzinski via
lists.yoctoproject.org
wrote:
>
> In the YOCTO/Linux source tree there's drivers/spi/ which
