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  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:   Wed, 30 Aug 2017 07:47:46 -0700
From:   Tony Lindgren <>
To:     Hans de Goede <>
Cc:     Darren Hart <>,
        Andy Shevchenko <>,
        Wolfram Sang <>,
        Sebastian Reichel <>,
        Greg Kroah-Hartman <>,
        Guenter Roeck <>,
        Heikki Krogerus <>,,,, Liam Breck <>,,
Subject: Re: [PATCH v3 09/11] power: supply: bq24190_charger: Get
 input_current_limit from our supplier

* Hans de Goede <> [170830 02:49]:
> 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 the external Type-C
> power brick (adapter/charger) as a power-supply class device which
> supplies the charger-IC, with its voltage-now and current-max representing
> the negotiated voltage and max current draw.
> This commit adds support for this to the bq24190_charger driver by adding
> an external_power_changed callback and calling
> power_supply_set_input_current_limit_from_supplier from this callback.
> This callback will only get called if the bq24190 has a parent-supply.
> Note this replaces the functionality to get the current-limit from an
> extcon device, which will be removed in a follow-up commit.
> Signed-off-by: Hans de Goede <>

Acked-by: Tony Lindgren <>

Powered by blists - more mailing lists