From: "Chris Chen (TPI)" <Chris.Chen3@flex.com>
To: "openbmc@lists.ozlabs.org" <openbmc@lists.ozlabs.org>
Subject: [x86-power-control]: press the power button for a long time that can't force turn off system power
Date: Fri, 23 Jul 2021 10:28:39 +0000 [thread overview]
Message-ID: <DM6PR08MB55145CD3DC0AD96D30B70771DCE59@DM6PR08MB5514.namprd08.prod.outlook.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1723 bytes --]
Hi all,
I am working on an ast2600 with Intel CPU.
The system power currently is able to turn on during Phosphor OpenBMC boot up after I completed works following:
1. enable ACPI in u-boot
2. set GPIOP0 ~ P3 pass-through in u-boot
3. porting ESPI driver from AST SDK v6.01 to linux-aspeed repository
4. add "&gpio0" with gpio-line-names which has POWER_BUTTON, POWER_OUT, SIO_S3, SIO_S5, etc. defintion in the dts, I think the "x86-power-control" repository required these.
5. append "x86-power-control" and "intel-ipmi-oem" repositories to image
However, I always only got the following logs when I pressed the power button for a long time (> 4s).
=====
power-control[263]: PowerControl: power button pressed
power-control[263]: powerStateOn: power button pressed event received
power-control[263]: Host0: Moving to "Graceful Transition to Off" state
power-control[263]: Graceful power-off timer started
=====
It doesn't occur "SIO_ONCONTROL value changed: 1 -> SIO power good de-assert event received", etc. operations and then to turn off the power.
Can anyone do me a favor to give me some clues for what I was wrong?
Thank you in advance for your help.
Regards,
Chris Chen
Legal Disclaimer :
The information contained in this message may be privileged and confidential.
It is intended to be read only by the individual or entity to whom it is addressed
or by their designee. If the reader of this message is not the intended recipient,
you are on notice that any distribution of this message, in any form,
is strictly prohibited. If you have received this message in error,
please immediately notify the sender and delete or destroy any copy of this message!
[-- Attachment #2: Type: text/html, Size: 2938 bytes --]
next reply other threads:[~2021-07-23 11:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-23 10:28 Chris Chen (TPI) [this message]
2021-07-23 20:36 ` [x86-power-control]: press the power button for a long time that can't force turn off system power Bills, Jason M
2021-07-24 3:04 ` 回覆: " Chris Chen (TPI)
2021-07-26 16:46 ` Bills, Jason M
2021-08-16 3:52 ` Chris Chen (TPI)
2021-08-16 6:30 ` Andrew Jeffery
2021-08-16 10:45 ` 回覆: " Chris Chen (TPI)
2021-08-17 1:57 ` Andrew Jeffery
2021-08-17 11:17 ` Chris Chen (TPI)
2021-08-17 11:30 ` Andrew Jeffery
2021-08-17 19:04 ` Bills, Jason M
2021-08-18 11:07 ` 回覆: " Chris Chen (TPI)
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=DM6PR08MB55145CD3DC0AD96D30B70771DCE59@DM6PR08MB5514.namprd08.prod.outlook.com \
--to=chris.chen3@flex.com \
--cc=openbmc@lists.ozlabs.org \
/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).