From: Pavel Machek <pavel@ucw.cz>
To: "Pali Rohár" <pali.rohar@gmail.com>
Cc: kernel list <linux-kernel@vger.kernel.org>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
linux-omap@vger.kernel.org, tony@atomide.com, sre@kernel.org,
nekit1000@gmail.com, mpartap@gmx.net, merlijn@wizzup.org,
afd@ti.com, linux-pm@vger.kernel.org
Subject: Re: bq27000: directory/files exists even when hardware is not available
Date: Fri, 20 Apr 2018 10:17:42 +0200 [thread overview]
Message-ID: <20180420081741.GA8856@amd> (raw)
In-Reply-To: <20180420074826.c7cy4z3tq7c56ccs@pali>
[-- Attachment #1: Type: text/plain, Size: 2160 bytes --]
On Fri 2018-04-20 09:48:26, Pali Rohár wrote:
> On Friday 20 April 2018 09:40:36 Pavel Machek wrote:
> > Hi!
> >
> > On droid4 (4.17-rc1), /sys/class/power_supply/bq27000-battery exists
> > even when hardware is not present (as on Droid 4).
> >
> > Any ideas?
> > Pavel
>
> Somebody must have registered bq device into power_supply subsystem.
> Maybe DT note is present?
No, I don't think so:
pavel@duo:/data/l/linux-n900$ grep bq27 arch/arm/boot/dts/*
Binary file arch/arm/boot/dts/omap3-n900.dtb matches
arch/arm/boot/dts/omap3-n900.dts: bq27200: bq27200@55 {
arch/arm/boot/dts/omap3-n900.dts: compatible =
"ti,bq27200";
arch/arm/boot/dts/omap3-n900.dts~: bq27200: bq27200@55 {
arch/arm/boot/dts/omap3-n900.dts~: compatible =
"ti,bq27200";
arch/arm/boot/dts/omap3-n900.dts.orig: bq27200: bq27200@55 {
arch/arm/boot/dts/omap3-n900.dts.orig: compatible =
"ti,bq27200";
Binary file arch/arm/boot/dts/omap3-n950.dtb matches
arch/arm/boot/dts/omap3-n950-n9.dtsi: bq27521: bq27521@55 {
arch/arm/boot/dts/omap3-n950-n9.dtsi: compatible =
"ti,bq27521";
arch/arm/boot/dts/omap3-n950-n9.dtsi~: bq27521: bq27521@55 {
arch/arm/boot/dts/omap3-n950-n9.dtsi~: compatible =
"ti,bq27521";
arch/arm/boot/dts/omap3-n950-n9.dtsi.orig: bq27521: bq27521@55 {
arch/arm/boot/dts/omap3-n950-n9.dtsi.orig: compatible =
"ti,bq27521";
Binary file arch/arm/boot/dts/omap3-n9.dtb matches
arch/arm/boot/dts/omap3-pandora-common.dtsi: bq27500@55 {
arch/arm/boot/dts/omap3-pandora-common.dtsi: compatible
= "ti,bq27500";
arch/arm/boot/dts/qcom-apq8064-asus-nexus7-flo.dts:
bq27541@55 {
arch/arm/boot/dts/qcom-apq8064-asus-nexus7-flo.dts:
compatible = "ti,bq27541";
arch/arm/boot/dts/rk3288-veyron-minnie.dts: battery: bq27500@55 {
arch/arm/boot/dts/rk3288-veyron-minnie.dts: compatible =
"ti,bq27500";
pavel@duo:/data/l/linux-n900$
Is it possible that one wire subsystem registers bq27000 even without
device tree node?
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
prev parent reply other threads:[~2018-04-20 8:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-20 7:40 bq27000: directory/files exists even when hardware is not available Pavel Machek
2018-04-20 7:48 ` Pali Rohár
2018-04-20 8:17 ` Pavel Machek [this message]
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=20180420081741.GA8856@amd \
--to=pavel@ucw.cz \
--cc=afd@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=merlijn@wizzup.org \
--cc=mpartap@gmx.net \
--cc=nekit1000@gmail.com \
--cc=pali.rohar@gmail.com \
--cc=sre@kernel.org \
--cc=tony@atomide.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).