Hi Hans, I sent too soon...
On Mon, Aug 28, 2017 at 9:04 AM, Hans de Goede wrote:
> Hi,
>
>
> On 16-08-17 22:28, Liam Breck wrote:
>>
>> Hi Hans,
>>
>> On Tue, Aug 15, 2017 at 1:04 PM, Hans de Goede
>> wrote:
>>>
>>> On some devices th
Hi Hans,
On Mon, Aug 28, 2017 at 9:04 AM, Hans de Goede wrote:
> Hi,
>
>
> On 16-08-17 22:28, Liam Breck wrote:
>>
>> Hi Hans,
>>
>> On Tue, Aug 15, 2017 at 1:04 PM, Hans de Goede
>> wrote:
>>>
>>> On some devices the USB Type-C port p
Hi Hans,
On Tue, Aug 15, 2017 at 1:04 PM, Hans de Goede wrote:
> On some devices the USB Type-C port power (USB PD 2.0) negotiation is
> done by a separate port-controller IC, while the current limit is
> controlled through another (charger) IC.
>
> It has been decided to model this by modelling
On Tue, Aug 8, 2017 at 2:00 AM, Hans de Goede wrote:
> Hi,
>
> On 08-08-17 10:39, Liam Breck wrote:
>>
>> Hi Hans,
>>
>> On Sun, Aug 6, 2017 at 5:35 AM, Hans de Goede wrote:
>>>
>>> Register the 5V boost converter as a regulator named
>&
Hi Hans,
On Sun, Aug 6, 2017 at 5:35 AM, Hans de Goede wrote:
> Register the 5V boost converter as a regulator named
> "regulator-bq24190-usb-vbus". Note the name includes "bq24190" because
> the bq24190 family is also used on ACPI devices where there are no
> device-tree phandles, so regulator_g
Hi Hans,
On Sun, Aug 6, 2017 at 5:35 AM, Hans de Goede wrote:
> Now that drivers/i2c/busses/i2c-cht-wc.c uses
> "input-current-limit-from-supplier" instead of "extcon-name" the last
> user of the bq24190 extcon code is gone, remove it.
>
> Signed-off-by: Hans de Goede
> ---
> drivers/power/supp
Hallo Hans :-)
On Sun, Aug 6, 2017 at 5:35 AM, Hans de Goede wrote:
> On some devices the USB Type-C port power (USB PD 2.0) negotiation is
> done by a separate port-controller IC, while the current limit is
> controlled through another (charger) IC.
>
> It has been decided to model this by mode
