Skip to content

Conversation

@sibradzic
Copy link

@sibradzic sibradzic commented Jul 8, 2019

This introduces GPIO offset detection by checking the dir name starting with
gpiochip[0-9]* found in /sys/bus/gpio/devices/gpiochip0/../gpio/.

The change is tested and confirmed working on Debian Buster 10 and Raspbian 9.9,
on both Raspberry Pi 3B and 3B+

This introduces GPIO offset detection by checking the dir name starting with
gpiochip[0-9]* found in /sys/bus/gpio/devices/gpiochip0/../gpio/.

Thec change is tested and confirmed working on Debian Buster 10 and Raspbian 9.9,
on boht Raspberry Pi 3B and 3B+
@illuusio
Copy link

Fixes working also with openSUSE Leap 15.1 without it doesn't work.

@sibradzic
Copy link
Author

@illuusio a bit off-topic, but what is the state of device-tree spi support on OpenSUSE Leap? I am asking because it gets quite painful in Debian Buster, relying on hacking and re-compiling in-kernel RPi3+ device-tree...

@illuusio
Copy link

@illuusio a bit off-topic, but what is the state of device-tree spi support on OpenSUSE Leap? I am asking because it gets quite painful in Debian Buster, relying on hacking and re-compiling in-kernel RPi3+ device-tree...

If you mean can I enable SPI with 'dtparam=spi' in 'config.txt'? Yes it's working as expected.

@illuusio
Copy link

illuusio commented Aug 6, 2019

If you mean that new kernel tainting spidev not supported then is in all that bad shape as it is in Debian.

@sibradzic
Copy link
Author

Well, in Debian 10 (Buster) kernel 4.19 spidev is ignoring SPI device cause it ain't in device tree. I had to hack & re-compile device tree to enable the thing. The dtparam=spi in config does nothing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants