On Tue, 5 Jul 2016 11:25:10 +0200 Maxime Ripard wrote: > On Tue, Jul 05, 2016 at 04:33:31PM +0800, Icenowy Zheng wrote: > > > > > > 05.07.2016, 13:26, "Michael Haas" <michael.haas@xxxxxxxxxxx>: > > > Hi, > > > > > > nice work! Is this in any way related to Bruno Prémonts driver for the > > > axp20x? > > > > > > I've got a reworked version of that lying around, but it's not quite > > > ready for submission. Do you know what pieces are missing in your driver > > > for axp20x support - as opposed to axp22x, which is already working? > > > > Therotically, it can run on axp20x. However, I have currently no > > test device. (Still waiting for my C.H.I.P.) So I can only promise > > it to run on axp22x. > > Still, it looks like you just took Bruno's driver, stripped out the > axp20x parts and added the one to deal with axp22x. > > This makes the driver look weird, by being called axp20x, without > actually supporting those PMICs, but having some axp22x variables > right in the middle. And that's awfully inconsistent. > > I'd rather have you add the AXP20x driver directly, and then add the > needed stuff for the AXP22x. >From a very quick look at the patch it looks like only basic "monitoring" features have been retained, and yes, claiming the driver to be for axp22x and having the functions named axp20x feels weird. Missing parts are OCV, charge control (be it as interaction with USB-power where charge current must be limited to not over-drain USB power source or manual control when user knows more about the USB power plug than the device). Proper capacity measurement is a completely different story which I did not implement (it exists in 3.4 sunxi kernel but is not straight-forward and makes use of extra registers for data keeping). Bruno -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
