openbmc.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Chris Chen (TPI)" <Chris.Chen3@flex.com>
To: Andrew Jeffery <andrew@aj.id.au>,
	"Bills, Jason M" <jason.m.bills@linux.intel.com>,
	"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: Mon, 16 Aug 2021 10:45:38 +0000	[thread overview]
Message-ID: <DM6PR08MB551444C4EAB80473CB576740DCFD9@DM6PR08MB5514.namprd08.prod.outlook.com> (raw)
In-Reply-To: <878c1c79-662f-468d-82d1-a890a8aeab2e@www.fastmail.com>

[-- Attachment #1: Type: text/plain, Size: 3477 bytes --]

Hi Andrew,

Thanks for your hint (CONFIG_DEBUG_PINCTRL=y) that let me see where the passthrough setting was disabled.
======
[   11.631044] aspeed-g6-pinctrl 1e6e2000.syscon:pinctrl: request pin 120 (AB22) for 1e780000.gpio:120
[   11.631064] Muxing pin 120 for GPIO
[   11.631071] Disabling signal PWM8 for PWM8
[   11.631087] Want SCU41C[0x01000000]=0x1, got 0x0 from 0x000000C0
[   11.631094] Disabling signal THRUIN0 for THRU0
[   11.631102] Want SCU4BC[0x01000000]=0x1, got 0x1 from 0x0F000000
[   11.631118] Want SCU4BC[0x01000000]=0x0, got 0x0 from 0x0E000000
[   11.631124] Enabling signal GPIOP0 for GPIOP0
======

But something strange is the logs seems from "x86-power-control" package because it would not appear after I commented out partial code as below in the package.
Could you or others tell me why, please? I mean did I miss any configurations or code changes or anything when using the "x86-power-control" package?

#if 0 //Added by Chris for testing
    // Request POWER_BUTTON GPIO events
    if (!powerButtonName.empty())
    {
        if (!requestGPIOEvents(powerButtonName, powerButtonHandler,
                               powerButtonLine, powerButtonEvent))
        {
            return -1;
        }
    }
    else
    {
        phosphor::logging::log<phosphor::logging::level::ERR>(
            "powerButton name should be configured from json config file");
        return -1;
    }
#endif //Added by Chris for testing

Another, last time I forgot to say that I have tried to use "devmem 0x1e6e24BC 32 0x0F000000" to set passthrough back manually and the power button works fine. This is why I think the passthrough was gone after the system booting up.

Regards,
Chris Chen


________________________________
寄件者: Andrew Jeffery <andrew@aj.id.au>
寄件日期: 2021年8月16日 下午 02:30
收件者: Chris Chen (TPI) <Chris.Chen3@flex.com>; Bills, Jason M <jason.m.bills@linux.intel.com>; openbmc@lists.ozlabs.org <openbmc@lists.ozlabs.org>
主旨: Re: [x86-power-control]: press the power button for a long time that can't force turn off system power

Hi Chris,

On Mon, 16 Aug 2021, at 13:22, Chris Chen (TPI) wrote:
> Hi Jason and others,
>
> I think I figured out the problem is the GPIOP0 and GPIOP1 passthrough
> was not set after system booting up. However, as I mentioned when
> rising the question, I have already set GPIOP0 and P1 passthrough in
> u-boot, it for now looks like was been turned off during Kernel or
> OpenBMC application running up. Can you please give me a clue why the
> GPIO passthrough would be turned off or where should I need to add
> passthrough setting again?
>

If the kernel is disabling it you might be able to find the cause with
CONFIG_DEBUG_PINCTRL=y and the pinctrl attributes in debugfs. Having
said that, the upstream kernel hasn't been taught about SCU510[28] on
the 2600, so if it is touching it then it's doing so via out-of-tree
patches.

Andrew

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: 8896 bytes --]

  reply	other threads:[~2021-08-16 10:46 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-23 10:28 Chris Chen (TPI)
2021-07-23 20:36 ` 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) [this message]
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=DM6PR08MB551444C4EAB80473CB576740DCFD9@DM6PR08MB5514.namprd08.prod.outlook.com \
    --to=chris.chen3@flex.com \
    --cc=andrew@aj.id.au \
    --cc=jason.m.bills@linux.intel.com \
    --cc=openbmc@lists.ozlabs.org \
    --subject='Re: 回覆: [x86-power-control]: press the power button for a long time that can'\''t force turn off system power' \
    /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

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