meta-phosphor: unset VOLATILE_LOG_DIR

This variable, if set, creates a symlink of /var/log to
/var/volatile/log. In most cases if machines have configured
applications like obmc-console or journald

meta-phosphor: unset VOLATILE_LOG_DIR

This variable, if set, creates a symlink of /var/log to
/var/volatile/log. In most cases if machines have configured
applications like obmc-console or journald to write to /var/log
they want it to be persistent. The symlink causes them to be written
to the non-persistent tmpfs space for /var/volatile.

Set all machines to `VOLATILE_LOG_DIR = no` by default.

Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I0f973e6b8599b32451c83d5161be079e967de711

show more ...

meta-ampere: mtjade: update LED configuration file name

phosphor-led-manager is changed to use xyz.openbmc_project.Inventory.
Decorator.Compatible interface to select the configuration file.
This up

meta-ampere: mtjade: update LED configuration file name

phosphor-led-manager is changed to use xyz.openbmc_project.Inventory.
Decorator.Compatible interface to select the configuration file.
This updates the led-group-config.json file to
com.ampere.Hardware.Chassis.Model.MtMitchell.json follow the
phosphor-led-manager.

Tested: verify that led config file in the system
root@mtjade:~# ls /usr/share/phosphor-led-manager/
com.ampere.Hardware.Chassis.Model.MtJade.json
com.ibm.Hardware.Chassis.Model.Rainier1S4U.json
com.ibm.Hardware.Chassis.Model.Rainier4U.json
com.ibm.Hardware.Chassis.Model.Everest.json
com.ibm.Hardware.Chassis.Model.Rainier2U.json

Signed-off-by: Hieu Huynh <hieuh@os.amperecomputing.com>
Change-Id: I83647f465506d3fc3202d2b8f7145a1342f86dcf

show more ...

meta-ampere: mtjade: leds: change to json configuration

Change LED configuration format to json to adapt new default setting in
phosphor-led-manager application.

Tested:
1. Check if all LED Groups

meta-ampere: mtjade: leds: change to json configuration

Change LED configuration format to json to adapt new default setting in
phosphor-led-manager application.

Tested:
1. Check if all LED Groups are created, the same as using yaml file
root@mtmitchell-dcscm:~# busctl tree xyz.openbmc_project.LED.GroupManager
`- /xyz
`- /xyz/openbmc_project
`- /xyz/openbmc_project/led
`- /xyz/openbmc_project/led/groups
|- /xyz/openbmc_project/led/groups/bmc_booted
|- /xyz/openbmc_project/led/groups/power_on
|- /xyz/openbmc_project/led/groups/enclosure_identify
|- /xyz/openbmc_project/led/groups/enclosure_identify_blink
`- /xyz/openbmc_project/led/groups/systemFault
2. Check if no error message in journal log

Signed-off-by: Thang Q. Nguyen <thang@os.amperecomputing.com>
Change-Id: I7de6bfe333bad04f045c38bb9ff7aeb64eaed8bd

show more ...

meta-ampere: fix package in packagegroup

This fixes packages in packagegroup as follows:
+ Removes phosphor-post-code-manager, phosphor-host-postd
which is already in packagegroup-bmc-apps
+ Adds mi

meta-ampere: fix package in packagegroup

This fixes packages in packagegroup as follows:
+ Removes phosphor-post-code-manager, phosphor-host-postd
which is already in packagegroup-bmc-apps
+ Adds missing phosphor-ipmi-blobs, phosphor-ipmi-blobs-binarystore
into mtjade.conf

Tested: code compiles.

Signed-off-by: Hieu Huynh <hieuh@os.amperecomputing.com>
Change-Id: Ic3f9668e4714566a814cc928067289d650a59f41

show more ...

meta-ampere: move packagegroup to common

This moves packagegroup to common to be used for all platforms.

Tested:
- All packages are available on RootFs
- ipmi sensor, fru report
- Web login
- Power

meta-ampere: move packagegroup to common

This moves packagegroup to common to be used for all platforms.

Tested:
- All packages are available on RootFs
- ipmi sensor, fru report
- Web login
- Power control

Signed-off-by: Hieu Huynh <hieuh@os.amperecomputing.com>
Change-Id: I87f7ddbd94e9321e452353ed21cacd0f8a4d8f74

show more ...

linux-aspeed: Move to Linux v6.5

This moves the OpenBMC kernel to a v6.5 base for ASPEED.

The 6.5 kernel moved all 32-bit ARM device trees, so our BMC device
tress are now under an 'aspeed' subdire

linux-aspeed: Move to Linux v6.5

This moves the OpenBMC kernel to a v6.5 base for ASPEED.

The 6.5 kernel moved all 32-bit ARM device trees, so our BMC device
tress are now under an 'aspeed' subdirectory. This change means systems
must describe the KERNEL_DEVICETREE with the aspeed directory prefix.

There are 78 patches in the tree, with 40 of those patches not
yet queued for merging in v6.6.

The remaining out of tree patches include:

Andrew Jeffery (6):
dt-bindings: hwmon: pmbus: Add Maxim MAX31785 documentation
pmbus (max31785): Add support for devicetree configuration
pmbus (core): One-shot retries for failure to set page
pmbus (max31785): Wrap all I2C accessors in one-shot failure handlers
ARM: dts: aspeed: witherspoon: Update max31785 node
ipmi: kcs_bmc: Add a "raw" character device interface

Cédric Le Goater (1):
/dev/mem: add a devmem kernel parameter to activate the device

Eddie James (16):
ARM: dts: aspeed: bonnell: Add reserved memory for TPM event log
dt-bindings: soc: Add Aspeed XDMA Engine
soc: aspeed: Add XDMA Engine Driver
soc: aspeed: xdma: Add user interface
soc: aspeed: xdma: Add reset ioctl
soc: aspeed: xdma: Add trace events
i2c: core: Add mux root adapter operations
iio: si7020: Lock root adapter to wait for reset
eeprom: ee1004: Enable devices on multiple busses
dt-bindings: trivial-devices: Add Atmel AT30TSE004A serial eeprom
eeprom: ee1004: Add OF matching support
leds: pca955x: Refactor with helper functions and renaming
leds: pca955x: Use pointers to driver data rather than I2C client
leds: pca955x: Optimize probe led selection
leds: pca955x: Add HW blink support
leds: Ensure hardware blinking turns off when requested

Jae Hyun Yoo (1):
clk: ast2600: enable BCLK for PCI/PCIe bus always

Joel Stanley (14):
net: ftgmac100: Ensure tx descriptor updates are visible
ARM: aspeed: Add debugfs directory
ARM: soc: aspeed: Add secure boot controller support
dt-bindings: trivial-devices: Remove Infineon SLB9673 TPM
ARM: dts: nuvoton: npmc750-evb: Add default console
tpm: tis-i2c: Add more compatible strings
leds: pca955x: Revert "Remove the unused function pca95xx_num_led_regs()"
arm64: configs: Add Nuvoton NPCM defconfig
ARM: configs: aspeed: Add new FSI drivers
ARM: config: aspeed_g5: Enable SSIF BMC driver
ARM: config: aspeed: Remove FIRMWARE_MEMMAP
ARM: config: aspeed: Add Ampere SMPro drivers
ARM: config: Add openbmc defconfig
ARM: config: openbmc: Add HPE GPX and Nuvoton 7xx

Johannes Holland (1):
dt-bindings: tpm: Add schema for TIS I2C devices

Potin Lai (1):
mtd: spi-nor: winbond: Add support for w25q01jvq

Change-Id: Ib97af192391af6e71c96fe14e12cfc88c23d7a7d
Signed-off-by: Joel Stanley <joel@jms.id.au>

show more ...

meta-ampere: add fault monitor support

Support to detect GPIO, PSU, FAN, ... faults and turn ON/OFF fault LED.

Tested:
1. Unplug a PSU and check if Fault LED is turned ON.
2. Unplug a FAN and check

meta-ampere: add fault monitor support

Support to detect GPIO, PSU, FAN, ... faults and turn ON/OFF fault LED.

Tested:
1. Unplug a PSU and check if Fault LED is turned ON.
2. Unplug a FAN and check if Fault LED is turned ON.
3. Stimulate GPIO fault pattern and check if the BMC can detect

Signed-off-by: Thang Q. Nguyen <thang@os.amperecomputing.com>
Signed-off-by: Hieu Huynh <hieuh@os.amperecomputing.com>
Signed-off-by: Quang Nguyen <quangn@amperecomputing.com>
Change-Id: Idfcd32953cf811fbe9299a162f604cb8fd028962

show more ...

meta-ampere: mtjade: Support automatic fan control

This commit supports phosphor-fan application for mtjade platform.
phosphor-fan-control service controls fan speed following the mapping
tables wit

meta-ampere: mtjade: Support automatic fan control

This commit supports phosphor-fan application for mtjade platform.
phosphor-fan-control service controls fan speed following the mapping
tables with TS4_Temp, OCP_Temp, nvme_bp_max and nvme_m2_max sensor.
phosphor-fan-presence-tach and phosphor-fan-monitor services are fully
supported.

Signed-off-by: Chau Ly <chaul@amperecomputing.com>
Change-Id: I11a598f627d5e261689c2bd9d85ce65f4fc330ea

show more ...

meta-ampere: mtjade: Change from phosphor-nvme to nvmesensor

This commit removes phosphor-nvme implementation in mtjade
platform and configures to use dbus-sensors's nvmesensor.

Signed-off-by: Chau

meta-ampere: mtjade: Change from phosphor-nvme to nvmesensor

This commit removes phosphor-nvme implementation in mtjade
platform and configures to use dbus-sensors's nvmesensor.

Signed-off-by: Chau Ly <chaul@amperecomputing.com>
Change-Id: Ib9ce787e34265382a222697fb102fe63b4ba8a03

show more ...

meta-ampere: mtjade: enable IPMI SSIF

Enable IPMI SSIF support for Mt.Jade platform. This also supports to set
BMC_OK GPIO when SSIF service starts and unset when SSIF service stops.

Tested:
1. Che

meta-ampere: mtjade: enable IPMI SSIF

Enable IPMI SSIF support for Mt.Jade platform. This also supports to set
BMC_OK GPIO when SSIF service starts and unset when SSIF service stops.

Tested:
1. Check if ssifbridge.service service starts
root@mtjade:~# systemctl status ssifbridge.service | grep Active
Active: active (running) since Tue 2022-10-11 02:17:55 UTC; 1h 49min ago
2. From Host OS, check if IPMI SSIF works.

Signed-off-by: Thang Q. Nguyen <thang@os.amperecomputing.com>
Change-Id: I6b3a764f15c63b45acafdb590c7dfb223bfdd3a3

show more ...

meta-ampere: refactor drivers binder services

Use obmc-power-already-on target to trigger
ampere-power-on-driver-binder scripts instead of intergrating code to
ampere-host-check service.
Use obmc-ho

meta-ampere: refactor drivers binder services

Use obmc-power-already-on target to trigger
ampere-power-on-driver-binder scripts instead of intergrating code to
ampere-host-check service.
Use obmc-host-already-running target to trigger
ampere-host-on-driver-binder scripts.
Add ampere-power-on-driver-binder service.

Tested:
1. ampere-power-on-driver-binder scripst should be called when the
chassis-power-control pin is triggered and only when the drivers are
not bound.
2. ampere-host-on-driver-binder scripts will be called when the host
is already on, right after host0-ready.

Signed-off-by: Thu Nguyen <thu@os.amperecomputing.com>
Change-Id: I02f83d60a603dbc8d214534a13162f504c8c7deb

show more ...

meta-ampere: mtjade: enable ipmi-blobs

Enable phosphor-ipmi-blobs and phosphor-ipmi-blobs-binarystore so that
SMBIOS MDR data can be sent from Host.

Tested:
1. Run BmcBlobGetCount command
$ ipmitoo

meta-ampere: mtjade: enable ipmi-blobs

Enable phosphor-ipmi-blobs and phosphor-ipmi-blobs-binarystore so that
SMBIOS MDR data can be sent from Host.

Tested:
1. Run BmcBlobGetCount command
$ ipmitool raw 46 128 0xcf 0xc2 0x0 0
cf c2 00 a4 78 01 00 00 00


Signed-off-by: Thang Q. Nguyen <thang@os.amperecomputing.com>
Change-Id: Ib8fe4f92d6e27d0c620aeb301b1dc63901720c9b

show more ...

meta-ampere: refine code structure

Restructure Ampere recipes to better reuse existing resource for
multiple platforms later.

Tested:
1. Compile without error.
2. Run regression test for related fe

meta-ampere: refine code structure

Restructure Ampere recipes to better reuse existing resource for
multiple platforms later.

Tested:
1. Compile without error.
2. Run regression test for related features without error.

Signed-off-by: Thang Q. Nguyen <thang@os.amperecomputing.com>
Change-Id: I5d034d21273b99be651f20dc2eb5549c1092f079

show more ...

meta-jade: Clean up phosphor-isolation distro feature

As mtjade uses the newer u-boot tree based on v2019.04, the
phosphor-isolation distro feature does not do anything.

The backdoors closed by the

meta-jade: Clean up phosphor-isolation distro feature

As mtjade uses the newer u-boot tree based on v2019.04, the
phosphor-isolation distro feature does not do anything.

The backdoors closed by the distro feature are now closed by default, so
no opt-in is required.

Change-Id: I779caf74f138715e0a49febbdb09d4ef78e33e0c
Signed-off-by: Joel Stanley <joel@jms.id.au>

show more ...

meta-ampere: mtjade: switch to use u-boot 2019.04

u-boot 2016.07 does not work well with 64MB SPI-NOR layout, which has
the following issues:
- Incorrect environment variable configuration which mak

meta-ampere: mtjade: switch to use u-boot 2019.04

u-boot 2016.07 does not work well with 64MB SPI-NOR layout, which has
the following issues:
- Incorrect environment variable configuration which makes fail to boot
to kernel and has fw_setenv/fw_getenv commands not work.
- Even update the patch in meta-phosphor to fix above issue, still has
issue with setting environment variable in Linux which makes factory
reset failure each 2 times.
This commit changes to use u-boot 2019.04 to fix above issue.

Tested:
1. Do factory reset and check if the BMC can boot to kernel.
2. Trigger factory reset via Redfish multiple times (6 times) and verify
if the factory reset action can be executed at all times.

Signed-off-by: Thang Q. Nguyen <thang@os.amperecomputing.com>
Change-Id: Ibb269d96a2e2b509aeccbeeaa130aad57093d139

show more ...

u-boot: Specify u-boot package for AST2500 machines

This sets u-boot to the package containing the v2016.07-aspeed-openbmc
branch. This ensures there will be no change if the default changes in
the

u-boot: Specify u-boot package for AST2500 machines

This sets u-boot to the package containing the v2016.07-aspeed-openbmc
branch. This ensures there will be no change if the default changes in
the future.

Change-Id: Iea12e1691dbdda34a3f95d6d0862add0b15bcf37
Signed-off-by: Joel Stanley <joel@jms.id.au>

show more ...

Revert "meta-ampere: mtjade: support PSU present detection via GPIO"

By replacing phosphor-hwmon by dbus-sensor, PSU presence detection via
GPIO does not work anymore and it causes confiction with d

Revert "meta-ampere: mtjade: support PSU present detection via GPIO"

By replacing phosphor-hwmon by dbus-sensor, PSU presence detection via
GPIO does not work anymore and it causes confiction with dbus-sensor's
PSUSensor.
Revert the commit to avoid the confliction

Change-Id: Idfd54325c122921a3c5df062bce1b6909b643999
Signed-off-by: Thang Q. Nguyen <thang@os.amperecomputing.com>

show more ...

meta-ampere: mtjade: support NVME Temperature

Enable phosphor-nvme with configuration for nvme_max sensor for FAN
control support later.

Tested:
1. Check NVME Temp:
$ bu

meta-ampere: mtjade: support NVME Temperature

Enable phosphor-nvme with configuration for nvme_max sensor for FAN
control support later.

Tested:
1. Check NVME Temp:
$ busctl get-property xyz.openbmc_project.nvme.manager \
/xyz/openbmc_project/sensors/temperature/nvme20 \
xyz.openbmc_project.Sensor.Value Value
d 22
2. Check nvme_max has valid value
$ busctl introspect xyz.openbmc_project.VirtualSensor \
/xyz/openbmc_project/sensors/temperature/nvme_max

Signed-off-by: Thang Q. Nguyen <thang@os.amperecomputing.com>
Change-Id: Ied609ba5b5d39877c09ed04faff5063c7882a689

show more ...

meta-ampere: mtjade: Add more Host firmware support

Add support SCP firmware update with checking if the ampere_fru_upgrade
available to execute the update.
This commit also supports

meta-ampere: mtjade: Add more Host firmware support

Add support SCP firmware update with checking if the ampere_fru_upgrade
available to execute the update.
This commit also supports 2nd Host SPI-NOR update ability.

Tested:
1. Manually copy ampere_fru_upgrade to the /usr/sbin folder and run SCP
firmware update via Redfish.
2. Flash UEFI firmware update on the secondary Host SPI-NOR.

Signed-off-by: Thang Q. Nguyen <thang@os.amperecomputing.com>
Change-Id: Ic335ee2d21625239c3df1937ed5333708233845b

show more ...

Partially revert "treewide: remove obmc-system-mgmt feature"

The obmc-system-mgmt feature is currently used in the image to trigger
inclusion of a virtual-provider which provides a numbe

Partially revert "treewide: remove obmc-system-mgmt feature"

The obmc-system-mgmt feature is currently used in the image to trigger
inclusion of a virtual-provider which provides a number of packages many
systems need. Partially revert the removal of this feature so that
the outcome is:

1. The empty obmc-phosphor-sysd package is still removed.
2. By default the 'obmc-system-mgmt' feature is included, unless
specifically exempted.
3. All EVB platforms remove the 'obmc-system-mgmt' feature since
they have no system they are managing.

This partially reverts commit 060ad3ff7fcc30aff78a9e504efee9d8fa0d4526.

Tested:

* Built `bletchley` and confirmed `packagegroup-fb-apps-system` and
`entity-manager` are present.

```
entity-manager armv7ahf-vfpv4d16 0.1+git0+6bf41588ab-r0
packagegroup-fb-apps-system all 1.0-r1
```
* Built `witherspoon` and confirmed `packagegroup-op-apps-system` and
`pdbg` are present.

```
packagegroup-op-apps-system noarch 1.0
pdbg arm1176jzs 3.3
```

* Ran `bitbake -p` on `evb-ast2600` to confirm the undefined
`virtual-obmc-system-mgmt` is not being included in the image.

Change-Id: I8b7804d5101cc84a2c57473b3f85672bf7767c67
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>

show more ...

treewide: remove obmc-system-mgmt feature

Every machine layer treats 'system-management' as either part of a
package-group or removes the feature. The sample implementation in
meta-

treewide: remove obmc-system-mgmt feature

Every machine layer treats 'system-management' as either part of a
package-group or removes the feature. The sample implementation in
meta-phosphor is a do-nothing shell script (and up until recently was a
Python script). There appears to be no useful purpose to this feature
as a stand-alone concept, so remove it.

Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I20ca1fa8ff3cb01cac2d07d4ded84e0769e4514b

show more ...

treewide: clean up use of OBMC_MACHINE_FEATURES

Modify the machine meta-layer configs to remove the use of the
OBMC_MACHINE_FEATURES indirection and favor the Yocto MACHINE_FEATURES

treewide: clean up use of OBMC_MACHINE_FEATURES

Modify the machine meta-layer configs to remove the use of the
OBMC_MACHINE_FEATURES indirection and favor the Yocto MACHINE_FEATURES
variable instead.

Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: Ifafb79e4e4c010e9476b9547cd4982f5b645060e

show more ...

meta-ampere: mtjade: replace u-boot patches by feature

Enable phosphor-aspeed-spi-master-mode.inc and remove the u-boot
patch that used for this feature.
Also remove GPIO setting pat

meta-ampere: mtjade: replace u-boot patches by feature

Enable phosphor-aspeed-spi-master-mode.inc and remove the u-boot
patch that used for this feature.
Also remove GPIO setting patches which the setting already implemented
in the platform init package.

Tested: on Mt.Jade platform with OCP plugged
1. Bind/unbind Host SPI-NOR and ensure no problem
2. Turn off Host, reboot BMC and check if Host SPI-NOR is probe
successfully.

Signed-off-by: Thang Q. Nguyen <thang@os.amperecomputing.com>
Change-Id: Ie85166edca93b882868e1373696fbf664bee2ee4

show more ...

meta-ampere: enable ampere-ipmi-oem repo

Adds the ampere-ipmi-oem.bb file to support ampere-ipmi-oem features.

Signed-off-by: Hieu Huynh <hieuh@os.amperecomputing.com>
Change-Id

meta-ampere: enable ampere-ipmi-oem repo

Adds the ampere-ipmi-oem.bb file to support ampere-ipmi-oem features.

Signed-off-by: Hieu Huynh <hieuh@os.amperecomputing.com>
Change-Id: I869a3e73573dd43103b52640ef3ac2d1912280dc

show more ...

meta-ampere: mtjade: initialize GPIOs

Several GPIOs should be configured properly when booting BMC. Currently,
these GPIOs are configured in u-boot. However, some must be configured

meta-ampere: mtjade: initialize GPIOs

Several GPIOs should be configured properly when booting BMC. Currently,
these GPIOs are configured in u-boot. However, some must be configured
in Linux. For example, the BMC_READY GPIO should be set only after BMC
is ready to work.
This commit introduce platform-init service which starts after BMC boots
to configure GPIOs pins required by hardware design.

Tested:
1. Do A/C power, check GPIO227 is set to 0.
2. Reboot BMC, check GPIO227 is set to 0.
3. Run gpioinfo and check GPIO directions

Signed-off-by: Thang Q. Nguyen <thang@os.amperecomputing.com>
Change-Id: Ie0cfe171659ad740c6a25297f2fcce259870d43d

show more ...