KREYREN_oftc has quit [Remote host closed the connection]
KREYREN_oftc has joined #linux-sunxi
KREYREN_oftc has quit [Write error: connection closed]
<macromorgan>
looks like the PWM controller is new IP too
<macromorgan>
seems to be the same as the T507 though
ity has joined #linux-sunxi
wingrime-ww has joined #linux-sunxi
bauen1 has quit [Ping timeout: 480 seconds]
apritzel has joined #linux-sunxi
<apritzel>
macromorgan: it's not compatible to anything existing, but close to the D1, patches for which are on the list
<macromorgan>
okay cool
<macromorgan>
I've got the gpadc working now and am just trying to decipher how to do the devicetree binding
<apritzel>
I have one patch on top to unify one difference, but there is more
<macromorgan>
weird part is there's a mux in place with an enable pin (maybe a regulator? not sure)
<macromorgan>
but I suppose the patch series for the gpadc is probably ready to go so I can send that
<macromorgan>
(it's also the same as the D1 by the way)
<macromorgan>
so I'll resubmit the NMI in the next day or so and also send a new series for the gpadc
<apritzel>
sounds good
<apritzel>
so the analogue buttons on the -H are connected to the GPADC, then?
<macromorgan>
the 2 analog joysticks are connected to a mux which goes through the gpadc channel 0
<macromorgan>
as best I can tell there's either 3 or 4 pins involved... 1 pin enables the mux, 2 pins switch between the 4 output channels, and 1 pin *might* be involved as an interrupt line
<macromorgan>
the enable pin is GPIO active low, the output pins are active high, and I have to guess about the possible interrupt pin
<macromorgan>
pain in the butt but now have 100% of the input buttons working for the RG35XXH (including the 2 ADC joysticks along with the power button)
<tokyovigilante>
macromorgan: good work! Anything to add for the -H DTS or in general for the power button? Will work on v2 of the DTS patchset hopefully today
<macromorgan>
power button should "just work" once the NMI controller is present and the interrupts are hooked up (and you fix the regmap in the driver)
<macromorgan>
so basically that patch series I posted last week + one additional line in the AXP717 driver
<macromorgan>
I'm trying to nail down the device tree right now, since what I need to describe is giving me errors when I describe it...
<apritzel>
I will send a v2 of the AXP717 fixes today or tomorrow, with those IRQ ACK registers added, so hopefully that should be covered
Robot_ has quit [Ping timeout: 480 seconds]
<tokyovigilante>
awesome
<macromorgan>
tokyovigilante: My current tree. Still needs some additional cleanup before it's upstream worthy, but it's getting there: https://paste.debian.net/1314318/
KREYREN_oftc has joined #linux-sunxi
KREYREN_oftc has quit [Remote host closed the connection]
KREYREN_oftc has joined #linux-sunxi
KREYREN_oftc has quit [Remote host closed the connection]
KREYREN_oftc has joined #linux-sunxi
ftg has joined #linux-sunxi
<apritzel>
macromorgan: oh wow, that's quite some elaborate DT maze for the ADC joysticks ;-) How did you figure this out?
<macromorgan>
experience... it's almost a perfect copy-pasta from what I did for the Anbernic devices, which is almost a perfect copy pasta of the Odroid Go Super
<macromorgan>
I'm trying to refine the regulators and stuff right now, then I'll hand off my tree to Tokyo to see if it helps him with what he's trying to do
KREYREN_oftc has quit [Remote host closed the connection]
KREYREN_oftc has joined #linux-sunxi
<apritzel>
yeah, the regulators need some love, but I commented on that already on tokyovigilante's post
<apritzel>
macromorgan: if you know something about the regulators, please consider replying on the list, that way we can keep all the process in one place
<macromorgan>
will do. For now I'm trying to just disable them all, test for broken hardware, then enable 1 at a time until the hardware starts to work
<apritzel>
and the mailing lists are *much* better archived and indexed than IRC
<macromorgan>
right
<apritzel>
I really tap into even 10 year old threads regularly to learn about something and find the reason for why code is written the way it is
<apritzel>
and especially seeing some changes (for instance from all regulators on to only the ones we need) is often very insightful
szemzoa_ has joined #linux-sunxi
jelly has quit [Write error: connection closed]
szemzoa has quit [Read error: Connection reset by peer]
vagrantc has quit [Quit: leaving]
<tokyovigilante>
macromorgan: looks good, will merge these in. Any thoughts here about just having one DTS for the three devices, given the missing HW on the -2024 and -Plus *should* be ignored?
jelly has joined #linux-sunxi
smaeul has quit [Read error: Connection reset by peer]