linux-kernel - Re: How to populate Battery information through ACPI tables

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] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 19 Feb 2013 19:42:10 +0200
From:	"Westerberg, Mika" <mika.westerberg@...el.com>
To:	"Pallala, Ramakrishna" <ramakrishna.pallala@...el.com>
Cc:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"Zhang, Rui" <rui.zhang@...el.com>
Subject: Re: How to populate Battery information through ACPI tables

On Tue, Feb 19, 2013 at 07:11:52PM +0200, Pallala, Ramakrishna wrote:
> 
> > On Tue, Feb 19, 2013 at 03:07:57PM +0000, Pallala, Ramakrishna wrote:
> > > I am trying to populate battery related information through ACPI
> > > tables and do battery management through non acpi drivers.  Can you
> > > tell or point me on how to populate the ACPI tables in FW/BIOS and get
> > > them in OS? I am new to ACPI world.
> > 
> > You should start by reading Documentation/acpi/enumeration.txt.
> > 
> > Also can you describe with bit more details, what you are trying to do? A new
> > battery driver that is enumerated from ACPI namespace, perhaps?
> > 
> > Do you have a DSDT table in hand which we could take a peek?
> 
> Thanks Mika for the pointers. I have looked at the documentation.
> 
> we already have i2c driver for battery monitoring but the chip needs initialized with
> characterization data. We wanted to populate/pass this data through ACPI table to the
> i2c slave driver.
> 
> How can I do that? Can I pass characterization data through ACPI table to
> the i2c slave device?

Is the characterization data available in DSDT (or SSDT) table? If yes,
then you can just use the fact that ACPI_HANDLE(&i2c_client->dev) returns a
valid ACPI handle for your device. You can use this handle to call some
ACPI method or whaterver is needed to extract that information.
--
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/