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 21:20:16 +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 08:59:29PM +0200, Pallala, Ramakrishna wrote:
> > > Mika, I want to populate this characterization data as device
> > > specific/custom data which could be anything And may not be entirely
> > > related to battery. Is this is possible?
> > 
> > Yes, for example you could have a custom ACPI method with your device which
> > then returns this information.
> > 
> > See for example chapter 10.2.2.1 from the ACPI spec. It describes _BIF method
> > that returns some battery data to the caller.
> 
> Mika, _BIF method returns battery data/struct which is defined Table. 10-233.

Yes, it was just an example. You can have your own custom method for that,
lets say:

	BLAH()

that then returns whatever you need.

> If I want to pass some device specific data seems like I can use
> _DSM(9.14.1) method and pass custom /device specific data to the driver.

_DSM is also an option, yes.

> And I believe this data format can be anything and private to the device?
> Can you confirm?

Yes.
--
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