00:59 <Jookia> time to head back to the u-boot clock mines today :D

01:25 <tokyovigilante> apritzel: sorry without CLDO4 referenced (for vmmc) it doesn't work. ALDO1 doesn't actually need to be referenced for vqmmc, but is defined in the vendor BSP @1.8v which is why we have it there initially I think.

01:26 <tokyovigilante> Have read the SD spec in part, but is the inference that the VCC and IO supplies are the same rail, initially 3.3v and then switched to 1.8v for LVS, or is it two separate supplies, with the 1.8v only enabled if LVS is supported and negotiated?

01:26 <tokyovigilante> or is it implementation-specific?

01:42 <tokyovigilante> ALDO1@3.3v for vmmc doesn't work either - [ 2.012045] sunxi-mmc 4022000.mmc: no support for card's volts

01:42 <tokyovigilante> I do note I've been seeing but politely ignoring this about MMC1 for the wifi - [ 2.213622] sunxi-mmc 4021000.mmc: card claims to support voltages below defined range

01:53 <tokyovigilante> Ah here we go, ALDO1@3.3v does work with no-1-8-v set

02:01 <tokyovigilante> can't get rid of the requirement for that extra regulator though

02:03 <tokyovigilante> [ 2.022330] sunxi-mmc 4022000.mmc: exceeding card's volts

02:03 <tokyovigilante> That's a new one...

02:08 <Jookia> card's volts!

02:35 <tokyovigilante> Vexing, but it seems for LVS, there must be a VCC/VDD which stays at 3.3v, and a vqmcc/VCC-IO/VDD2 which starts at 3.3v then is switched to 1.8v for LVS. But in the vendor BSP clearly ALDO1 is vqmmc, and is reported running at 1.8v, ie ALDO1 must be vqmmc, so then it can't be vmmc, but where is vmmc? Maybe I will just take the board to work and CT it to get traces ;)

05:30 <Jookia> okay, i figured out how to bind device tree clocks correctly. the allwinner tree is sloowly happening: https://paste.xogium.me/Ig.txt

05:31 <Jookia> (ignore the numbers)

07:48 <tokyovigilante> Jookia: nice!

07:50 <Jookia> sloowly getting there

07:53 <Jookia> not even sure how this will help the de2 clocking situation tbh

07:58 <Jookia> apritzel may have to remind me :) i recall doing this in part so we can ask for specific clocks

10:06 <apritzel> tokyovigilante: still around?

10:06 <apritzel> so for all Allwinner boards so far we go with not specifying vqmmc explicitly, which means it's the same as vmmc, which must be 3.3V

10:07 <apritzel> and all SD cards must work with this setting, although this limits the speed modes available

10:08 <apritzel> so I wonder if we should just drop vqmmc, but keep aldo1 at 1.8V, as always-on?

10:09 <gnarface> apritzel: does that sound related to why i couldn't get sd-uhs-sdr104 acknowledged by my pine64+ board?

10:09 <apritzel> as for why the BSP runs at 1.8V: this is the *runtime* value, for when the board is up and running, right? So it could have been switched to that value before?

10:10 <apritzel> gnarface: that was for WiFi, right?

10:10 <gnarface> apritzel: yea, the sdio wifi module add-on

10:10 <tokyovigilante> apritzel: yup, was hoping you might pop in. Yeah absolutely, there is obviously more to unpack with the regulators, so would be good to just drop it for now.

10:11 <tokyovigilante> apritzel: correct, so I'm assuming it's capable of the 3.3v->1.8v switch, just not sure how

10:11 <apritzel> gnarface: in general UHS requires 1.8V, and it requires a *switchable* supply for that, per the spec

10:11 <apritzel> tokyovigilante: one way could be re-programming aldo1, but it might also be fixed at 1.8V, and they have a separate voltage switch (controlled by PE4?)

10:12 <gnarface> apritzel: that was a yes, right?

10:13 <tokyovigilante> no combination of regulators I've been able to arrive at allows the card to work with that extra vcc_3v3_sd2 regulator defined *AND* referencing it in the mmc2, ie I've had to use vmmc = &CLDO4; which of course makes no sense and doesn't look good in the commit message

10:13 <tokyovigilante> I'll try again with just 3.3v

10:14 <apritzel> gnarface: I think on the Pine64 PortG is already 1.8V, and SDIO and eMMC are slightly different from SD, in that you can drive them just with 1.8V signalling voltage

10:14 <gnarface> hmm

10:14 <apritzel> tokyovigilante: but vmmc using CLDO4 looks absolutely right, this must always be 3.3V, regardless of the speed mode

10:15 <apritzel> gnarface: that's why we can use advanced speed modes easily for all the eMMC devices: they are just hardwired to some 1.8V rail, and that's it

10:15 <tokyovigilante> apritzel: yup have figured that out, but just unclear why I need that extra regulator defined in that case.

10:16 <apritzel> tokyovigilante: so does it work if you omit vqmmc? And maybe have ALDO1 as always-on?

10:16 <apritzel> I would feel best with not specifying vqmmc at all, as we simply don't know yet what it is

10:17 <apritzel> and it looks like aldo1 has a play in here, IIUC you said SD2 doesn't work if that is not enabled?

10:17 <gnarface> apritzel: aah, i see, thanks

10:20 <apritzel> gnarface: so I am not even sure those Wifi modules support the advanced speed modes, the datasheet didn't mention them, and it shouldn't really matter, as the 100 MBit/s should suffice for those WiFi speeds it supports

10:20 <tokyovigilante> sorry no it works fine with just vmmc defined, I've disabled ALDO1 now and no problems

10:21 <apritzel> ah, that's great!

10:21 <apritzel> tokyovigilante: what is your SD card? Is it a UHS capable one (should have this "U" style logo then)

10:21 <tokyovigilante> UHS-I yup

10:22 <apritzel> I wonder if those SD cards actually tolerate being run with always 1.8V on the signal lines

10:22 <apritzel> even though this is not what the spec says

10:22 <tokyovigilante> It's a newish Samsung, have given it a flogging, thats for sure