lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:   Fri, 20 Apr 2018 10:17:42 +0200
From:   Pavel Machek <pavel@....cz>
To:     Pali Rohár <pali.rohar@...il.com>
Cc:     kernel list <linux-kernel@...r.kernel.org>,
        linux-arm-kernel <linux-arm-kernel@...ts.infradead.org>,
        linux-omap@...r.kernel.org, tony@...mide.com, sre@...nel.org,
        nekit1000@...il.com, mpartap@....net, merlijn@...zup.org,
        afd@...com, linux-pm@...r.kernel.org
Subject: Re: bq27000: directory/files exists even when hardware is not
 available

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

Download attachment "signature.asc" of type "application/pgp-signature" (182 bytes)

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ