[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAMz4kuJroGf6xLdMXfgFtCkLE8Esg5eqbydBgnvm5ELN=2xFmQ@mail.gmail.com>
Date: Tue, 4 Jul 2017 15:27:55 +0800
From: Baolin Wang <baolin.wang@...aro.org>
To: Charles Keepax <ckeepax@...nsource.cirrus.com>
Cc: Felipe Balbi <balbi@...nel.org>,
Greg KH <gregkh@...uxfoundation.org>,
Sebastian Reichel <sre@...nel.org>, Jun Li <jun.li@....com>,
Peter Chen <peter.chen@...escale.com>,
Mark Brown <broonie@...nel.org>,
John Stultz <john.stultz@...aro.org>,
NeilBrown <neilb@...e.com>, patches@...nsource.wolfsonmicro.com,
Linux PM list <linux-pm@...r.kernel.org>,
USB <linux-usb@...r.kernel.org>,
device-mainlining@...ts.linuxfoundation.org,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2 3/3] power: wm831x_power: Support USB charger current
limit management
Hi,
On 3 July 2017 at 16:53, Charles Keepax <ckeepax@...nsource.cirrus.com> wrote:
> On Mon, Jul 03, 2017 at 02:07:15PM +0800, Baolin Wang wrote:
>> Integrate with the newly added USB charger interface to limit the current
>> we draw from the USB input based on the input device configuration
>> identified by the USB stack, allowing us to charge more quickly from high
>> current inputs without drawing more current than specified from others.
>>
>> Signed-off-by: Mark Brown <broonie@...nel.org>
>> Signed-off-by: Baolin Wang <baolin.wang@...aro.org>
>> ---
> <snip>
>> /*********************************************************************
>> * Battery properties
>> *********************************************************************/
>> @@ -607,6 +647,22 @@ static int wm831x_power_probe(struct platform_device *pdev)
>> }
>> }
>>
>> + power->usb_phy = devm_usb_get_phy_by_phandle(&pdev->dev,
>> + "usb-phy", 0);
>> + if (IS_ERR(power->usb_phy)) {
>> + ret = PTR_ERR(power->usb_phy);
>> + dev_err(&pdev->dev, "Failed to find USB phy: %d\n", ret);
>> + goto err_bat_irq;
>> + }
>> +
>
> We should probably update the binding documentation for this as
> well: mfd/wm831x.txt
Yes, I will update the binding documentation.
>
> Also I am not sure this needs to be implemented now, but what is
> the plan regarding pdata systems? Generally the driver supports
> both and it would be nice to know there is a way forward for that
> even if we don't implement it yet.
OK, I'll modify this in next version. Thanks.
--
Baolin.wang
Best Regards
Powered by blists - more mailing lists