00:35 <smaeul> that boot log shows raw NAND, not eMMC; and sboot is the "secure" boot0, which implies you should look for TOC0, not eGON

00:40 <smaeul> I don't have any A100/A133 devices to test the mkimage TOC0 code on, but my guess is that it will work

01:29 <ItsKaitlyn03> ohh...

01:34 <ItsKaitlyn03> whats the toc0 header look like?

03:31 <MoeIcenowy> BTW I think tablets now usually come with TOC0 bootloader

03:31 <MoeIcenowy> even if it's not locked

12:38 <DarkNeutrino> Hi folks. A question. I have 2 gpios that are used to enable Wifi power and the wakeup. The WiFi works when i enable the GPIOs like this: https://pastebin.com/F5dKEUvn but im well aware this is not right and i cant seem to find any proper way of actually controling these GPIOs without the gpio-led driver. The actual wifi driver is out of tree. Wifi is RTL8189FTV and the driver is here https://github.com/jwrdegoede/rtl8189ES_li

12:40 <Jookia> DarkNeutrino: usually you specify the gpios directy in the device tree node for the device, such as the rtl8189ftv. for power you create a regulator node and specify that for the wifi node

12:41 <DarkNeutrino> Do you have any example of how that should look exactly ?

12:42 <Jookia> it depends driver to driver, you would have to see what compatibles that driver supports

12:43 <Jookia> try and find a board tree that uses this driver and supports the features you use

12:45 <Jookia> i think that driver may relay on fex variables like wl_reg_on and wl_host_wake

12:46 <Jookia> maybe a pinctrl could work for this? not sure

12:49 <DarkNeutrino> Seems like few boards use similar driver. They just specify a node in the mmc node where they add interrupts. Could work i guess :)

12:49 <DarkNeutrino> Thanks Jookia

12:50 <Jookia> DarkNeutrino: stick around and see if someone can give a better advice :)

12:58 <DarkNeutrino> :)

13:02 <mripard> rfkill-gpio is also a good option for this

13:04 <Jookia> yeah that and an always-on regulator might solve two issues

13:15 <mripard> always-on regulator are almost always not the right solution though

13:30 <MoeIcenowy> DarkNeutrino: SDIO Wi-Fi's are usually similar

13:30 <MoeIcenowy> for reset/enable GPIO I think mmc-pwrseq could be used

13:30 <MoeIcenowy> and for powering it up vmmc-supply is useful (because it's really powering the card)

13:31 <MoeIcenowy> mripard: I think for wifi few situations need rfkill-gpio

13:31 <MoeIcenowy> and my experience tells me although rfkill-gpio is correct from the kernel side, the userspace of generic Linux distros usually mess it up

13:34 <DarkNeutrino> I do have vmmc-supply regulator. Tho no GPIO assigned to it. So assigning it a GPIO could work i think

14:11 <MoeIcenowy> DarkNeutrino: I think in case the CPU is powered by a regulator or a power switch, model that part with a regulator is a good choice

14:11 <MoeIcenowy> a power switch could be a fixed regulator with a GPIO and a vin-supply

14:12 <MoeIcenowy> a DCDC/LDO with EN pin could also be this to

14:12 <MoeIcenowy> too *

14:12 <MoeIcenowy> s/CPU/WiFi/

14:16 <apritzel> DarkNeutrino: in case you are still looking for an example: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/arch/arm64/boot/dts/allwinner/sun50i-h6-pine-h64-model-b.dts

14:16 <apritzel> or look for any DT snippet that references "mmc1"

14:17 <DarkNeutrino> The reset GPIO in the pwrseq would be the power GPIO im assuming ?

14:17 <MoeIcenowy> apritzel: well I assume it's a PMIC less platform

14:17 <MoeIcenowy> DarkNeutrino: well I think it should be reset or wake

14:17 <MoeIcenowy> the power GPIO is the gpio of the VMMC regulator

14:18 <MoeIcenowy> which should be created now

14:18 <DarkNeutrino> Got it :)

14:18 <MoeIcenowy> the created regulator should have the original VMMC as vin-supply

14:18 <MoeIcenowy> if you want some example, check some H3/5 boards

14:18 <MoeIcenowy> (I assume you are on H3/5 too?

14:18 <DarkNeutrino> H616 :)

14:19 <MoeIcenowy> oops

14:19 <MoeIcenowy> PMIC-less?

14:19 <MoeIcenowy> or the PMIC is not enough for having an output for WiFi?

14:19 <DarkNeutrino> Nah it has AXP813a

14:20 <DarkNeutrino> iirc the name

14:20 <DarkNeutrino> We just recently got the thing into mainline

14:22 <apritzel> 313a?

14:23 <DarkNeutrino> yep haha

14:23 <apritzel> which is almost the same as "PMIC less": there are so few rails that you need all of them all of the time

14:23 <DarkNeutrino> yep

14:44 <DarkNeutrino> huh. It looks like the GPIOs werent needed at all :confused: Oh well LOL

14:45 <DarkNeutrino> pwrseq already had a GPIO so i guess that was the correct one

15:30 <Jookia> Would anyone know of a working sunxi TDM device tree I can investigate?

15:37 <apritzel> what's "sunxi TDM"?

15:39 <Jookia> uhh sorry, sunxi i2s tdm

17:29 <Jookia> ok i have done it. using the d1/t113 i2s i have multiplexed 3 ADCs without TDM :)