From: Anton Vorontsov <cbouatmailru@gmail.com>
To: Paul Fertser <fercerpav@gmail.com>
Cc: Anton Vorontsov <cbou@mail.ru>,
David Woodhouse <dwmw2@infradead.org>,
linux-kernel@vger.kernel.org,
Nelson Castillo <arhuaco@freaks-unidos.net>,
Lars-Peter Clausen <lars@metafoo.de>,
Ben Dooks <ben@simtec.co.uk>,
Russell King <rmk+kernel@arm.linux.org.uk>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] gta02: set pcf50633 chg_ref_current_ma
Date: Thu, 15 Oct 2009 21:15:01 +0400 [thread overview]
Message-ID: <20091015171501.GA25775@oksana.dev.rtsoft.ru> (raw)
In-Reply-To: <1255471148-29047-3-git-send-email-fercerpav@gmail.com>
On Wed, Oct 14, 2009 at 01:59:05AM +0400, Paul Fertser wrote:
> From: Lars-Peter Clausen <lars@metafoo.de>
>
> This value is board-specific and is needed for calculations to set charging
> current limit properly.
>
> Signed-off-by: Lars-Peter Clausen <lars@metafoo.de>
> Acked-by: Nelson Castillo <arhuaco@freaks-unidos.net>
> Signed-off-by: Paul Fertser <fercerpav@gmail.com>
> ---
>
> Since this patch compile-depends on previous probably it should go through
> the same tree as others. Nelson (gta02 maintainer) agrees with whatever you
> think is best.
I would happy to apply this patch via battery tree, along
with other your patches.
Just to make things clear: we no longer need RMK's Ack for
mach-specific patches that don't touch core code? Or maybe
Ben's Ack is still required?
Want to be on a safe side before applying.
Thanks!
> arch/arm/mach-s3c2442/mach-gta02.c | 3 +++
> 1 files changed, 3 insertions(+), 0 deletions(-)
>
> diff --git a/arch/arm/mach-s3c2442/mach-gta02.c b/arch/arm/mach-s3c2442/mach-gta02.c
> index 0fb385b..b0a3d74 100644
> --- a/arch/arm/mach-s3c2442/mach-gta02.c
> +++ b/arch/arm/mach-s3c2442/mach-gta02.c
> @@ -268,6 +268,9 @@ struct pcf50633_platform_data gta02_pcf_pdata = {
>
> .batteries = gta02_batteries,
> .num_batteries = ARRAY_SIZE(gta02_batteries),
> +
> + .chg_ref_current_ma = 1000,
> +
> .reg_init_data = {
> [PCF50633_REGULATOR_AUTO] = {
> .constraints = {
> --
> 1.6.0.6
--
Anton Vorontsov
email: cbouatmailru@gmail.com
irc://irc.freenode.net/bd2
next prev parent reply other threads:[~2009-10-15 17:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-13 21:59 [PATCH] power: pcf50633: add ac power supply class to the charger Paul Fertser
2009-10-13 21:59 ` [PATCH] power: pcf50633: introduces battery charging current control Paul Fertser
2009-10-13 21:59 ` [PATCH] gta02: set pcf50633 chg_ref_current_ma Paul Fertser
2009-10-13 21:59 ` [PATCH] power: pcf50633: get rid of charging restart software auto-triggering Paul Fertser
2009-10-13 21:59 ` [PATCH] power: pcf50633: properly reenable charging when the supply conditions change Paul Fertser
2009-10-13 21:59 ` [PATCH] power: pcf50633: query charger status directly Paul Fertser
2009-10-15 17:15 ` Anton Vorontsov [this message]
2009-10-17 17:01 ` [PATCH] power: pcf50633: introduces battery charging current control Pavel Machek
2009-10-20 0:01 ` Paul Fertser
2009-10-20 7:26 ` Pavel Machek
2009-10-19 21:35 ` 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=20091015171501.GA25775@oksana.dev.rtsoft.ru \
--to=cbouatmailru@gmail.com \
--cc=arhuaco@freaks-unidos.net \
--cc=ben@simtec.co.uk \
--cc=cbou@mail.ru \
--cc=dwmw2@infradead.org \
--cc=fercerpav@gmail.com \
--cc=lars@metafoo.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk+kernel@arm.linux.org.uk \
/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