Age | Commit message (Collapse) | Author | Files | Lines | |
---|---|---|---|---|---|
2021-12-09 | meta-ampere: mtjade: don't configure OCP GPIO when BMC rebooted | Thang Q. Nguyen | 1 | -2/+2 | |
Configure OCP_AUX_PWREN and/or OCP_MAIN_PWREN GPIOs, even without changing their values, make the OCP power glitched which consequently makes the Host OS generates many calltrace message. When BMC is rebooted, the ampere-gpio-poweron@service service is triggered that reconfigure these GPIOs. This comit prevents this case by checking if the Host is currently ON to skip the reconfiguration. Tested: 1. Boot the BMC and Host CPU. 2. Reboot BMC. Ensure no call trace for OCP Signed-off-by: Thang Q. Nguyen <thang@os.amperecomputing.com> Change-Id: I621e025adf72baf84bffd011ea0e04229f739755 | |||||
2021-08-04 | meta-ampere: mtjade: add mtjade-gpio-config package | ThuBaNguyen | 1 | -0/+10 | |
The OCP module in Mt.Jade platform supports the GPIO pins to set the power state. The SPI0 module also supports the GPIO pins to config SPI mode. These gpio pins have to be set to the right states before power off/on. The mtjade-gpio-config package will support that. Tested: 1. Power off/on the host. 2. The OCP and SPI0 gpio pins should be in the corrected states. Signed-off-by: ThuBaNguyen <thu@os.amperecomputing.com> Change-Id: I46bca50222b0428f73aa9c05003f650f6ec0cc0b |