From: Marek Vasut <marex@denx.de>
To: Hector Palacios <hector.palacios@digi.com>
Cc: "linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
linux-pm@vger.kernel.org,
"fabio.estevam@freescale.com" <fabio.estevam@freescale.com>,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Subject: Re: Freescale MXS battery driver
Date: Tue, 16 Jul 2013 10:26:14 +0200 [thread overview]
Message-ID: <201307161026.14916.marex@denx.de> (raw)
In-Reply-To: <51E4FE90.9010700@digi.com>
Dear Hector Palacios,
> Greetings,
>
> Does anybody know if there is any on-going work to support Freescale's MXS
> battery driver?
Nothing I know of, but implementing charger itself should be rather easy.
Implementing overcharging protection and all this stuff would be hell. Good luck
;-)
Best regards,
Marek Vasut
WARNING: multiple messages have this Message-ID (diff)
From: marex@denx.de (Marek Vasut)
To: linux-arm-kernel@lists.infradead.org
Subject: Freescale MXS battery driver
Date: Tue, 16 Jul 2013 10:26:14 +0200 [thread overview]
Message-ID: <201307161026.14916.marex@denx.de> (raw)
In-Reply-To: <51E4FE90.9010700@digi.com>
Dear Hector Palacios,
> Greetings,
>
> Does anybody know if there is any on-going work to support Freescale's MXS
> battery driver?
Nothing I know of, but implementing charger itself should be rather easy.
Implementing overcharging protection and all this stuff would be hell. Good luck
;-)
Best regards,
Marek Vasut
next prev parent reply other threads:[~2013-07-16 8:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-16 8:04 Freescale MXS battery driver Hector Palacios
2013-07-16 8:04 ` Hector Palacios
2013-07-16 8:26 ` Marek Vasut [this message]
2013-07-16 8:26 ` Marek Vasut
2013-07-16 10:05 ` Uwe Kleine-König
2013-07-16 10:05 ` Uwe Kleine-König
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=201307161026.14916.marex@denx.de \
--to=marex@denx.de \
--cc=fabio.estevam@freescale.com \
--cc=hector.palacios@digi.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-pm@vger.kernel.org \
--cc=u.kleine-koenig@pengutronix.de \
/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.