Revision (<<< Hide revision tags) (Show revision tags >>>) Date Author Comments
# bc0e1c0c 10-Mar-2025 Sean He <sean.he.wiwynn@gmail.com>

meta-facebook: yosemite4: set i3c hub register

This action is currently handled by the I3C hub driver.
However, it may result in EID loss if slots are removed.
To address this, we perform the same a

meta-facebook: yosemite4: set i3c hub register

This action is currently handled by the I3C hub driver.
However, it may result in EID loss if slots are removed.
To address this, we perform the same action in the
Early-init service by checking the presence of the slots
and writing the correct values to the register. This
approach helps resolve the issue.

Change-Id: Id1b64f954a13cb81fda855ac0611290320641e06
Signed-off-by: Sean He <sean.he.wiwynn@gmail.com>

show more ...


# 7d7b3459 26-Mar-2025 Zoey YJ Chung <zoey.yj.chung.wiwynn@gmail.com>

meta-facebook: yosemite4: Adjust all fan PWM to 70% as default

Summary:
Set all the fans' PWM to 70% to prevent the fans' speed exceed the UNC
before starting the phosphor-pid-control service.
(base

meta-facebook: yosemite4: Adjust all fan PWM to 70% as default

Summary:
Set all the fans' PWM to 70% to prevent the fans' speed exceed the UNC
before starting the phosphor-pid-control service.
(based on thermal team's requirements)

Tested:
Checked all the fans' PWM are 70% before phosphor-pid-control service
starts.

Change-Id: I4fe2258ec9e6789b5a7f08855ae972d7146ea399
Signed-off-by: Zoey YJ Chung <zoey.yj.chung.wiwynn@gmail.com>

show more ...


# c5617208 14-Feb-2025 Eric Yang <eric.yang.wiwynn@gmail.com>

meta-facebook: yosemite4: modify service window

Service window changes fan duty to 90% when a slot is unplugged.
Currently, it uses the virtual sensor
SENTINEL_DOME_SLOT_PRESENT_PERCENTAGE to monito

meta-facebook: yosemite4: modify service window

Service window changes fan duty to 90% when a slot is unplugged.
Currently, it uses the virtual sensor
SENTINEL_DOME_SLOT_PRESENT_PERCENTAGE to monitor each slot's
MB_FIO_TEMP sensor to detect slot removal.
However, this triggers the service window during slot AC off.

Therefore, change implementation to modify
SENTINEL_DOME_SLOT_PRESENT_PERCENTAGE value when GPIO monitors slot
PRSNT PIN changes.

- Test Plan:
Build code - pass
Fan speed does not change to 90% during one slot AC off - pass
Fan duty changes to 90% after slot is unplugged - pass

Change-Id: I294d041ee8b66916b021327ee6f616793eedd034
Signed-off-by: Eric Yang <eric.yang.wiwynn@gmail.com>

show more ...


Revision tags: 2.18.0-dev
# 4fe85488 30-Oct-2024 Ricky CX Wu <ricky.cx.wu.wiwynn@gmail.com>

yosemite4: enable mctp-i3c between BMC and SD BIC

Use MCTP-I3C between BMC and SD BIC for ASPEED BMC.

Change-Id: Ic2af8fe54e8995549e04b64fff2f052a7137b331
Signed-off-by: Ricky CX Wu <ricky.cx.wu.wi

yosemite4: enable mctp-i3c between BMC and SD BIC

Use MCTP-I3C between BMC and SD BIC for ASPEED BMC.

Change-Id: Ic2af8fe54e8995549e04b64fff2f052a7137b331
Signed-off-by: Ricky CX Wu <ricky.cx.wu.wiwynn@gmail.com>

show more ...


# e81cec1e 16-Oct-2024 Bright Cheng <bright_cheng@wiwynn.com>

meta-facebook: yosemite4: set powerstate for empty slots

The power state of empty slot is not handled correctly due to
obmc-chassis-poweron@{}.target keeping active.

1. Get present pins of slots in

meta-facebook: yosemite4: set powerstate for empty slots

The power state of empty slot is not handled correctly due to
obmc-chassis-poweron@{}.target keeping active.

1. Get present pins of slots in yosemite4-early-sys-init.
2. Add a judgement in power control scripts to return fail when slot is
not present.
3. Add service to handle power control failure.

Tested:
1. Get power state while Yv4 being powered on with some empty slots, the
power state of empty slots should be off - pass.

Change-Id: I3b8c10bb12d6e54cbe89834962e52039bb497c83
Signed-off-by: Bright Cheng <bright.cheng.wiwynn@gmail.com>

show more ...


# 91d1d0fc 17-Sep-2024 Ricky CX Wu <ricky.cx.wu.wiwynn@gmail.com>

meta-facebook: yosemite4: set all fan PWM to 80% as default

The fan IC will set the PWM to 100% after sled cycle, so the fans' speed
will exceed the warning threshold before the fan control service

meta-facebook: yosemite4: set all fan PWM to 80% as default

The fan IC will set the PWM to 100% after sled cycle, so the fans' speed
will exceed the warning threshold before the fan control service
starts.

Set all the fans' PWM to 80% to prevent the fans' speed exceed the
warning threshold before starting the phosphor-pid-control service.

Tested:
Checked all the fans' PWM are 80% before phosphor-pid-control service
starts.

Change-Id: I955f41b20c770aaad4a8176179dd20b11abde52f
Signed-off-by: Ricky CX Wu <ricky.cx.wu.wiwynn@gmail.com>

show more ...


# 8a1dbe29 24-Sep-2024 Marshall Zhan <marshall.zhan.wiwynn@gmail.com>

meta-facebook: yosemite4: Adjust I2C 11 clock duty cycle

In order to have better margin, modify the duty cycle of the i2c bus.

Change-Id: I752083eb7e9187c88b3915eb5b3c061c89108543
Signed-off-by: Ma

meta-facebook: yosemite4: Adjust I2C 11 clock duty cycle

In order to have better margin, modify the duty cycle of the i2c bus.

Change-Id: I752083eb7e9187c88b3915eb5b3c061c89108543
Signed-off-by: Marshall Zhan <marshall.zhan.wiwynn@gmail.com>

show more ...


# 4682d54c 15-Aug-2024 Allen.Wang <Allen_Wang@quantatw.com>

meta-facebook: yosemite4: Fix yosemite4-sys-init fail to start

yosemite4-sys-init fails while mknod which already exist,
check if node exist to avoid fail exit.

Tested:

-before:
root@bmc:~# system

meta-facebook: yosemite4: Fix yosemite4-sys-init fail to start

yosemite4-sys-init fails while mknod which already exist,
check if node exist to avoid fail exit.

Tested:

-before:
root@bmc:~# systemctl status yosemite4-sys-init.service
× yosemite4-sys-init.service - Yosemite4 Early System Init
Loaded: loaded (/usr/lib/systemd/system/yosemite4-sys-init.service; enabled; preset: enabled)
Active: failed (Result: exit-code) since Wed 2024-08-14 20:18:23 PDT; 38s ago
Process: 644 ExecStart=/usr/libexec/yosemite4-early-sys-init (code=exited, status=1/FAILURE)
Main PID: 644 (code=exited, status=1/FAILURE)
CPU: 642ms

Aug 14 20:18:23 bmc Yosemite4 Early Init[644]: set_gpio: set EN_P3V_BAT_SCALED_R = 0 success
Aug 14 20:18:23 bmc Yosemite4 Early Init[644]: set_gpio: set FM_BMC_SLED_CYCLE_R = 0 success
Aug 14 20:18:23 bmc Yosemite4 Early Init[644]: set_gpio: set NIC0_MAIN_PWR_EN = 1 success
Aug 14 20:18:23 bmc Yosemite4 Early Init[644]: set_gpio: set NIC1_MAIN_PWR_EN = 1 success
Aug 14 20:18:23 bmc Yosemite4 Early Init[644]: set_gpio: set NIC2_MAIN_PWR_EN = 1 success
Aug 14 20:18:23 bmc Yosemite4 Early Init[644]: set_gpio: set NIC3_MAIN_PWR_EN = 1 success
Aug 14 20:18:23 bmc Yosemite4 Early Init[735]: mknod: /dev/mem: File exists
Aug 14 20:18:23 bmc systemd[1]: yosemite4-sys-init.service: Main process exited, code=exited, status=1/FAILURE
Aug 14 20:18:23 bmc systemd[1]: yosemite4-sys-init.service: Failed with result 'exit-code'.
Aug 14 20:18:23 bmc systemd[1]: Failed to start Yosemite4 Early System Init.

-after:
root@bmc:~# systemctl status yosemite4-sys-init.service
○ yosemite4-sys-init.service - Yosemite4 Early System Init
Loaded: loaded (/usr/lib/systemd/system/yosemite4-sys-init.service; enabled; preset: enabled)
Active: inactive (dead) since Thu 2024-08-15 00:23:02 PDT; 1h 1min ago
Process: 646 ExecStart=/usr/libexec/yosemite4-early-sys-init (code=exited, status=0/SUCCESS)
Main PID: 646 (code=exited, status=0/SUCCESS)
CPU: 658ms

Signed-off-by: Allen.Wang <Allen_Wang@quantatw.com>
Change-Id: I3e4ec67f8eeb4389b970d60c7cbca05d9474db7a

show more ...


# 9f2ebc96 30-Jul-2024 Ricky CX Wu <ricky.cx.wu.wiwynn@gmail.com>

meta-facebook: yosemite4: adjust the function to enable fan input

There is no fanX_enable for 2nd source Fan IC: NCT7363, so search the
fanX_enable before setting it.

Also removed the "-e" to preve

meta-facebook: yosemite4: adjust the function to enable fan input

There is no fanX_enable for 2nd source Fan IC: NCT7363, so search the
fanX_enable before setting it.

Also removed the "-e" to prevent the script exit without doing all the
steps.

Tested:
Checked the yosemite4-sys-init.service would not failed with 2nd source
fan IC.

Change-Id: I3668c1656d30a621b7140a06a88b9f1bb62fa413
Signed-off-by: Ricky CX Wu <ricky.cx.wu.wiwynn@gmail.com>

show more ...


# a365e4bb 18-Jul-2024 MarshallZhan <Marshall_Zhan@wiwynn.com>

meta-facebook: yosemite4: Adjust sled cycle method

Use FRU information to distinguish different sled cycle methods.

PVT or after : notify CPLD by GPIOO7
Before PVT : notify CPLD by CPLD IO expender

meta-facebook: yosemite4: Adjust sled cycle method

Use FRU information to distinguish different sled cycle methods.

PVT or after : notify CPLD by GPIOO7
Before PVT : notify CPLD by CPLD IO expender

Tested:
Did sled cycle on EVT, DVT an PVT system.

Change-Id: Iad82056ff9a57ef6bf39ec1978c5d099b55706a9
Signed-off-by: Marshall Zhan <marshall.zhan.wiwynn@gmail.com>

show more ...


# 52b63362 22-Jul-2024 Tim Lee <timlee660101@gmail.com>

meta-facebook: yosemite4: refactor common function for stability

Refactor `check_nuvoton_board` function to avoid some scritps define
`set -e` in the beginning of `#!/bin/bash` that will think faile

meta-facebook: yosemite4: refactor common function for stability

Refactor `check_nuvoton_board` function to avoid some scritps define
`set -e` in the beginning of `#!/bin/bash` that will think failed when
return value is non-zero and related services might got failed also.

Tested:
Run related services successfully.
root@bmc:/# systemctl status yosemite4-sys-init.service
bmc systemd[1]: Starting Yosemite4 Early System Init...
bmc systemd[1]: yosemite4-sys-init.service: Deactivated successfully.
bmc systemd[1]: Finished Yosemite4 Early System Init.

root@bmc:/# systemctl status mctpd.service
* mctpd.service - MCTP control protocol daemon
Drop-In: /usr/lib/systemd/system/mctpd.service.d
`-setup-local-eid.conf, setup-static-endpoints.conf

Signed-off-by: Tim Lee <timlee660101@gmail.com>
Change-Id: I6045d6ae6349cf84f0e920e4d219def602515809

show more ...


# 68f27092 18-Jul-2024 Tim Lee <timlee660101@gmail.com>

meta-facebook: yosemite4: gpio: set interface of SD BIC to I3C

Set interface to SD BIC to I3C for Nuvoton BMC.

Tested:
Run yosemite4-early-sys-init successfully and boot up pass.

Signed-off-by: Ti

meta-facebook: yosemite4: gpio: set interface of SD BIC to I3C

Set interface to SD BIC to I3C for Nuvoton BMC.

Tested:
Run yosemite4-early-sys-init successfully and boot up pass.

Signed-off-by: Tim Lee <timlee660101@gmail.com>
Change-Id: I0dc5f97257cd0ab634eb12413126ea8ac42bc754

show more ...


# 1b847b2c 18-Jul-2024 Tim Lee <timlee660101@gmail.com>

meta-facebook: yosemite4: adjust yosemite4-early-sys-init for common use

For different management boards specific initialization.

Tested:
Run yosemite4-early-sys-init successfully and boot up pass.

meta-facebook: yosemite4: adjust yosemite4-early-sys-init for common use

For different management boards specific initialization.

Tested:
Run yosemite4-early-sys-init successfully and boot up pass.

Signed-off-by: Tim Lee <timlee660101@gmail.com>
Change-Id: Idaab0185ac936e05c3cda482e39a2793a84f025a

show more ...


Revision tags: 2.17.0-dev
# 1fd57fe1 03-Apr-2024 Allen.Wang <Allen_Wang@quantatw.com>

meta-facebook: yosemite4: Enable all fan input initially

Summary:

Fan controller need a time interval to count fan speed,to read fan speed
immediately after enable fan input will get a fake zero re

meta-facebook: yosemite4: Enable all fan input initially

Summary:

Fan controller need a time interval to count fan speed,to read fan speed
immediately after enable fan input will get a fake zero reading.

Enable all fan input to prevent bmc log fan sensor read 0 value and
logging critical low threshold assert during SLED cycle.

Tested:
Tested pass on yosemite4 system.

Before change:

Log a fake low threshold assert and it deaaset 1 sec later due to fan controller success to read an actual reading

{
"@odata.id": "/redfish/v1/Systems/system/LogServices/EventLog/Entries/13",
"@odata.type": "#LogEntry.v1_9_0.LogEntry",
"AdditionalDataURI": "/redfish/v1/Systems/system/LogServices/EventLog/Entries/13/attachment",
"Created": "2023-12-15T20:25:29.312+00:00",
"EntryType": "Event",
"Id": "13",
"Message": "FANBOARD0_FAN0_TACH_IL critical low threshold assert. Reading=0.000000 Threshold=1000.000000.",
"Modified": "2023-12-15T20:25:29.312+00:00",
"Name": "System Event Log Entry",
"Resolved": false,
"Severity": "Critical"
},
{
"@odata.id": "/redfish/v1/Systems/system/LogServices/EventLog/Entries/15",
"@odata.type": "#LogEntry.v1_9_0.LogEntry",
"AdditionalDataURI": "/redfish/v1/Systems/system/LogServices/EventLog/Entries/15/attachment",
"Created": "2023-12-15T20:25:30.226+00:00",
"EntryType": "Event",
"Id": "15",
"Message": "FANBOARD0_FAN0_TACH_IL critical low threshold deassert. Reading=15603.000000 Threshold=1000.000000.",
"Modified": "2023-12-15T20:25:30.226+00:00",
"Name": "System Event Log Entry",
"Resolved": false,
"Severity": "OK"
},
{
"@odata.id": "/redfish/v1/Systems/system/LogServices/EventLog/Entries/14",
"@odata.type": "#LogEntry.v1_9_0.LogEntry",
"AdditionalDataURI": "/redfish/v1/Systems/system/LogServices/EventLog/Entries/14/attachment",
"Created": "2023-12-15T20:25:30.187+00:00",
"EntryType": "Event",
"Id": "14",
"Message": "FANBOARD0_FAN0_TACH_IL warning high threshold assert. Reading=15603.000000 Threshold=13915.000000.",
"Modified": "2023-12-15T20:25:30.187+00:00",
"Name": "System Event Log Entry",
"Resolved": false,
"Severity": "Warning"
},

After change:
No fake low threshold assert/deassert occurs during sled cycle

cat sledcycle.log|grep FANBOARD
[2024-04-03 12:07:15.363] "Message": "FANBOARD0_FAN1_TACH_OL warning high threshold assert. Reading=13466.000000 Threshold=11970.000000.",
[2024-04-03 12:07:15.392] "Message": "FANBOARD0_FAN1_TACH_IL warning high threshold assert. Reading=15603.000000 Threshold=13140.000000.",
[2024-04-03 12:07:15.413] "Message": "FANBOARD0_FAN0_TACH_OL warning high threshold assert. Reading=13284.000000 Threshold=11970.000000.",
[2024-04-03 12:07:15.413] "Message": "FANBOARD0_FAN2_TACH_OL warning high threshold assert. Reading=13284.000000 Threshold=11970.000000.",
[2024-04-03 12:07:15.424] "Message": "FANBOARD0_FAN2_TACH_IL warning high threshold assert. Reading=15603.000000 Threshold=13140.000000.",
[2024-04-03 12:07:15.441] "Message": "FANBOARD0_FAN0_TACH_IL warning high threshold assert. Reading=15603.000000 Threshold=13140.000000.",
[2024-04-03 12:07:15.441] "Message": "FANBOARD1_FAN1_TACH_OL warning high threshold assert. Reading=13284.000000 Threshold=11970.000000.",
[2024-04-03 12:07:15.455] "Message": "FANBOARD1_FAN1_TACH_IL warning high threshold assert. Reading=15603.000000 Threshold=13140.000000.",
[2024-04-03 12:07:15.455] "Message": "FANBOARD1_FAN0_TACH_OL warning high threshold assert. Reading=13466.000000 Threshold=11970.000000.",
[2024-04-03 12:07:15.471] "Message": "FANBOARD1_FAN2_TACH_OL warning high threshold assert. Reading=13466.000000 Threshold=11970.000000.",
[2024-04-03 12:07:15.488] "Message": "FANBOARD1_FAN2_TACH_IL warning high threshold assert. Reading=15603.000000 Threshold=13140.000000.",
[2024-04-03 12:07:15.488] "Message": "FANBOARD1_FAN0_TACH_IL warning high threshold assert. Reading=15603.000000 Threshold=13140.000000.",
[2024-04-03 12:07:15.503] "Message": "FANBOARD0_FAN4_TACH_OL warning high threshold assert. Reading=13107.000000 Threshold=11970.000000.",
[2024-04-03 12:07:15.503] "Message": "FANBOARD0_FAN4_TACH_IL warning high threshold assert. Reading=15603.000000 Threshold=13140.000000.",
[2024-04-03 12:07:15.515] "Message": "FANBOARD0_FAN3_TACH_OL warning high threshold assert. Reading=13284.000000 Threshold=11970.000000.",
[2024-04-03 12:07:15.531] "Message": "FANBOARD0_FAN5_TACH_OL warning high threshold assert. Reading=13284.000000 Threshold=11970.000000.",
[2024-04-03 12:07:15.531] "Message": "FANBOARD0_FAN5_TACH_IL warning high threshold assert. Reading=15603.000000 Threshold=13140.000000.",
[2024-04-03 12:07:15.548] "Message": "FANBOARD0_FAN3_TACH_IL warning high threshold assert. Reading=15855.000000 Threshold=13140.000000.",
[2024-04-03 12:07:15.565] "Message": "FANBOARD1_FAN4_TACH_OL warning high threshold assert. Reading=13284.000000 Threshold=11970.000000.",
[2024-04-03 12:07:15.565] "Message": "FANBOARD1_FAN4_TACH_IL warning high threshold assert. Reading=15603.000000 Threshold=13140.000000.",
[2024-04-03 12:07:15.581] "Message": "FANBOARD1_FAN3_TACH_OL warning high threshold assert. Reading=14672.000000 Threshold=11970.000000.",
[2024-04-03 12:07:15.581] "Message": "FANBOARD1_FAN5_TACH_OL warning high threshold assert. Reading=13284.000000 Threshold=11970.000000.",
[2024-04-03 12:07:15.595] "Message": "FANBOARD1_FAN5_TACH_IL warning high threshold assert. Reading=15855.000000 Threshold=13140.000000.",
[2024-04-03 12:07:15.601] "Message": "FANBOARD1_FAN3_TACH_IL warning high threshold assert. Reading=15603.000000 Threshold=13140.000000.",

Signed-off-by: Allen.Wang <Allen_Wang@quantatw.com>
Change-Id: I803dc113624c3693fde8f12e5c0aadd339d6dd0b

show more ...


# 05c30e10 05-Mar-2024 Delphine CC Chiu <Delphine_CC_Chiu@wiwynn.com>

meta-facebook: yosemite4: Set GPIO status for slot reset button

Although GPIO v0/v1/v2/v3 have been set as input in kernel devicetree,
these pins' direction still perform to output in bmc runtime.

meta-facebook: yosemite4: Set GPIO status for slot reset button

Although GPIO v0/v1/v2/v3 have been set as input in kernel devicetree,
these pins' direction still perform to output in bmc runtime.

Before resolving the unexpected behavior with Aspeed,
This change adds a short-term solution for GPIO pins setting to input,
to ensure slot reset button being capable of pressing.

Tested:
Get gpioinfo in bmc runtime

Change-Id: Ibcc6e87bfa20c90471e1adbcd53018d8a29293ea
Signed-off-by: Delphine CC Chiu <Delphine_CC_Chiu@wiwynn.com>

show more ...


# 4f0996c9 11-Jan-2024 Delphine CC Chiu <Delphine_CC_Chiu@wiwynn.com>

meta-facebook: yosemite4: Revise i/o config for medusa board's schematic changes

Revise medusa board i/o initialization for EVT schematic changes

Tested: Verified with yosemite4 POC/EVT medusa boar

meta-facebook: yosemite4: Revise i/o config for medusa board's schematic changes

Revise medusa board i/o initialization for EVT schematic changes

Tested: Verified with yosemite4 POC/EVT medusa board

Change-Id: Iae1809de1b0ada79425a59f124387b974e22d168
Signed-off-by: Delphine CC Chiu <Delphine_CC_Chiu@wiwynn.com>

show more ...


# a29bca51 04-Dec-2023 Eric <Eric_LC_Chen@wiwynn.com>

meta-facebook: yosemite4: probe devices for EVT HW schematic change

Summary:
Probe devices behind mux to cpld for EVT HW schematic change

Tested:
Check i2c device probing on both POC/EVT unit

Chan

meta-facebook: yosemite4: probe devices for EVT HW schematic change

Summary:
Probe devices behind mux to cpld for EVT HW schematic change

Tested:
Check i2c device probing on both POC/EVT unit

Change-Id: I46235b977dbe0a103cd55b43205f49ba12f62713
Signed-off-by: Delphine CC Chiu <Delphine_CC_Chiu@wiwynn.com>

show more ...


Revision tags: 2.16.0-dev
# 177e987b 21-Sep-2023 Delphine CC Chiu <Delphine_CC_Chiu@wiwynn.com>

meta-facebook: yosemite4: Add initial GPIO setting

Summary:
To initial GPIO setting by following yosemite4 hardware setting

Tested:
Check GPIO using devmem

Change-Id: I706ecfc8a41dcc12e4bd0f293c5a

meta-facebook: yosemite4: Add initial GPIO setting

Summary:
To initial GPIO setting by following yosemite4 hardware setting

Tested:
Check GPIO using devmem

Change-Id: I706ecfc8a41dcc12e4bd0f293c5ae38f5943d377
Signed-off-by: Delphine CC Chiu <Delphine_CC_Chiu@wiwynn.com>

show more ...