summaryrefslogtreecommitdiff
path: root/meta-ibm
AgeCommit message (Collapse)AuthorFilesLines
2021-04-12ibm: power: Replace rainier with p10bmcAdriana Kobylak4-5/+5
The IBM rainier machine name is being replaced with the generic p10bmc. Change-Id: I8dece8c720fd520de7a6857a7311b62a65c054ba Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
2021-04-12ibm: Remove the openbmc-witherspoon distroAdriana Kobylak5-11/+13
The meta-ibm layer supported two different DISTROs depending on the machine being built. This caused complexity since the user needed to remember to specify the DISTRO name, in addition to the CI build scripts needed to check for the machine name being built to override the default DISTRO. For simplification, remove the openbmc-witherspoon DISTRO, which is the openpower DISTRO plus additional features, and move these features to the machine configuration files. Make the openpower DISTRO the default. Tested: Built witherspoon and p10bmc using "source setup <machine> build" followed by "bitbake obmc-phosphor-image" without specifying the DISTRO. Verified witherspoon built a ubi image and p10bmc built a emmc image. Change-Id: If33441ab4ad2dc0fbedde09f0db91d691d2da4f7 Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
2021-04-12ibm: Add back fru-fault-monitor to Rainier and Everest systemsVishwanatha Subbanna1-1/+0
Commit f7b1f26 removed fru-fault-monitor from Rainier since the idea then was to have PEL daemon set the Asserted property of LED Group Object that is mapping to the Inventory D-Bus object. However, that was not accepted by the community and we now have a new way of monitoring faults. With the new way, when monitor-operational-status feature is enabled, fru-fault-monitor will watch Functional property of xyz.openbmc_project.State.Decorator.OperationalStatus interface and sets the Asserted property of appropriate LED Group D-Bus objects that is mapped via "fault_led_group" association with the Inventory D-Bus object. When monitor-operational-status feature is enabled, fru-fault-monitor will not monitor the OBMC events and would only watch OperationalStatus. This is done because these 2 features will result in conflicting end result on the LEDs. Change-Id: I739b5fc261b0c79d50a8dc34ab19a3e108e84edc Signed-off-by: Vishwanatha Subbanna <vishwa@linux.vnet.ibm.com>
2021-04-12fru-fault-monitor: Enable OperationalStatus monitor featureVishwanatha Subbanna1-2/+3
Currently, the phosphor-fru-fault-monitor updates the Asserted property of the Led Group D-Bus object by monitoring the `/xyz/openbmc_project/logging` object path. The intent behind this commit is to add another way to monitor the `xyz.openbmc_project.State.Decorator.OperationalStatus` interface of the Inventory D-Bus object, and check whether the Inventory D-Bus object is associated with the LED group D-Bus object, and then update the Asserted property of the LedManager. Since both these methods handle the faults differently, Only ONE of these 2 methods can be enabled and NOT both. The first way is supported by default. To turn OFF the default way AND turn ON this second way, Enable monitor-operational-status. Change-Id: I03701e599b6a120bc1f83da6f473b12f38660d64 Signed-off-by: Vishwanatha Subbanna <vishwa@linux.vnet.ibm.com>
2021-04-08ibm: Add power button GPIO definitionMatt Spinler1-0/+5
This allows a power button press to power on the system. Rainier and Everest use the same GPIO. Tested: Button was pressed and the system booted. Signed-off-by: Matt Spinler <spinler@us.ibm.com> Change-Id: Ib8f373dda2adb5575f2a0001d986962e5430fba5
2021-04-08ibm: led-manager: Replace rainier with p10bmcAdriana Kobylak1-9/+9
The IBM rainier machine name is being replaced with the generic p10bmc. Tested: Verified the rainier build included the expected service files and LED override file, example: - rainier-openbmc-linux-gnueabi/obmc-phosphor-image/1.0-r0/rootfs/usr/share/phosphor-led-manager/lamp-test-led-overrides.json Change-Id: I8f9ecbc6ebe1d320a649b24bf71c5023cfc035c8 Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
2021-04-08ibm: Create p10bmc build targetAdriana Kobylak4-37/+39
Replace rainier with p10bmc as build target. Keep the rainier.conf as a symlink to p10bmc.conf to allow the transition. Remove the rainier.conf and the machine override from p10bmc.conf in a later commit to complete the replacement. Tested: Built rainier and p10bmc and checked for some files/service units to exist on both. Change-Id: Ic8c8c6ffbc3507fbd9c692da259e37ae695359a6 Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
2021-04-08ibm: kernel: Replace rainier with p10bmcAdriana Kobylak3-2/+2
The IBM rainier system is being replaced with the generic p10bmc name. Since the rainier.conf file will be renamed p10bmc.conf, add the device tree files for all p10 systems that will be supported with the p10bmc name (rainier, everest). Change-Id: I10983b913d8a2ae98ed4d327131b864f2df96a0c Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
2021-04-08ibm: inventory-manager: Replace rainier with p10bmcAdriana Kobylak4-3/+3
The IBM rainier machine name is being replaced with the generic p10bmc. Tested: Built rainier and verified files were installed: rainier-openbmc-linux-gnueabi/obmc-phosphor-image/1.0-r0/rootfs/usr/share/phosphor-inventory-manager/ibm,everest_associations.json rainier-openbmc-linux-gnueabi/obmc-phosphor-image/1.0-r0/rootfs/usr/share/phosphor-inventory-manager/ibm,rainier-4u_associations.json rainier-openbmc-linux-gnueabi/obmc-phosphor-image/1.0-r0/rootfs/usr/share/phosphor-inventory-manager/ibm,rainier-2u_associations.json Change-Id: I422374d25966e731147eebd1772d5cfc4f62f9d9 Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
2021-04-08ibm: fans: Replace rainier with p10bmcAdriana Kobylak22-31/+31
The IBM rainier machine name is being replaced with the generic p10bmc. Tested: Built rainier and verified the fan files were installed, ex: obmc-phosphor-image/1.0-r0/rootfs/usr/share/phosphor-fan-presence/control/ibm,rainier-4u/zones.json obmc-phosphor-image/1.0-r0/rootfs/usr/share/phosphor-fan-presence/control/ibm,rainier-2u/zones.json obmc-phosphor-image/1.0-r0/rootfs/usr/share/phosphor-fan-presence/control/ibm,everest/zones.json Change-Id: I10edb9e30716cffa3f510fe94822eadb08326912 Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
2021-04-06hardknott: yocto releaseAndrew Geissler3-3/+3
Latest upstream yocto has moved on to the 3.3 hardknott release Signed-off-by: Andrew Geissler <geissonator@yahoo.com> Change-Id: Ieae36798d66d21c2c642931f06407d3bb2acf163
2021-04-01ibm: obmc-phosphor-image: Replace rainier with p10bmcAdriana Kobylak1-1/+1
The IBM rainier machine name is being replaced with the generic p10bmc. Change-Id: I0a265a7eb9d763a8385a7139dae47bf2f475c672 Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
2021-04-01ibm: certificate-manager: Replace rainier with p10bmcAdriana Kobylak1-1/+1
The IBM rainier machine name is being replaced with the generic p10bmc. Change-Id: I0ab8ca402117e6eae8508d3f27cac7ad8c8b8aca Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
2021-04-01ibm: systemd: Replace rainier with p10bmcAdriana Kobylak1-7/+7
The IBM rainier machine name is being replaced with the generic p10bmc. Tested: Built a rainier image and verified the journal config files were present under: rainier-openbmc-linux-gnueabi/obmc-phosphor-image/1.0-r0/rootfs/lib/systemd/ Change-Id: Ia5c1de23fdbf7b8aeed70bd450cb72254542eb41 Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
2021-04-01ibm: mboxd: Replace rainier with p10bmcAdriana Kobylak1-1/+1
The IBM rainier machine name is being replaced with the generic p10bmc. Tested: Built rainier and verified that the mboxd service file had 64M: $ cat tmp/work/rainier-openbmc-linux-gnueabi/obmc-phosphor-image/1.0-r0/rootfs/lib/systemd/system/mboxd.service .. ExecStart=/usr/bin/env mboxd --flash 64M --window-size 1M Change-Id: I7c5bf66ac38ab0b97efa1eba7ceccba86565ed85 Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
2021-04-01ibm: network: Replace rainier with p10bmcAdriana Kobylak3-2/+2
The IBM rainier machine name is being replaced with the generic p10bmc. Change-Id: Ic76f6202f9ae43440e5e6a793ca835a45d6ab088 Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
2021-04-01ibm: debug-collector: Replace rainier with p10bmcAdriana Kobylak1-3/+3
The IBM rainier machine name is being replaced with the generic p10bmc. Change-Id: I5e0b884b405f56da7aa746b059d2490a1de2caab Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
2021-04-01ibm: openssl: Replace rainier with p10bmcAdriana Kobylak1-2/+2
The IBM rainier machine name is being replaced with the generic p10bmc. Change-Id: I5b7b173bd0255fcbe1956042cc365bf1fb6c7520 Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
2021-04-01ibm: sensors: Replace rainier with p10bmcAdriana Kobylak6-4/+4
The IBM rainier machine name is being replaced with the generic p10bmc. Change-Id: I43d08c3be45d8cc8b03914b9bc257df2668e9fe0 Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
2021-04-01ibm: packagegroups: Replace rainier with p10bmcAdriana Kobylak1-8/+8
The IBM rainier machine name is being replaced with the generic p10bmc. Change-Id: If32498a59ce621b1e456fdf0ec965c92d646ab86 Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
2021-04-01ibm: dbus-interfaces: Replace rainier with p10bmcAdriana Kobylak1-1/+1
The IBM rainier machine name is being replaced with the generic p10bmc. Change-Id: I7bfbbf2310be78a2ae601047710204f5fb9f0da0 Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
2021-04-01ibm: obmc-console: Replace rainier with p10bmcAdriana Kobylak4-8/+8
The IBM rainier machine name is being replaced with the generic p10bmc. Tested: Built rainier and verified the console files were installed: rainier-openbmc-linux-gnueabi/obmc-phosphor-image/1.0-r0/rootfs/etc/obmc-console/ Change-Id: Ida1010ae6c6c0e1eecf2b62521c06bfe055b0d88 Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
2021-04-01ibm: settings: Replace rainier with p10bmcAdriana Kobylak2-1/+1
The IBM rainier machine name is being replaced with the generic p10bmc. Change-Id: I3947988f73e601ca281b6222a6116bc7f50c8c32 Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
2021-04-01ibm: skeleton: Replace rainier with p10bmcAdriana Kobylak1-0/+0
The IBM rainier machine name is being replaced with the generic p10bmc. Change-Id: Id9cbde5f3ccc505635c37c8ffd92efef191e9320 Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
2021-04-01ibm: logging: Replace rainier with p10bmcAdriana Kobylak1-1/+1
The IBM rainier machine name is being replaced with the generic p10bmc. Change-Id: I9fa2bb6f199144816bd9d90405afe4fba36fc575 Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
2021-04-01ibm: software-manager: Replace rainier with p10bmcAdriana Kobylak1-4/+4
The IBM rainier machine name is being replaced with the generic p10bmc. Change-Id: Iba75dcfe5eee66bcb0afb5a01feddbf26b2c7988 Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
2021-04-01ibm: host-postd: Replace rainier with p10bmcAdriana Kobylak1-1/+1
The IBM rainier machine name is being replaced with the generic p10bmc. Change-Id: I430e6ed6bf006a114e185d4adb507d1c5c6e2cd4 Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
2021-04-01ibm: gpio-monitor: Replace rainier with p10bmcAdriana Kobylak5-2/+2
The IBM rainier machine name is being replaced with the generic p10bmc. Tested: Built rainier and verified the files were installed as expected: rainier-openbmc-linux-gnueabi/obmc-phosphor-image/1.0-r0/rootfs/etc/default/obmc/gpio/phosphor-power-supply-0.conf Change-Id: I6539c71cfc37fa67027204b17c68a0c7f8fec5a6 Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
2021-04-01ibm: rainier: Add p10bmc as MACHINEOVERRIDESAdriana Kobylak1-0/+1
The IBMC POWER10 systems will have a common BMC image, therefore there will be a transition to move from the 'rainier' system name to the generic 'p10bmc' name. This will be done in two stages. The first one is to create a p10bmc MACHINEOVERRIDES and replace the rainier conditionals with p10bmc. Once that's done, the rainier.conf will be replaced with p10bmc.conf. Change-Id: Ic499d36dd7f74a8b7f4a44723f76d1e344e15a32 Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
2021-03-30leds: rainier: Create virtual physical LEDsVishwanatha Subbanna3-1/+45
These virtual physical LEDs are a mirror of real enclosure fault and enclosure Identify physical LEDs. However, these virtual LEDs are needed to be able to communicate the effective state of the enclosure fault and enclosure identify LEDs during lamp test. During lamp test, real physical enclosure fault and enclosure id LEDs should not be updated and they must be updated only after the lamp test finishes. However, Hypervisors would need to know the effective state of enclosure level fault and identify LEDs and that problem is resolved by these virtual LEDs. Once the lamp test finishes, these virtual physical LEDs would again be in sync with real enclosure fault and Identify LEDs. Tests: root@bmc:/lib/systemd/system/multi-user.target.wants# busctl tree xyz.openbmc_project.LED.Controller.virtual_enc_fault └─/xyz └─/xyz/openbmc_project └─/xyz/openbmc_project/led └─/xyz/openbmc_project/led/physical └─/xyz/openbmc_project/led/physical/virtual_enc_fault root@bmc:/lib/systemd/system/multi-user.target.wants# busctl tree xyz.openbmc_project.LED.Controller.virtual_enc_id └─/xyz └─/xyz/openbmc_project └─/xyz/openbmc_project/led └─/xyz/openbmc_project/led/physical └─/xyz/openbmc_project/led/physical/virtual_enc_id root@bmc:/lib/systemd/system/multi-user.target.wants# busctl get-property xyz.openbmc_project.LED.Controller.virtual_enc_fault /xyz/openbmc_project/led/physical/virtual_enc_fault xyz.openbmc_project.Led.Physical State s "xyz.openbmc_project.Led.Physical.Action.Off" root@bmc:/lib/systemd/system/multi-user.target.wants# busctl set-property xyz.openbmc_project.LED.GroupManager /xyz/openbmc_project/led/groups/ddimm0_identify xyz.openbmc_project.Led.Group Asserted b true root@bmc:/lib/systemd/system/multi-user.target.wants# busctl get-property xyz.openbmc_project.LED.Controller.virtual_enc_id /xyz/openbmc_project/led/physical/virtual_enc_id xyz.openbmc_project.Led.Physical State s "xyz.openbmc_project.Led.Physical.Action.On" root@bmc:/lib/systemd/system/multi-user.target.wants# busctlset-property xyz.openbmc_project.LED.GroupManager /xyz/op_ebmc_project/led/groups/ddimm0_identify xyz.openbmc_project.Led.Group Asserted b false root@bmc:/lib/systemd/system/multi-user.target.wants# busctl get-property xyz.openbmc_project.LED.Controller.virtual_enc_id /xyz/openbmc_project/led/physical/virtual_enc_id xyz.openbmc_project.Led.Physical State s "xyz.openbmc_project.Led.Physical.Action.Off" Change-Id: Ic0ee5b0f376911650d5489d8bb84a4e83247190f Signed-off-by: Vishwanatha Subbanna <vishwa@linux.vnet.ibm.com>
2021-03-26ledmanager: Remove phosphor-led-manager-ledmanager packageVishwanatha Subbanna1-4/+4
phosphor-led-manager has 3 packages - phosphor-led-manager : Default - phosphor-led-manager-ledmanager : Packages phosphor-ledmanager - phosphor-ledmanager-faultmonitor : Packages phosphor-fru-fault-monitor Because of this, it was not possible to install files via Makefile and that always needed a corresponding update to FILES_{PN}-ledmanager. Removing phosphor-led-manager-ledmanager will eliminate this problem. Change-Id: I00ca4c34346a47f887872464b9050a46d8f5e8e9 Signed-off-by: Vishwanatha Subbanna <vishwa@linux.vnet.ibm.com>
2021-03-25Inventory: rainier: Add LED group associations to Inventory objectsVishwanatha Subbanna2-5/+5408
This commit adds below forward and reverse associations "rType": "fault_inventory_object", "fType": "fault_led_group" "rType": "identify_inventory_object", "fType": "identify_led_group" Change-Id: Icaad89e6e690c3c0a635362e8c604874bc3f37fe Signed-off-by: Vishwanatha Subbanna <vishwa@linux.vnet.ibm.com>
2021-03-25ibm: Add TMP401 driver to RainierMatt Spinler1-0/+1
This driver supports the TMP435 temperature sensor, which is used on 2 IBM manufactured PCIe cards, an NVME JBOF riser, and a PCIE gen 4 CXP cable card. The former only plugs into Rainier, and the latter into Rainier and Everest. The TMP435 devices on these cards are powered by slot power, controlled by the hypervisor, and so will not be accessible until the hypervisor has started and has turned on slot power. Note that the sensor instances for these cards will not be in the device tree because they are monitored by the hwmontempsensors application which gets its configuration information from the entity-manager application. Entity-manager uses the 'new_device' API to instantiate drivers, which does not need device tree entries. In fact, if these are in the device tree, then the new_device write will fail even though the device driver wasn't truly bound to that instance. As mentioned above, because they are on slot power they cannot be probed as usual on kernel startup. Signed-off-by: Matt Spinler <spinler@us.ibm.com> Change-Id: I8aab28266f4e4b492c8d1c0c256714439ef1b5cd
2021-03-251s4u: support presence config.json for new systemAndrew Geissler2-0/+90
The 1s4u is just like the 2s4u except it has two less fans. Tested: - Booted up system with entity-manager loading rainier-1s4u config and verified fan applications found and loaded new 1s4u files and system was able to chassis power on. Signed-off-by: Andrew Geissler <geissonator@yahoo.com> Change-Id: I575a63edb242c1b94e1a6f1eafd86a96e4518e37
2021-03-251s4u: support zones.json for new systemAndrew Geissler2-0/+13
The 1s4u is just like the 2s4u except it has two less fans. Signed-off-by: Andrew Geissler <geissonator@yahoo.com> Change-Id: I56ed73ee573df250072bd014a0e4c8a4072e974e
2021-03-251s4u: support fans.json for new systemAndrew Geissler2-0/+30
The 1s4u is just like the 2s4u except it has two less fans. Signed-off-by: Andrew Geissler <geissonator@yahoo.com> Change-Id: I35333e49c883fb9ac8c84223545fe3b903a66d7d
2021-03-251s4u: fan-monitor support for new systemAndrew Geissler2-0/+94
The 1s4u is just like the 2s4u except it has two less fans. Thermal profiling may change some of the variable but for now just use the same as the 2s4u. Signed-off-by: Andrew Geissler <geissonator@yahoo.com> Change-Id: Iab3fd9d1699de779c242bb42456d976697b4da14
2021-03-24kexec: Added to Witherspoon-Tacoma & Rainier imagesBruce Mitchell1-2/+2
For implementing kdump Witherspoon-Tacoma and Rainier kexec is needed. This was done by pulling kexec-tools package into the build. Tested: I successfully build each Witherspoon-Tacoma and Rainier booted each in QEMU and manually verified kexec with no parameters showed the version and help. Presently the kernel's SMP is missing HOTPLUG so further testing of kexec utility is not possible. Signed-off-by: Bruce Mitchell <Bruce.Mitchell@ibm.com> Change-Id: I253dd3e0c46987070b5c252dcd5ab6008b3b09d3
2021-03-24leds: rainier: lamptest: Enable lamp test feature for rainier systemVishwanatha Subbanna1-1/+2
This commit enables phosphor-ledmanager to do lamp test Change-Id: I4933ec034911198f99ae1289f681f15057310c33 Signed-off-by: Vishwanatha Subbanna <vishwa@linux.vnet.ibm.com>
2021-03-24leds: rainier: Enable PACKAGECONFIG to use jsonVishwanatha Subbanna1-0/+3
This enables phosphor-ledmanager to use JSON configuration file Change-Id: I3cbd0bf6b60e81f9f0a479ad51dab438c708c6c1 Signed-off-by: Vishwanatha Subbanna <vishwa@linux.vnet.ibm.com>
2021-03-22openbmc: add meta-security layerAnton D. Kachalov3-0/+6
This layer provides libseccomp. Signed-off-by: Anton D. Kachalov <gmouse@google.com> Change-Id: I84513d56f2ed75fab49043196b98ef8b858e394f
2021-03-22Override the snoop device name to empty for IBM systemsManojkiran Eda1-0/+2
- We have already made the change to make the snooping port optional, which means that snoopd daemon can still run and host the interfaces & Postcode Raw Value property even on the systems with no snooping port. - The intent behind this commit is to over ride the snoop-device name to empty from the meta-ibm layer so that the snoopd daemon will run without the support for snooping port on ibm machines. Tested: - Build images for witherspoon-tacoma & rainier, and made sure the snoopd service runs without any issues. Signed-off-by: Manojkiran Eda <manojkiran.eda@gmail.com> Change-Id: I622a903f9084a9b94561c1202f8c637d30062112
2021-03-09Correction in debug-collector recipePriyangaRamasamy1-1/+1
For installing gendumpheader plugin, the recipe was including all files from tools/dreport.d/ibm.d. Corrected it to take only gendumpheader plugin so that it wont conflict with installation of other plugins from same directory. Signed-off-by: PriyangaRamasamy <priyanga24@in.ibm.com> Change-Id: I5a1358f07aba6997cb9ae84dba59b3420c7ce968
2021-03-09Rainier: Add a presence to bind delay of 1500msBrandon Wyman4-0/+4
The firmware code in these power supplies takes about 1500 milliseconds to boot after they are inserted, and the presence line goes active. Until the firmware has completely booted, the power supplies will not respond to the I2C traffic initiated by the BMC device driver code as it attempts to probe the hardware. Adding in a DRIVER_BIND_DELAY_MS environment variable, set to 1500 (milliseconds), to delay the device driver binding in order to hold off the probe until the power supply firmware should be ready, in order to avoid ENXIO errors. Change-Id: I101f8e3b7ff1c2c9e76df758c4551c7793006266 Signed-off-by: Brandon Wyman <bjwyman@gmail.com>
2021-03-09Package phosphor-host-postd for tacoma & rainierManojkiran Eda1-2/+2
- The intent behind this commit is to pull the snooping daemon into tacoma & rainier. - This daemon is used for hosting the necessary dbus interface & Raw Value property for the pldm to write the progress codes into. Signed-off-by: Manojkiran Eda <manojkiran.eda@gmail.com> Change-Id: I4730046a40345d74d53b19a5058e8e45d2d40e8f
2021-03-03rainier: Add inventory associations JSON filesMatt Spinler4-2/+425
The phosphor-inventory-manager application supports creating associations based on JSON files, where the JSON files have conditions built into them that say which inventory-manager property values are required for the associations files to be valid. Add minimal associations files for the Rainier 2U, Rainier 4U, and Everest systems that just contain the fan inventory associations for now. The condition is the 'IM' property on the com.ipzvpd.VSBP interface on the system/chassis/motherboard path. Change-Id: Ib6807d8982a2efeb94692b917804c53965d6c98a Signed-off-by: Matt Spinler <spinler@us.ibm.com>
2021-03-02wspoon: Add fan monitor start delayMatt Spinler1-0/+4
Now that phosphor-fan-monitor starts at multi-user instead of the fans-ready target, it needs a JSON config option to let it know when to start monitoring after the fans have ramped up. Signed-off-by: Matt Spinler <spinler@us.ibm.com> Change-Id: If8eef303ee585dd30b3fbe9764a624eeab3b1a8a
2021-03-02native class is not inherited lastJoseph Reynolds4-4/+4
Moved "inherit native" statements to the last position to remove QA Issues. The message is: WARNING: QA Issue: {RECIPENAME}: native/nativesdk class is not inherited last, this can result in unexpected behaviour. Classes inherited after native/nativesdk: {CLASSFILES} [native-last] Tested: The witherspoon image builds without the warnings. Signed-off-by: Joseph Reynolds <joseph-reynolds@charter.net> Change-Id: Ic3c71234abfcac8b26478bc32808e3bec8bba810
2021-03-01Remove phsophor-gpio-keys as a standalone featureJoel Stanley1-1/+0
The feature was implemented as an append to the kernel (BSP) layers in meta-phsophor. This created a three way dance between machine layers, BSP and meta-phosphor, when it should have been the kernel layer providing this feature and machines could then opt in. Fixing this means we could remove the KERNEL_DANGLING_FEATURES_WARN_ONLY workaround. As the feature is simply turning on a pair of kernel options without any other impact, we can implement it by adding the options to our defconfigs. In fact, aspeed and hpe kernel configurations enable the two kernel options: $ git grep CONFIG_KEYBOARD_GPIO=y meta-aspeed/recipes-kernel/linux/linux-aspeed/aspeed-g4/defconfig:CONFIG_KEYBOARD_GPIO=y meta-aspeed/recipes-kernel/linux/linux-aspeed/aspeed-g5/defconfig:CONFIG_KEYBOARD_GPIO=y meta-aspeed/recipes-kernel/linux/linux-aspeed/aspeed-g6/defconfig:CONFIG_KEYBOARD_GPIO=y meta-hpe/meta-gxp/recipes-kernel/linux/linux-obmc/defconfig:CONFIG_KEYBOARD_GPIO=y $ git grep CONFIG_INPUT_EVDEV meta-aspeed/recipes-kernel/linux/linux-aspeed/aspeed-g4/defconfig:CONFIG_INPUT_EVDEV=y meta-aspeed/recipes-kernel/linux/linux-aspeed/aspeed-g5/defconfig:CONFIG_INPUT_EVDEV=y meta-aspeed/recipes-kernel/linux/linux-aspeed/aspeed-g6/defconfig:CONFIG_INPUT_EVDEV=y meta-hpe/meta-gxp/recipes-kernel/linux/linux-obmc/defconfig:CONFIG_INPUT_EVDEV=y Other machines that wish to enable this feature should ensure it is added to their BSP's defconfig, or add it to their machine specific defconfig. Change-Id: I0726836319022f96c1d13d4a0cbd73708047302c Signed-off-by: Joel Stanley <joel@jms.id.au>
2021-02-26Package post-code-manager for rainier & tacomaManojkiran Eda1-2/+2
- This commit would package the post-code-manager deamon support for tacoma & rainier machines. Signed-off-by: Manojkiran Eda <manojkiran.eda@gmail.com> Change-Id: Ieea0b1516419d8cde2b93126fb278ffa16f0c15d
generated by cgit v1.2.3 (git 2.39.0) at 2024-07-03 02:17:20 +0300