A person wrote a small program that can read all the registers from user space. so its possible
https://github.com/wphermans/Beaglebone-Web-PMIC-Register-Viewer


On 6/8/2019 12:08 PM, Dave wrote:
I found the PMIC docs and I could get the information I want from it.
But it is I2C and owned by the kernel and I can not seem to communicate with the PMIC while the kernel driver is loaded, which does not surprise me.

I noted from other posts that there is a patch to the tps65217.c driver that generates KEY_POWER hits on various changes that the PMIC detects.

Unfortunately the current tps65217.c source (5.1-rc3) has significantly different interrupt handling, and patching it to incorporate the KEY_POWER functionality without breaking the other things that have been changed is on the edge of my abilities.

Is there someone that understand threaded and nested interrupt handling in Linux that can guide me in patching the current tps65217.c driver to include the Key generation without blowing it up ?

--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected] <mailto:[email protected]>. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/55c8aec1-6598-4799-8bb9-1c8da55bcb49%40googlegroups.com <https://groups.google.com/d/msgid/beagleboard/55c8aec1-6598-4799-8bb9-1c8da55bcb49%40googlegroups.com?utm_medium=email&utm_source=footer>.
For more options, visit https://groups.google.com/d/optout.

--
For more options, visit http://beagleboard.org/discuss
--- You received this message because you are subscribed to the Google Groups "BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/82ea943f-69fb-7e86-6c95-d1556ed06c76%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to