public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Udit Kumar <udit.kumar@nxp.com>
To: "afish@apple.com" <afish@apple.com>
Cc: Daniel Thompson <daniel.thompson@linaro.org>,
	Ard Biesheuvel <ard.biesheuvel@linaro.org>,
	"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>,
	Leif Lindholm <leif.lindholm@linaro.org>
Subject: Re: [RFC] ACPI table HID/CID allocation
Date: Sun, 26 Nov 2017 08:35:20 +0000	[thread overview]
Message-ID: <AM6PR0402MB3334F91F923FC680C66F995991240@AM6PR0402MB3334.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <52514A09-FA53-4051-AA7F-F59F5E8F6D17@apple.com>


Hi Andrew 
 
> Udit,
> 
> I think it is more like you only need ACPI if you don't have a driver.

Ok, then ACPI or say firmware needs to export AML methods, which are known to OS.

> If it is standard bus with standard drivers the OS code can do power management
> without any help from ACPI. 

In some cases there could be some config registers in IP, which could 
leads to power down mode, then probably power management could be done
without ACPI. 
If we have clock and regulators doing power management,  then ACPI is needed.
No ? 

> In general ACPI exists to abstract chipsets that don't
> have OS drivers, or mother board layout of power plains, GPIOs, etc.

I can think of for power management, without specific driver if such
Power saving is limited to internal SOC.

For example, say temperature of mother board is read using 
some sensor connected with SOC over i2c line. And in SOC
i2c interface is behind some controller.
How do you see to read temperature without having a OS drivers.
For power management based on  temperature, we may not need a
driver.


Thanks,
 Udit


  reply	other threads:[~2017-11-26  8:31 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-21  9:19 [RFC] ACPI table HID/CID allocation Udit Kumar
2017-11-21  9:38 ` Ard Biesheuvel
2017-11-21  9:59   ` Udit Kumar
2017-11-21 10:13     ` Ard Biesheuvel
2017-11-21 11:32       ` Udit Kumar
2017-11-21 12:29         ` Ard Biesheuvel
2017-11-21 13:24           ` Udit Kumar
2017-11-21 14:03             ` Ard Biesheuvel
2017-11-21 18:10               ` Udit Kumar
2017-11-22 11:30                 ` Daniel Thompson
2017-11-22 13:39                   ` Udit Kumar
2017-11-22 17:34                     ` Andrew Fish
2017-11-25 12:40                       ` Udit Kumar
2017-11-22 19:39                   ` Ard Biesheuvel
2017-11-22 20:11                     ` Daniel Thompson
2017-11-25 12:56                       ` Udit Kumar
2017-11-25 19:41                         ` Andrew Fish
2017-11-26  8:35                           ` Udit Kumar [this message]
2017-11-27 12:13                         ` Daniel Thompson
2017-11-27 13:31                           ` Udit Kumar
2017-11-25 12:47                     ` Udit Kumar

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-list 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=AM6PR0402MB3334F91F923FC680C66F995991240@AM6PR0402MB3334.eurprd04.prod.outlook.com \
    --to=devel@edk2.groups.io \
    /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