Thats the regulator driver.

On Mon, Sep 5, 2016 at 2:06 AM, Christoph Mayer <[email protected]> wrote:

> I am not an expert on this but it looks like you have looked at the
> wrong driver.
>
> You may have a look here:
> http://lxr.free-electrons.com/source/drivers/regulator/
> tps65217-regulator.c?v=4.4
> The low-level driver you have looked at is used by this.
>
> Cheers
> Christoph
>
> On Sat, Sep 3, 2016 at 4:04 AM, William Hermans <[email protected]> wrote:
> > So I did some searching on this because I am interested in this as well.
> I
> > figured that the PMIC driver in the kernel would or should be responsible
> > for this if such support existed. So I read through the source file here:
> > http://lxr.free-electrons.com/source/drivers/mfd/tps65217.c?v=4.4 , and
> came
> > to the conclusion that battery charging was not "supported". Afterwards I
> > found this: http://elinux.org/BeagleBone_Power_Management#Battery which
> > seems to confirm my belief that battery charging is not supported in the
> > kernel driver.
> >
> > Anyway, it seems as though that if someone wants battery charging to work
> > "flawlessly" they either have to rewrite the kernel module to support
> this
> > feature. *OR* I do believe it should be possible to write a userspace
> > application, or script that communicates with the tps65217c directly via
> the
> > i2c bus, where it is connected. To manually "twiddle" the register bits.
> >
> > I would have to experiment with this myself to confirm that anything I
> think
> > may be possible. Actually *is* possible.
> >
> > On Fri, Sep 2, 2016 at 3:52 PM, William Hermans <[email protected]>
> wrote:
> >>
> >> Page 41 of the datasheet, looks like registers 3-6. Although I have not
> >> read in details what the function of those registers are. This should be
> >> fixable through custom software, but I'd have to read in greater detail
> to
> >> understand what must be done, and what should be checked for before
> manually
> >> setting the charger bits. Or even if it is even a good idea to do so.
> >>
> >> I'm a bit leery about writing to the actual registers of the PMIC, but
> >> only because I have no hands on with that.
> >
> >
> > --
> > 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/CALHSORoP%
> 2BctrmrzjEa%2B_2jRQ%3DBe_J6GKdjgiMsjC%2BENXLxWpDA%40mail.gmail.com.
> >
> > 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/CAJahsjXOChOneEfFZmKKvhjsZSb6f
> oLeyBm5HcCpmumi9E8L9A%40mail.gmail.com.
> 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/CALHSORqjUhDAdf-FyYxJ7pNF7Z6sEC-SJoVmZ0jq0o6f_%2BR%3Dbg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to