From: "Andrew Jeffery" <andrew@aj.id.au>
To: "Chris Chen (TPI)" <Chris.Chen3@flex.com>,
"Bills, Jason M" <jason.m.bills@linux.intel.com>,
"openbmc@lists.ozlabs.org" <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
Date: Mon, 16 Aug 2021 16:00:32 +0930 [thread overview]
Message-ID: <878c1c79-662f-468d-82d1-a890a8aeab2e@www.fastmail.com> (raw)
In-Reply-To: <DM6PR08MB55145A59C44D48FFD5B70C26DCFD9@DM6PR08MB5514.namprd08.prod.outlook.com>
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
next prev parent reply other threads:[~2021-08-16 6:31 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 [this message]
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=878c1c79-662f-468d-82d1-a890a8aeab2e@www.fastmail.com \
--to=andrew@aj.id.au \
--cc=Chris.Chen3@flex.com \
--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).