回信:Re: [PATCH linux] Add debounce for power button, pull down gpioQ7 to unlock identify LED

ken.th.liu at foxconn.com ken.th.liu at foxconn.com
Tue May 17 13:05:22 AEST 2016


<DIV style="FONT-SIZE: 10pt; FONT-FAMILY: Microsoft Sans Serif">Hi Adri<BR><BR>Response as below.</DIV>
<DIV style="FONT-SIZE: 10pt; FONT-FAMILY: Microsoft Sans Serif"><BR>========================================<BR><BR>劉亭宏 Ken Liu<BR>Foxconn / Hon Hai Precision Ind. Co., Ltd.<BR>CESBG - Cloud Enterprise Solution Business Group<BR>SRD1<BR>Firmware Development Department<BR>TEL: +886-2-2268-3466 <BR>Ext. : 511 + 2704   (虎躍廠)                                 <BR>Engineer (BMC Firmware)<BR>E-mail : ken.th.liu at foxconn.com<BR>(Ken T.H. Liu/CES/SUPERNOTES)<BR>2, Zihyou St., TU-CHENG, New TAIPEI City, 23644, Taiwan, R.O.C<BR><BR>========================================</DIV>
<DIV style="FONT-SIZE: 10pt; FONT-FAMILY: Microsoft Sans Serif"><BR>
<HR>
<LABEL style="FONT-SIZE: 10pt; FONT-FAMILY: Microsoft Sans Serif">本電子郵件及附件所載信息均為保密信息,受合同保護或依法不得洩漏。其內容僅供指定收件人按限定範圍或特殊目的使用。未經授權者收到此信息均無權閱讀、 使用、 複製、洩漏或散佈。若您因為誤傳而收到本郵件或者非本郵件之指定收件人,請即刻回覆郵件或致電Super Notes郵件客服熱線 560-104,並永久刪除此郵件及其附件和銷毀所有複印件。謝謝您的合作!<BR>This e-mail message together with any attachments thereto (if any) is confidential, protected under an enforceable non-disclosure agreement, intended only for the use of the named recipient(s) above and may contain information that is privileged, belonging to professional work products or exempt from disclosure under applicable laws.Any unauthorized review, use, copying, disclosure, or distribution of any information contained in or attached to this transmission is STRICTLY PROHIBITED and may be against the laws. If you have received this message in error, or are not the named recipient(s), please immediately notify the sender by e-mail or telephone at Super Notes support hotline 560-104 and delete this e-mail message and any attached documentation from your computer. Receipt by anyone other than the intended recipient(s) is not a waiver of any attorney-client or work product privilege. Thank you!</LABEL><BR>
<HR>
</DIV>
<DIV style="FONT-SIZE: 10pt; FONT-FAMILY: Microsoft Sans Serif"></DIV>
<DIV><BR>
<HR>
<LABEL style="COLOR: #cc0099">— 回信者 ken.th.liu at mail.foxconn.com 於 2016/5/17 上午 10:57:25 —</LABEL><BR><BR>
<TABLE border=0>
<TBODY>
<TR>
<TD width=50></TD>
<TD style="COLOR: #0000ff" width=220>anoo at us.ibm.com</TD>
<TD style="COLOR: #0000ff" width=50 align=right>To: </TD>
<TD style="BORDER-TOP: 2px ridge; BORDER-RIGHT: 2px ridge; BORDER-BOTTOM: 2px ridge; BORDER-LEFT: 2px ridge" width=1000 noWrap>ken.th.liu at mail.foxconn.com</TD></TR>
<TR>
<TD width=50></TD>
<TD width=220></TD>
<TD style="COLOR: #0000ff" width=50 align=right>Cc: </TD>
<TD style="BORDER-TOP: 2px ridge; BORDER-RIGHT: 2px ridge; BORDER-BOTTOM: 2px ridge; BORDER-LEFT: 2px ridge" width=1000 noWrap>openbmc-patches at stwcx.xyz,openbmc at lists.ozlabs.org,joel at jms.id.au</TD></TR>
<TR>
<TD width=50></TD>
<TD style="COLOR: #0000ff" width=220>2016/5/17 上午 02:26:11</TD>
<TD style="COLOR: #0000ff" width=50 align=right>主旨: </TD>
<TD style="BORDER-TOP: 2px ridge; BORDER-RIGHT: 2px ridge; BORDER-BOTTOM: 2px ridge; BORDER-LEFT: 2px ridge" width=1000 noWrap>Re: [PATCH linux] Add debounce for power button, pull down gpioQ7 to unlock identify LED</TD></TR></TBODY></TABLE><BR></DIV>
<P style="MARGIN: 2px"><FONT size=3>Hi Ken,</FONT><BR><BR><FONT size=3>Could you reply to Joel if you have any questions about his comments or make a new pull request so that the change can be merged? Specifically is provide more info regarding the changes, I'm copying the comments here. Thanks.</FONT><BR><BR><BR><TT><FONT size=3>>> From: Ken <ken.sk.lai at mail.foxconn.com></FONT></TT><BR><TT><FONT size=3>> We need to include a description of why this change is being made.<BR>> What does it fix? Why does the previous behaviour need to be modified?</FONT></TT></P>
<P style="MARGIN: 2px"><TT><FONT color=#0080ff>It's fix when power on, the identify led can not be controlled.</FONT></TT></P>
<P style="MARGIN: 2px"><TT><FONT color=#0080ff>And power button issue.</FONT></TT></P>
<P style="MARGIN: 2px"><BR><BR><TT><FONT size=3>>> +       writel(0x00001080, AST_IO(AST_BASE_GPIO | 0x84));<BR>> We have a GPIO driver that handles setting this register.</FONT></TT><BR></P>
<P style="MARGIN: 2px"><FONT color=#0080ff>OK. We can move the code to skeleton.</FONT></P>
<P style="MARGIN: 2px"><FONT color=#0080ff></FONT> </P>
<P style="MARGIN: 2px"><FONT color=#0080ff>The GPIO is for unlock Identify LED by GPIOQ7 when power on.</FONT></P><BR><TT><FONT size=3>>> +       writel(0x010FFFFF, AST_IO(AST_BASE_SCU | 0xA8));<BR>> Can you explain each of these you're setting each of these bits?</FONT></TT><BR>
<P style="MARGIN: 2px"><FONT color=#0080ff>It's a long story, please check the attachment mail history.</FONT></P>
<P style="MARGIN: 2px"> </P>
<P style="MARGIN: 2px"><FONT color=#0080ff>To conclude, to avoid the debounce pulse for power button interrupt.</FONT></P>
<P style="MARGIN: 2px"><BR><BR><BR><BR><FONT size=3>From:        </FONT><FONT size=3>Joel Stanley <joel at jms.id.au></FONT><BR><FONT size=3>To:        </FONT><FONT size=3>OpenBMC Patches <openbmc-patches at stwcx.xyz>, ken.th.liu at foxconn.com</FONT><BR><FONT size=3>Cc:        </FONT><FONT size=3>OpenBMC Maillist <openbmc at lists.ozlabs.org></FONT><BR><FONT size=3>Date:        </FONT><FONT size=3>05/12/2016 02:11 AM</FONT><BR><FONT size=3>Subject:        </FONT><FONT size=3>Re: [PATCH linux] Add debounce for power button, pull down gpioQ7 to unlock identify LED</FONT><BR><FONT size=3>Sent by:        </FONT><FONT size=3>"openbmc" <openbmc-bounces+anoo=us.ibm.com at lists.ozlabs.org></FONT><BR>
<HR noShade>
<BR><BR><BR><TT><FONT size=3>ping<BR><BR>On Mon, May 2, 2016 at 11:12 AM, Joel Stanley <joel at jms.id.au> wrote:<BR>> On Fri, Apr 29, 2016 at 3:10 PM, OpenBMC Patches<BR>> <openbmc-patches at stwcx.xyz> wrote:<BR>>> From: Ken <ken.sk.lai at mail.foxconn.com><BR>>><BR>><BR>> We need to include a description of why this change is being made.<BR>> What does it fix? Why does the previous behaviour need to be modified?<BR>><BR>>> ---<BR>>>  arch/arm/mach-aspeed/aspeed.c | 8 ++++++--<BR>>>  1 file changed, 6 insertions(+), 2 deletions(-)<BR>>>  mode change 100644 => 100755 arch/arm/mach-aspeed/aspeed.c<BR>>><BR>>> diff --git a/arch/arm/mach-aspeed/aspeed.c b/arch/arm/mach-aspeed/aspeed.c<BR>>> old mode 100644<BR>>> new mode 100755<BR>>> index 594a781..fa5d467<BR>>> --- a/arch/arm/mach-aspeed/aspeed.c<BR>>> +++ b/arch/arm/mach-aspeed/aspeed.c<BR>>> @@ -138,9 +138,10 @@ static void __init do_barreleye_setup(void)<BR>>>         /* GPIO setup */<BR>>>         writel(0x9E82FCE7, AST_IO(AST_BASE_GPIO | 0x00));<BR>>>         writel(0x0370E677, AST_IO(AST_BASE_GPIO | 0x04));<BR>>> -<BR>>> +       writel(0x00001080, AST_IO(AST_BASE_GPIO | 0x84));<BR>><BR>> We have a GPIO driver that handles setting this register.<BR>><BR>>>         /* SCU setup */<BR>>>         writel(0x01C00000, AST_IO(AST_BASE_SCU | 0x88));<BR>>> +       writel(0x010FFFFF, AST_IO(AST_BASE_SCU | 0xA8));<BR>><BR>> Can you explain each of these you're setting each of these bits?<BR>><BR>>>         /*<BR>>>          * Do read/modify/write on power gpio to prevent resetting power on<BR>>> @@ -150,7 +151,10 @@ static void __init do_barreleye_setup(void)<BR>>>         reg |= 0xCFC8F7FD;<BR>>>         writel(reg, AST_IO(AST_BASE_GPIO | 0x20));<BR>>>         writel(0xC738F20A, AST_IO(AST_BASE_GPIO | 0x24));<BR>>> -       writel(0x0031FFAF, AST_IO(AST_BASE_GPIO | 0x80));<BR>>> +       writel(0x0031FF2F, AST_IO(AST_BASE_GPIO | 0x80));<BR>>> +       writel(0x00000001, AST_IO(AST_BASE_GPIO | 0x48));<BR>>> +       writel(0x00000001, AST_IO(AST_BASE_GPIO | 0x4C));<BR>>> +       writel(0x00075300, AST_IO(AST_BASE_GPIO | 0x58));<BR>><BR>> As above; we have a GPIO driver that handles setting this register.<BR>> Changing these states needs to be done from userspace. See<BR>> </FONT></TT><A href="https://github.com/openbmc/skeleton/blob/master/bin/Barreleye.py#L531"><TT><FONT size=3>https://github.com/openbmc/skeleton/blob/master/bin/Barreleye.py#L531</FONT></TT></A><TT><FONT size=3><BR>_______________________________________________<BR>openbmc mailing list<BR>openbmc at lists.ozlabs.org<BR></FONT></TT><A href="https://lists.ozlabs.org/listinfo/openbmc"><TT><FONT size=3>https://lists.ozlabs.org/listinfo/openbmc</FONT></TT></A><TT><FONT size=3><BR></FONT></TT><BR><BR><BR>
<P></P>
<DIV style="FONT-SIZE: 10pt; FONT-FAMILY: Microsoft Sans Serif"><BR>mail from ip-->10.38.3.183<BR>mail from pc-->KEN<BR>Version: Super Notes 1.6.5.9B</DIV>
<DIV style="FONT-SIZE: 10pt; FONT-FAMILY: Microsoft Sans Serif"><BR></DIV>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ozlabs.org/pipermail/openbmc/attachments/20160517/873bd50b/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: System Power on Automatically Issue.pdf
Type: application/octet-stream
Size: 294489 bytes
Desc: not available
URL: <http://lists.ozlabs.org/pipermail/openbmc/attachments/20160517/873bd50b/attachment-0001.obj>


More information about the openbmc mailing list