digetx has quit [Remote host closed the connection]
digetx has joined #linux-sunxi
barni2000[m] has joined #linux-sunxi
apritzel has quit [Ping timeout: 480 seconds]
Schimsalabim has quit [Ping timeout: 480 seconds]
cyrevolt has joined #linux-sunxi
Schimsalabim has joined #linux-sunxi
ftg has quit [Read error: Connection reset by peer]
MasterR3C0RD has quit [Quit: Bye-bye!]
MasterR3C0RD has joined #linux-sunxi
vagrantc has quit [Quit: leaving]
Soupborsh has joined #linux-sunxi
exkc has joined #linux-sunxi
junari has joined #linux-sunxi
<junari>
apritzel: There were some electrically interesting usb-hubs on sale that had one USB3.0 port and 3xUSB2.0. In fact, the USB2 part of the upstream USB port was connected to a 4 port USB2.0 hub, and the USB3.0 part from the upstream port complemented one of the hub's downstream ports
<junari>
so, i think the can be independent
Daanct12 has joined #linux-sunxi
Danct12 has quit [Read error: Connection reset by peer]
hexdump0815 has joined #linux-sunxi
hexdump01 has quit [Ping timeout: 480 seconds]
JohnDoe_71Rus has joined #linux-sunxi
gsz has joined #linux-sunxi
Sensu_Bean has joined #linux-sunxi
Sensu_Be1 has quit [Read error: Connection reset by peer]
junari_ has joined #linux-sunxi
dfas has quit [Remote host closed the connection]
dfas has joined #linux-sunxi
junari has quit [Ping timeout: 480 seconds]
MasterR3C0RD is now known as Guest22512
MasterR3C0RD has joined #linux-sunxi
Guest22512 has quit [Ping timeout: 480 seconds]
dfas has quit [Remote host closed the connection]
Sensu_Be1 has joined #linux-sunxi
Sensu_Bean has quit [Read error: Connection reset by peer]
apritzel has joined #linux-sunxi
evgeny_boger has joined #linux-sunxi
apritzel has quit [Ping timeout: 480 seconds]
junari__ has joined #linux-sunxi
junari_ has quit [Ping timeout: 480 seconds]
digetx has quit [Remote host closed the connection]
warpme has joined #linux-sunxi
digetx has joined #linux-sunxi
warpme has quit []
digetx has quit [Remote host closed the connection]
digetx has joined #linux-sunxi
Schimsalabim has quit [Ping timeout: 480 seconds]
junari__ has quit [Remote host closed the connection]
Schimsalabim has joined #linux-sunxi
junari has joined #linux-sunxi
Schimsalabim has quit [Ping timeout: 480 seconds]
Schimsalabim has joined #linux-sunxi
wasutton3 has joined #linux-sunxi
wasutton- has quit [Read error: Connection reset by peer]
apritzel has joined #linux-sunxi
<dlan>
apritzel: hi, I kind of agree with you, on Radxa A5E, the schematics has wrong placement for D+/- of usb3, which should be pin USB2-DM/DP, not USB1-DM/DP..
wingrime-ww has quit [Quit: WeeChat 4.7.0]
wingrime-ww has joined #linux-sunxi
wingrime-ww has quit []
wingrime-ww has joined #linux-sunxi
junari has quit [Remote host closed the connection]
junari has joined #linux-sunxi
<apritzel>
dlan: well, as jakllsch said and I now learned, this doesn't really matter, it seems. And it means we get USB access already today
<apritzel>
dlan: can you say whether the "radxa-a5e_defconfig" name in U-Boot would be the right one for the board? That follows other Radxa boards in U-Boot, but drops the "cubie" name in there
warpme has joined #linux-sunxi
BroderTuck has joined #linux-sunxi
<dlan>
for board naming, I do not have strong preference, having "cubie" in there better help people to search, but that do break consistency..
<dlan>
by "get USB access", did you test a USB2.0 or USB3.0 interface? in this hw design, they come up with different USB controller..
<dlan>
I'm still a little bit confused..
<apritzel>
dlan: I mean the even without USB3.0 support (at the moment) we can use the USB connector, just as a USB 2.0 one. But much better than nothing, especially given that it's the only type A connector on the board
<apritzel>
and that also means that eventually even with PCIe support this USB port will keep working, again just as a USB 2.0 one
<apritzel>
BroderTuck: ah nice, I found the auxdisplay subsystem the other day, and was already wondering if that could be used (but wasn't aware at that series, so haven't checked)
<apritzel>
BroderTuck: feel free to explore that!
<dlan>
apritzel: oh, I see, so this is fine (and in the case with no USB3.0 support)..
<dlan>
and they can still have USB3.0 support (with PCIe disabled)?
<apritzel>
dlan: yes
<dlan>
it's complicated, and need to do some pre pin-mux (via GMA340)
<apritzel>
dlan: my plan was to probe a GPIO in U-Boot, to detect a M.2 card. Then change the DTB in memory accordingly, and program the mux
<dlan>
probe a gpio, then load m.2 dtbo conditionally? otherwise usb
<apritzel>
PCIE0-CLKREQN should be a good indicator, from what I could see
<dlan>
but for usb, you still have two choice? USB2.0 or USB3.0, since they will go with different USB controller
<apritzel>
and I would rather skip any DT overlays, and patch the DTB in U-Boot code directly
<dlan>
I mean, to enable USB2.0 or USB3.0, you will have to enable different USB driver..
<apritzel>
the idea would be to have the DT as it is, which would always give USB2.0. Then eventually have a PCIe DT node, and a USB3.0 DT node. Each is marked as disabled, and U-Boot just toggles the one used
<apritzel>
so if there is a M.2 card in the slot, you will get PCIe plus USB 2.0, if not, you would get USB3.0 + USB 2.0
wingrime-ww has quit [Quit: WeeChat 4.7.0]
wingrime-ww has joined #linux-sunxi
<dlan>
sounds good plan
paulk-bis has quit []
paulk has joined #linux-sunxi
digetx has quit [Remote host closed the connection]
<apritzel>
BroderTuck: that looks reasonable. Maybe you need to do something about PB3 as well? The BSP DT has this as "vfd_stb_gpio".
warpme has joined #linux-sunxi
<BroderTuck>
Well, the descriptions talk about 2-wire i2c-gpio and 3-wire spi, and iirc the a523 page mentions that spi isn't quite working yet
<apritzel>
No, it's definitely bitbanged I2C, but I meant PB3 might be some enable GPIO or so (I guess "standby"). So try to toggle it?
gsz has quit [Ping timeout: 480 seconds]
<BroderTuck>
I forget, how do you calculate gpio numbers?
<apritzel>
PA0=0 PB0=32 PB1=33 PB3=35 PC0=64 ...
<apritzel>
BroderTuck: you could also do it in U-Boot: => gpio set PB3
warpme has quit [Ping timeout: 480 seconds]
digetx has quit [Remote host closed the connection]
wingrime-ww has quit [Quit: WeeChat 4.7.0]
wingrime-ww has joined #linux-sunxi
<BroderTuck>
Tried adding that to my boot.scr, no change
digetx has joined #linux-sunxi
gsz has joined #linux-sunxi
<BroderTuck>
Wonder if the @24 is really correct, taken from another device overlay
digetx has quit [Remote host closed the connection]
digetx has joined #linux-sunxi
gsz has quit [Ping timeout: 480 seconds]
digetx has quit [Quit: No Ping reply in 180 seconds.]
junari has quit []
digetx has joined #linux-sunxi
paulk-bis has joined #linux-sunxi
paulk has quit [Ping timeout: 480 seconds]
<apritzel>
mmh, that's weird, the device is technically not really I2C, it's just some serial interface copying some of the I2C properties. But I don't see any address mentioned in the datasheet
<jakllsch>
RSB?
<apritzel>
jakllsch: no, just a data and a clock line, defined by some timing diagram in the datasheet (which happens to be close to I2C). But it's not a bus, so no need for any addresses
<apritzel>
BroderTuck: is the TM1628 actually supported as an I2C device by this driver? I only see the compatible under spi_of_match[] ...
<apritzel>
maybe try spi-gpio?
<apritzel>
yeah, looks like the TM1650, which is listed under i2c_of_match, describes a serial protocol compatible with I2C (with ACKs, an address, and so on)
<apritzel>
but for the TM1628 you probably need to disguise this as a bitbanged SPI device, with just MOSI and SCLK
digetx has quit [Remote host closed the connection]
<apritzel>
jakllsch: so I was wrong, the TM1628 is using a simple serial protocol, but it's closer to one-way SPI than to I2C
digetx has joined #linux-sunxi
digetx has quit [Quit: No Ping reply in 180 seconds.]
<apritzel>
BroderTuck: nice, thanks! Out of curiosity, where did you get the LED symbols mapping from?
<BroderTuck>
The order of the icons is just a placeholder for now, to be fixed once things start working.
<BroderTuck>
The symbol names, "functions", is left-to-right from a marketing image for the box, and hunting for matching texts in other device overlays in the tm16xx repository
<apritzel>
ah, I see
<apritzel>
I guess because the interface is write only there is no way for the driver to verify the communication actually works ...
<BroderTuck>
Not sure that PB3 is really cs as I put it v2. Also noticed that other dt fragments tend to have it as active_low
<BroderTuck>
But tested that to no avail
<apritzel>
do you have the BSP image still available? You could check the state of the pins (in sysfs) there, while the display is running
<BroderTuck>
The android stopped working a few days ago, sadly
<apritzel>
I will have a look later, last time I checked it still booted for me
<apritzel>
also have at least two other boxes with similar displays
vagrantc has joined #linux-sunxi
colinsane has quit []
Sensu_Be1 has quit [Read error: Connection reset by peer]
Sensu_Bean has joined #linux-sunxi
colinsane has joined #linux-sunxi
paulk-bis has quit []
paulk has joined #linux-sunxi
colinsane1 has joined #linux-sunxi
colinsane has quit [Ping timeout: 480 seconds]
digetx has quit [Quit: No Ping reply in 180 seconds.]
gsz has joined #linux-sunxi
digetx has joined #linux-sunxi
apritzel has quit [Ping timeout: 480 seconds]
Schimsalabim has quit [Read error: Connection reset by peer]
Schimsalabim has joined #linux-sunxi
hazardchem has quit [Read error: Connection reset by peer]
hazardchem has joined #linux-sunxi
Schimsalabim has quit [Ping timeout: 480 seconds]
Schimsalabim has joined #linux-sunxi
<BroderTuck>
In fact, the pro+ display fits the template-display-type5.inc template
apritzel has joined #linux-sunxi
ftg has joined #linux-sunxi
apritzel has quit [Ping timeout: 480 seconds]
Sensu_Be1 has joined #linux-sunxi
Sensu_Bean has quit [Read error: Connection reset by peer]
Sensu_Bean has joined #linux-sunxi
Sensu_Be1 has quit [Remote host closed the connection]
hazardchem has quit [Read error: Connection reset by peer]
hazardchem has joined #linux-sunxi
Sensu_Be1 has joined #linux-sunxi
Sensu_Bean has quit [Read error: Connection reset by peer]
JohnDoe_71Rus has quit [Quit: KVIrc KVIrc Quasar 5.2.6, revision: 5.2.6+git-7614-6f23368f1, build type: debug, sources date: 20160102, built on: 2025-03-30 13:34:35 UTC 5.2.6+git-7614-]
tlwoerner_ has joined #linux-sunxi
tlwoerner has quit [Ping timeout: 480 seconds]
BroderTuck has quit [Ping timeout: 480 seconds]
gsz has quit [Ping timeout: 480 seconds]
Sensu_Bean has joined #linux-sunxi
Sensu_Be1 has quit [Ping timeout: 480 seconds]
digetx has quit [Remote host closed the connection]
apritzel has joined #linux-sunxi
digetx has joined #linux-sunxi
Sensu_Be1 has joined #linux-sunxi
Sensu_Bean has quit [Read error: Connection reset by peer]
Sensu_Bean has joined #linux-sunxi
Sensu_Be1 has quit [Ping timeout: 480 seconds]
BroderTuck has joined #linux-sunxi
BroderTuck has quit []
sdfgsdfs has joined #linux-sunxi
Schimsalabim has quit [Ping timeout: 480 seconds]
evgeny_boger has quit [Ping timeout: 480 seconds]
evgeny_boger has joined #linux-sunxi
<apritzel>
BroderTuck: well done, you were so close! According to the running Android system, PB3 is low, so the CS is ACTIVE_LOW. And all GPIOs are push-pull, so no pull-ups or so
<apritzel>
so use just GPIO_ACTIVE_HIGH for PB1 and PB2, and GPIO_ACTIVE_LOW for PB3 (remove GPIO_OPEN_DRAIN)
<apritzel>
that worked for me. It's all a mess, because the mapping is completely off, but sounds like a nice puzzle to get this sorted