From: Tony Lindgren <tony@atomide.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: kernel list <linux-kernel@vger.kernel.org>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
linux-omap@vger.kernel.org, sre@kernel.org, nekit1000@gmail.com,
mpartap@gmx.net, merlijn@wizzup.org, martin_rysavy@centrum.cz,
linux-pm@vger.kernel.org, "Arthur D." <spinal.by@gmail.com>
Subject: Re: [RFC] Limiting charge current on Droid 4 (and N900)
Date: Thu, 20 Aug 2020 07:15:12 +0300 [thread overview]
Message-ID: <20200820041512.GH2994@atomide.com> (raw)
In-Reply-To: <20200629155515.GR37466@atomide.com>
* Tony Lindgren <tony@atomide.com> [200629 18:46]:
> * Pavel Machek <pavel@ucw.cz> [200615 07:06]:
> > Hi!
> >
> > Droid 4 has same problem as N900: it is often neccessary to manually
> > tweak current draw from USB, for example when using thin charging cable.
> >
> > N900 creates unique attribute by hand, but I believe
> > POWER_SUPPLY_PROP_INPUT_CURRENT_LIMIT looks suitable. (Should N900 be
> > converted?)
> >
> > Comments? Would the patch be acceptable after fixing whitespace?
>
> Looks OK to me. Until we have better charger vs host vs usb3 charging hub
> detection in place this seems like a good thing to do.
FYI, I'm cleaning up the pending charger and battery patches to send out
for review. So that includes my earlier RFC battery status patches, and
Spinal's additions, and this patch. It will likely be several days before
I have the series ready for posting though.
Regards,
Tony
next prev parent reply other threads:[~2020-08-20 4:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-15 14:05 [RFC] Limiting charge current on Droid 4 (and N900) Pavel Machek
2020-06-27 11:01 ` Merlijn Wajer
2020-06-29 21:49 ` Pavel Machek
2020-06-29 15:55 ` Tony Lindgren
2020-08-20 4:15 ` Tony Lindgren [this message]
2020-08-20 6:58 ` Pavel Machek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200820041512.GH2994@atomide.com \
--to=tony@atomide.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=martin_rysavy@centrum.cz \
--cc=merlijn@wizzup.org \
--cc=mpartap@gmx.net \
--cc=nekit1000@gmail.com \
--cc=pavel@ucw.cz \
--cc=spinal.by@gmail.com \
--cc=sre@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).