From: Greg KH <gregkh@linuxfoundation.org>
To: ivan <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: Tue, 14 Jul 2020 09:37:11 +0200 [thread overview]
Message-ID: <20200714073711.GA689066@kroah.com> (raw)
In-Reply-To: <CAPtXDt2ALhYRTTn7m6Jb3k+339VC84YUDC7V=Yb7-a+DpvuVtg@mail.gmail.com>
A: http://en.wikipedia.org/wiki/Top_post
Q: Were do I find info about this thing called top-posting?
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
A: No.
Q: Should I include quotations after my reply?
http://daringfireball.net/2007/07/on_top
On Tue, Jul 14, 2020 at 03:31:52PM +0800, ivan wrote:
> I think we should add an enumederated for this
What is "this"?
>
> for example
>
> abi document
>
> 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.
> Different quick charge type represent different charging power.
> QUICK_CHARGE_NORMAL : Charging Power <= 10W
> QUICK_CHARGE_FAST : 10W < Charging Power <= 20W
> QUICK_CHARGE_FLASH : 20W < Charging Power <= 30W
> QUICK_CHARGE_TURBE : 30W < Charging Power <= 50W
> QUICK_CHARGE_SUPER : Charging Power > 50W
>
> Access: Read-Only
> Valid values:
> 0: QUICK_CHARGE_NORMAL,
> 1: QUICK_CHARGE_FAST,
> 2: QUICK_CHARGE_FLASH,
> 3: QUICK_CHARGE_TURBE,
> 4: QUICK_CHARGE_SUPER.
>
>
> power_supply.h
>
> enum power_supply_quick_charge_type {
> QUICK_CHARGE_NORMAL = 0,
> QUICK_CHARGE_FAST,
> QUICK_CHARGE_FLASH,
> QUICK_CHARGE_TURBE,
> QUICK_CHARGE_SUPER,
> QUICK_CHARGE_MAX,
> };
That seems like a good change, why not do this? :)
thanks,
greg k-h
next prev parent reply other threads:[~2020-07-14 7:37 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 ` Qiwu Huang
2020-07-13 8:41 ` Greg KH
[not found] ` <CAPtXDt2ALhYRTTn7m6Jb3k+339VC84YUDC7V=Yb7-a+DpvuVtg@mail.gmail.com>
2020-07-14 7:37 ` Greg KH [this message]
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=20200714073711.GA689066@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
Powered by JetHome