On Mon, 04 August 2014 "[email protected]" <[email protected]> wrote: > On Mon, Aug 4, 2014 at 4:29 PM, [email protected] <[email protected]> wrote: > > Would it make sense to add this to the device driver and the put this > > output in debugfs? > > Some of this should probably always be present in sysfs
The register values themselves are in debugfs via regmap infrastructure. Providing a decoded dump in debugfs is probably asking too much and better suited in a userspace decoding application (maybe some hwinfo package?). Important higher-level information is being exported via respective subdrivers (e.g. pek input driver, power_supply drivers, regulators, ...). Bruno > > On Mon, Aug 4, 2014 at 4:20 PM, Bruno Prémont <[email protected]> > > wrote: > >> Hi, > >> > >> Attached code is a little program to decode AXP20x registers and present > >> their values in a readable way. > >> > >> By default it looks for AXP20x mfd driver's regmap in sysfs. > >> > >> Not all registers are being decoded yet (missing are e.g. GPIOs). > >> Some undocumented registers are mentioned (e.g. OCV values, RDC). > >> > >> A nice bonus would be to add support for reading the regs directly > >> via i2c (in order to easily display register status under 3.4 kernels). > >> > >> Bruno > >> > >> -- > >> You received this message because you are subscribed to the Google Groups > >> "linux-sunxi" group. > >> To unsubscribe from this group and stop receiving emails from it, send an > >> email to [email protected]. > >> For more options, visit https://groups.google.com/d/optout. > > > > > > > > -- > > Jon Smirl > > [email protected] > > > -- You received this message because you are subscribed to the Google Groups "linux-sunxi" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
