[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <1411564278-17207-1-git-send-email-frans.klaver@xsens.com>
Date: Wed, 24 Sep 2014 15:11:16 +0200
From: Frans Klaver <frans.klaver@...ns.com>
To: <linux-kernel@...r.kernel.org>
CC: Frans Klaver <frans.klaver@...ns.com>,
Dmitry Eremin-Solenikov <dbaryshkov@...il.com>,
David Woodhouse <dwmw2@...radead.org>,
Rob Herring <robh+dt@...nel.org>,
Pawel Moll <pawel.moll@....com>,
Mark Rutland <mark.rutland@....com>,
Ian Campbell <ijc+devicetree@...lion.org.uk>,
Kumar Gala <galak@...eaurora.org>,
Randy Dunlap <rdunlap@...radead.org>,
<devicetree@...r.kernel.org>, <linux-doc@...r.kernel.org>
Subject: [RFC PATCH 0/2] explicitly instantiate battery from device tree
Hi there,
Here's some patches that make it possible to instantiate an sbs battery without
it being present yet.
i2c devices are more or less presumed to be persistent. This is a fair
assumption, except for the case of batteries. It is perfectly sensible for a
device to boot up using wall power, but no battery attached. While later
attaching a battery and dropping the wall power. Detecting the device from
userspace is tedious requires you to scan for device presence yourself, or you
can ask the kernel to probe again, cluttering your logs with failed probes.
I'd like to hear what you think about this.
Thanks,
Frans
Frans Klaver (2):
sbs-battery: add forced instantiation from device tree
sbs-battery: dts: document always-present property
.../devicetree/bindings/power_supply/sbs_sbs-battery.txt | 2 ++
drivers/power/sbs-battery.c | 11 +++++++++--
include/linux/power/sbs-battery.h | 3 +++
4 files changed, 15 insertions(+), 2 deletions(-)
--
2.1.0
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists