lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Mon, 20 Mar 2017 12:34:03 +0100
From:   Quentin Schulz <quentin.schulz@...e-electrons.com>
To:     Sebastian Reichel <sre@...nel.org>
Cc:     mark.rutland@....com, thomas.petazzoni@...e-electrons.com,
        lars@...afoo.de, linux-pm@...r.kernel.org,
        linux-iio@...r.kernel.org, linux-sunxi@...glegroups.com,
        linux-kernel@...r.kernel.org, robh+dt@...nel.org, wens@...e.org,
        devicetree@...r.kernel.org, liam@...workimprov.net,
        icenowy@...c.xyz, pmeerw@...erw.net, knaack.h@....de,
        linux@...linux.org.uk, maxime.ripard@...e-electrons.com,
        bonbons@...ux-vserver.org, Lee Jones <lee.jones@...aro.org>,
        jic23@...nel.org, linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH v4 00/18] add support for AXP20X and AXP22X power supply
 drivers

Hi Sebastian and Liam,

On 15/03/2017 23:46, Sebastian Reichel wrote:
> On Wed, Mar 15, 2017 at 02:18:56PM +0100, Quentin Schulz wrote:
>> Hi Lee,
>>
>> On 15/03/2017 13:14, Lee Jones wrote:
>>> On Wed, 15 Mar 2017, Quentin Schulz wrote:
>>>
>>>> The X-Powers AXP20X and AXP22X PMICs have multiple ADCs. They expose
>>>> information and data of the various power supplies they support such as
>>>> ACIN, battery and VBUS. For example, they expose the current battery
>>>> voltage, charge or discharge, as well as ACIN and VBUS current voltages
>>>> and currents, internal PMIC temperature and ADC on 2 different GPIOs
>>>> when in the right mode (for the AXP209 only).
>>>
>>> What are you missing from this set now?  What Acks etc?  And what's
>>> the plan with regards to route to Mainline?  Where are the dependencies
>>> etc?
>>>
>>
>> Basically, a consensus on how we should named the DT property I added in
>> patch 01 and 02 (which is used afterwards in battery driver). All other
>> patches have ACKs.
>>
>> I added some logic to the battery driver so if anyone wants to review
>> that you're welcome. I already got several ACKs from the v3 though.
>>
>> No dependencies except for the battery driver (and the first two
>> patches) which needs the battery "framework" in the Power Supply
>> subsystem. A v9 of this framework has been sent a little bit more than a
>> week ago, I need this to be merged first or the battery driver will just
>> not compile. I think the other patches are ready to be merged.
> 
> FWIW I expect, that the axp battery patches go through my tree, since
> there doesn't seem to be a compile time dependency to the other
> patches from this series nor vice versa. I'm aware of the dependency
> to the bq27xxx series of course.
> 

As there are still some discussion going on Liam's patch series on which
my patch series depends, I propose to wait for it to be merged and then
I'll rework these battery driver patches. Is there anything I can do to
help the merging of Liam's patch series?

Could you ping me when it is merged? The easiest way would be to Cc me
to the next version though so I can follow the discussion :)

Thanks,
Quentin

-- 
Quentin Schulz, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com



Download attachment "signature.asc" of type "application/pgp-signature" (802 bytes)

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ