On Sun, 21 Apr 2024, at 3:09 PM, Chris Morgan wrote: Thanks for the review and all the work on the regulators! >> >> Is there any reason to not just use the existing gpio-keys node? >> Either put a label on it in patch 2/5, and reference that below, >> outside of the root node, or use an absolute path reference. > > I would also second just putting an alias and adding these to it. > I myself as a preference tend to set the GPIO volume buttons as > a seperate node only so I can enable key repeat on them, otherwise > one node is best. > Thanks, have split the volume keys out and merged the thumbsticks into the existing node. > > After extensive testing with a multimeter and fudging the regulator > voltages up or down, I've been able to figure out the regulator > assignments for each of the different power domains. Schematics would > have helped, but sadly this had to be done the hard way. Based on > past experience with Anbernic I would strongly suspect all devices > have this assignment, but I know for sure my 35XXH does. > > vcc-pa-supply = <®_cldo3>; > vcc-pc-supply = <®_cldo3>; > vcc-pe-supply = <®_cldo3>; > vcc-pf-supply = <®_cldo3>; > vcc-pg-supply = <®_aldo4>; > vcc-ph-supply = <®_cldo3>; > vcc-pi-supply = <®_cldo3>; > > On my board the reg_cldo3 is a constant 3.3v output, and the reg_aldo4 > is a constant 1.8v output. > Nice work! These work well in my testing. > > I haven't figured out the boost regulator yet, but for the host port > I've been able to ascertain there's no less than 2 GPIO controlled > regulators in play. PE5 must be driven high or the USB host port will > not power on at all. If PE5 is driven high then the port kicks on, but > at 3.3v. Once I also enable PI7 the port then reaches 4.6v. I'm not sure > how to get it to a proper 5v yet, I'm still working that part out. > Thanks for working all that out, will hold off any other changes for now. Ryan
