On Fri, Mar 24, 2017 at 3:55 PM, Quentin Schulz
wrote:
> Hi,
>
> On 23/03/2017 10:52, Chen-Yu Tsai wrote:
>> On Thu, Mar 23, 2017 at 5:35 PM, Sebastian Reichel wrote:
>>> Hi,
>>>
>>> On Wed, Mar 22, 2017 at 12:34:45PM +0800, Chen-Yu Tsai wrote:
On Fri, Mar 24, 2017 at 3:55 PM, Quentin Schulz
wrote:
> Hi,
>
> On 23/03/2017 10:52, Chen-Yu Tsai wrote:
>> On Thu, Mar 23, 2017 at 5:35 PM, Sebastian Reichel wrote:
>>> Hi,
>>>
>>> On Wed, Mar 22, 2017 at 12:34:45PM +0800, Chen-Yu Tsai wrote:
P.S. I'm thinking about having MFD_AXP20X
Hi,
On 23/03/2017 10:52, Chen-Yu Tsai wrote:
> On Thu, Mar 23, 2017 at 5:35 PM, Sebastian Reichel wrote:
>> Hi,
>>
>> On Wed, Mar 22, 2017 at 12:34:45PM +0800, Chen-Yu Tsai wrote:
>>> P.S. I'm thinking about having MFD_AXP20X imply its various sub-drivers.
>>> Not sure if that
Hi,
On 23/03/2017 10:52, Chen-Yu Tsai wrote:
> On Thu, Mar 23, 2017 at 5:35 PM, Sebastian Reichel wrote:
>> Hi,
>>
>> On Wed, Mar 22, 2017 at 12:34:45PM +0800, Chen-Yu Tsai wrote:
>>> P.S. I'm thinking about having MFD_AXP20X imply its various sub-drivers.
>>> Not sure if that was the intended
On Thu, Mar 23, 2017 at 5:35 PM, Sebastian Reichel wrote:
> Hi,
>
> On Wed, Mar 22, 2017 at 12:34:45PM +0800, Chen-Yu Tsai wrote:
>> P.S. I'm thinking about having MFD_AXP20X imply its various sub-drivers.
>> Not sure if that was the intended usage of the new imply syntax though.
On Thu, Mar 23, 2017 at 5:35 PM, Sebastian Reichel wrote:
> Hi,
>
> On Wed, Mar 22, 2017 at 12:34:45PM +0800, Chen-Yu Tsai wrote:
>> P.S. I'm thinking about having MFD_AXP20X imply its various sub-drivers.
>> Not sure if that was the intended usage of the new imply syntax though.
>
> I think
Hi,
On Wed, Mar 22, 2017 at 12:34:45PM +0800, Chen-Yu Tsai wrote:
> P.S. I'm thinking about having MFD_AXP20X imply its various sub-drivers.
> Not sure if that was the intended usage of the new imply syntax though.
I think adding "default MFD_AXP20X" to the sub-drivers is cleaner,
as you will
Hi,
On Wed, Mar 22, 2017 at 12:34:45PM +0800, Chen-Yu Tsai wrote:
> P.S. I'm thinking about having MFD_AXP20X imply its various sub-drivers.
> Not sure if that was the intended usage of the new imply syntax though.
I think adding "default MFD_AXP20X" to the sub-drivers is cleaner,
as you will
On 22 March 2017 04:34:45 GMT+00:00, Chen-Yu Tsai wrote:
>Hi,
>
>On Mon, Mar 20, 2017 at 4:16 PM, Quentin Schulz
> wrote:
>> The X-Powers AXP20X and AXP22X PMICs have multiple ADCs. They expose
>the
>> battery voltage, battery charge and
On 22 March 2017 04:34:45 GMT+00:00, Chen-Yu Tsai wrote:
>Hi,
>
>On Mon, Mar 20, 2017 at 4:16 PM, Quentin Schulz
> wrote:
>> The X-Powers AXP20X and AXP22X PMICs have multiple ADCs. They expose
>the
>> battery voltage, battery charge and discharge currents, AC-in and
>VBUS
>> voltages and
Hi,
On Mon, Mar 20, 2017 at 4:16 PM, Quentin Schulz
wrote:
> The X-Powers AXP20X and AXP22X PMICs have multiple ADCs. They expose the
> battery voltage, battery charge and discharge currents, AC-in and VBUS
> voltages and currents, 2 GPIOs muxable in ADC mode
Hi,
On Mon, Mar 20, 2017 at 4:16 PM, Quentin Schulz
wrote:
> The X-Powers AXP20X and AXP22X PMICs have multiple ADCs. They expose the
> battery voltage, battery charge and discharge currents, AC-in and VBUS
> voltages and currents, 2 GPIOs muxable in ADC mode and PMIC temperature.
>
> This adds
The X-Powers AXP20X and AXP22X PMICs have multiple ADCs. They expose the
battery voltage, battery charge and discharge currents, AC-in and VBUS
voltages and currents, 2 GPIOs muxable in ADC mode and PMIC temperature.
This adds support for most of AXP20X and AXP22X ADCs.
Signed-off-by: Quentin
The X-Powers AXP20X and AXP22X PMICs have multiple ADCs. They expose the
battery voltage, battery charge and discharge currents, AC-in and VBUS
voltages and currents, 2 GPIOs muxable in ADC mode and PMIC temperature.
This adds support for most of AXP20X and AXP22X ADCs.
Signed-off-by: Quentin
14 matches
Mail list logo