02:40 <wens> Hmm, I see patches for GC0308 camera sensor

09:46 <apritzel> Does anyone have more information about the Allwinner A523? A manual, by any chance, or BSP source code?

09:46 <apritzel> Or even a link to a recovery image? There seem to be the Teclast P85T and P26T tablets out there with that chip.

16:29 <jernej> fun, DE3.3 registers are not double buffered and while most functionality works as-is, scaler refuses to work properly if it's not programmed at vsync time.

16:31 <jernej> there is RCQ, some sort of DMA for registers, which writes them at right time, but that will need a major rework

19:45 <Nexrem> Hey, I'm having a problem with seemingly both my pull-up and pull-down being active at the same time on H618. I have a devicetree overlay loaded in from u-boot which sets my pins as active_low with pull-up with the gpio-keys driver. That all works but on some pins it doesnt. When reading the GPIOs those pins measure 0 when they should in fact be 1, since they're being pulled high. Probing the pins with my meter shows about 1.5V which is why

19:48 <Nexrem> I tried setting up the pin modes under the gpio controller, but then I get a message saying the pins are already taken by the gpio-keys driver and then neither works. I'm not sure why it would collide like that. I should be able to do both

19:51 <Nexrem> Here's my dts if anyone wants to look https://pastebin.com/raw/zf3wtAmj

21:42 <apritzel> Nexrem: you don't need any pinctrl properties for gpio-keys

21:43 <apritzel> that's basically saying the same thing twice: you announce PC5 at the top and then at the bottom again

21:44 <apritzel> besides: this "allwinner," prefix is really ancient syntax, we use the generic properties now for years

21:48 <apritzel> Nexrem: so it's really just the gpio-keys node, without pinctrl-0 and pinctrl-names properties