17:41 <re_irc> <@dirbaio:matrix.org> yeah apparently I was using 0 and 2

17:41 <re_irc> <@dirbaio:matrix.org> 0 reads shifted garbeage, 2 reads 0xFF

17:41 <re_irc> <@adamgreig:matrix.org> it's not often documented as literally "mode 0" because it could be a bit ambiguous but the timing diagram usually tells the story

17:41 <re_irc> <@adamgreig:matrix.org> sigh

17:41 <re_irc> <@dirbaio:matrix.org> 2 does sample on falling edge, but it seems the device needs the initial dummy rising edge

17:41 <re_irc> <@adamgreig:matrix.org> no easy way to change cpha

17:42 <re_irc> <@dirbaio:matrix.org> it's right there documented https://docs.rs/ftd2xx-embedded-hal/0.9.1/ftd2xx_embedded_hal/struct.Spi.html#method.set_clock_polarity

17:42 <re_irc> <@dirbaio:matrix.org> I just suck at reading 🤣

17:44 <re_irc> <@dirbaio:matrix.org> The demo board does support i2c too, but needs changing like 7x 0201 0-ohm resistors

17:46 <re_irc> <@adamgreig:matrix.org> lol that's helpful

17:47 <re_irc> <@dirbaio:matrix.org> just ST being ST

17:53 <re_irc> <@almindor:matrix.org> introducing: https://crates.io/crates/mipidsi

18:51 <re_irc> <@firefrommoonlight:matrix.org> I can relate re mild frustration on Spi mode documentation across periphs. Also, some use mode terminology; others pol and phase. If you have multiple devices on a bus, hope there's a mode they all support

18:53 <re_irc> <@firefrommoonlight:matrix.org> MCU-side, I've set up the API so the mode is a struct of polarity and phase tuples, with optional constructors of `mode0()`, `mode1()` etc. If I'm confused by a datasheet's description of mode, I try modes and see which work

18:54 <re_irc> <@firefrommoonlight:matrix.org> I recall sometimes the terminology re phase and polarity is sometimes inconsistent, but can't recall what's confused me in the past

18:57 <re_irc> <@adamgreig:matrix.org> multiple devices on a bus don't need to use the same mode

18:57 <re_irc> <@adamgreig:matrix.org> they'll ignore anything while nto selected

18:58 <re_irc> <@adamgreig:matrix.org> (does mean you have to reconfigure the spi peripheral between devices though)

18:58 <re_irc> <@firefrommoonlight:matrix.org> Oh - reconfiguring the periph could be an option - good point

18:58 <re_irc> <@firefrommoonlight:matrix.org> I should probably add a method to do that

18:59 <re_irc> <@firefrommoonlight:matrix.org> I have a comment in one of my projects along the line of "Device A seems to work with modes A and B. Device B works with all modes except B. So, we use A

19:09 <re_irc> <@almindor:matrix.org> yeah that's how we implemented SPI sharing here: https://github.com/riscv-rust/e310x-hal/blob/master/src/spi.rs reconfigures each time you switch, seems to work good although I have only tested on mode0 both

19:10 <re_irc> <@almindor:matrix.org> each time a shared device on the bus needs to send or receive it calls configure on the bus e.g. https://github.com/riscv-rust/e310x-hal/blob/master/src/spi/shared_device.rs#L84

19:10 <re_irc> <@dirbaio:matrix.org> even different freqs! neat!

19:10 <re_irc> <@almindor:matrix.org> yeah it works fine with my usb host on 100khz and display at 54mhz

19:11 <re_irc> <@almindor:matrix.org> there are timing issues outside of SPI tho e.g. if the display resets (even soft reset) and you don't give it a delay it might register some stuff and go wonky even if CS is high