From: Greg KH <gregkh@linuxfoundation.org>
To: Qiwu Huang <yanziily@gmail.com>
Cc: sre@kernel.org, linux-pm@vger.kernel.org,
linux-kernel@vger.kernel.org, jiangfei1@xiaomi.com,
Qiwu Huang <huangqiwu@xiaomi.com>
Subject: Re: [PATCH v2 1/5] power: supply: core: add quick charge type property
Date: Mon, 13 Jul 2020 10:41:13 +0200 [thread overview]
Message-ID: <20200713084113.GC215949@kroah.com> (raw)
In-Reply-To: <38b7b1dc10cf608faceae923374791a52a450919.1594612572.git.huangqiwu@xiaomi.com>
On Mon, Jul 13, 2020 at 12:03:36PM +0800, Qiwu Huang wrote:
> From: Qiwu Huang <huangqiwu@xiaomi.com>
>
> Reports the kind of quick charge type based on
> different adapter power. UI will show different
> animation effect for different quick charge type.
>
> Signed-off-by: Qiwu Huang <huangqiwu@xiaomi.com>
> ---
> Documentation/ABI/testing/sysfs-class-power | 10 ++++++++++
> drivers/power/supply/power_supply_sysfs.c | 1 +
> include/linux/power_supply.h | 1 +
> 3 files changed, 12 insertions(+)
What changed from v1 of this patch? SHouldn't that always be below the
--- line?
>
> diff --git a/Documentation/ABI/testing/sysfs-class-power b/Documentation/ABI/testing/sysfs-class-power
> index 216d61a22f1e..d3169d47e359 100644
> --- a/Documentation/ABI/testing/sysfs-class-power
> +++ b/Documentation/ABI/testing/sysfs-class-power
> @@ -708,3 +708,13 @@ Description:
>
> Access: Read
> Valid values: 1-31
> +
> +What: /sys/class/power_supply/<supply_name>/quick_charge_type
> +Date: Jul 2020
> +Contact: Fei Jiang <jiangfei1@xiaomi.com>
> + Description:
> + Reports the kind of quick charge type based on different adapter power.
What are the allowed types here? Shouldn't that also be an enumerated
type with a predefined string?
thanks,
greg k-h
next prev parent reply other threads:[~2020-07-13 8:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1594612572.git.huangqiwu@xiaomi.com>
2020-07-13 4:03 ` [PATCH v2 1/5] power: supply: core: add quick charge type property Qiwu Huang
2020-07-13 8:41 ` Greg KH [this message]
[not found] ` <CAPtXDt2ALhYRTTn7m6Jb3k+339VC84YUDC7V=Yb7-a+DpvuVtg@mail.gmail.com>
2020-07-14 7:37 ` Greg KH
2020-07-13 4:03 ` [PATCH v2 2/5] power: supply: core: add wireless charger adapter " Qiwu Huang
2020-07-13 8:42 ` Greg KH
[not found] ` <CAPtXDt3kX0=MNXUjDfKr0EgmTxejctdoSoDWUY561gfT6CAr1Q@mail.gmail.com>
2020-07-14 7:37 ` Greg KH
2020-07-13 4:03 ` [PATCH v2 3/5] power: supply: core: add wireless signal strength property Qiwu Huang
2020-07-13 4:03 ` [PATCH v2 4/5] power: supply: core: property to control reverse charge Qiwu Huang
2020-07-13 4:03 ` [PATCH v2 5/5] power: supply: core: supply battery soc with decimal form Qiwu Huang
2020-07-13 8:44 ` Greg KH
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=20200713084113.GC215949@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=huangqiwu@xiaomi.com \
--cc=jiangfei1@xiaomi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=sre@kernel.org \
--cc=yanziily@gmail.com \
/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).