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
Subject: Re: [RFC] Limiting charge current on Droid 4 (and N900)
Date: Mon, 29 Jun 2020 08:55:15 -0700 [thread overview]
Message-ID: <20200629155515.GR37466@atomide.com> (raw)
In-Reply-To: <20200615140557.GA22781@duo.ucw.cz>
* 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.
Regards,
Tony
WARNING: multiple messages have this Message-ID (diff)
From: Tony Lindgren <tony@atomide.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: mpartap@gmx.net, linux-pm@vger.kernel.org, merlijn@wizzup.org,
martin_rysavy@centrum.cz,
kernel list <linux-kernel@vger.kernel.org>,
sre@kernel.org, nekit1000@gmail.com, linux-omap@vger.kernel.org,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>
Subject: Re: [RFC] Limiting charge current on Droid 4 (and N900)
Date: Mon, 29 Jun 2020 08:55:15 -0700 [thread overview]
Message-ID: <20200629155515.GR37466@atomide.com> (raw)
In-Reply-To: <20200615140557.GA22781@duo.ucw.cz>
* 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.
Regards,
Tony
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-06-29 18:45 UTC|newest]
Thread overview: 12+ 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-15 14:05 ` Pavel Machek
2020-06-27 11:01 ` Merlijn Wajer
2020-06-27 11:01 ` Merlijn Wajer
2020-06-29 21:49 ` Pavel Machek
2020-06-29 21:49 ` Pavel Machek
2020-06-29 15:55 ` Tony Lindgren [this message]
2020-06-29 15:55 ` Tony Lindgren
2020-08-20 4:15 ` Tony Lindgren
2020-08-20 4:15 ` Tony Lindgren
2020-08-20 6:58 ` Pavel Machek
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=20200629155515.GR37466@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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.