OpenBMC Distribution (mirror) https://git.radix-linux.su/BMC/OpenBmc/openbmc.git/atom?h=redfish2phosphor-cpp 2022-01-31T20:35:54+00:00 2022-01-31T20:35:54+00:00 Eddie James eajames@linux.ibm.com 2022-01-28T22:07:18+00:00 urn:sha1:797c018f75fabf7df2bb9f87649c619ab215be67 The PL2303 is a serial-to-USB converter chip, needed to communicate with a UPS. These are commonly attached via USB1.1, meaning that a UHCI driver is required to communicate with them, so enable that too. Signed-off-by: Eddie James <eajames@linux.ibm.com> Change-Id: I3a7550a51d084af498e7a5aab5c6b6e75002a4e3 2021-10-06T17:34:06+00:00 Andrew Geissler geissonator@yahoo.com 2021-10-05T18:49:19+00:00 urn:sha1:17e10e6463249dda117e09d86749610931b52053 The documentation for CONFIG_PSTORE_CONSOLE indicates the following: "pstore will log all kernel messages, even if no oops or panic happened" This causes a console-ramoops-0 to appear in /var/lib/systemd/pstore/ on any BMC reboot. This in turn causes phosphor-debug-collector, which monitors for any files in this directory, to generate a BMC dump with the file. This is not what we want. What we really need are the dmesg-ramoops-* files which are generated when a kernel panic or oops occur. Remove the CONSOLE setting so we only get dumps when an actual BMC failure occurs. Tested: - Verified that console-ramoops-0 file no longer appears in /var/lib/systemd/pstore/ after a BMC reboot. - Verified we still get needed dmesg-ramoops-* files when a kernel panic occurs. Signed-off-by: Andrew Geissler <geissonator@yahoo.com> Change-Id: I6b48a8715946b193257bcc4892e07f87c13c95e6 2021-08-11T17:28:12+00:00 Adriana Kobylak anoo@us.ibm.com 2021-08-06T16:25:30+00:00 urn:sha1:b96c75046da8f72359d101c813f0694409bbe0d1 Change-Id: I9116ed7260e369136acb39eec15075db2d4dbeba Signed-off-by: Adriana Kobylak <anoo@us.ibm.com> 2021-07-20T15:17:44+00:00 Andrew Jeffery andrew@aj.id.au 2021-07-09T12:30:13+00:00 urn:sha1:f489c252ffbe88ae5621211e13649ad30d86fe42 Currently required for the debug-trigger application. Change-Id: I585ccc5591b3f66db41bfd9799df05cec902403d Signed-off-by: Andrew Jeffery <andrew@aj.id.au> 2021-07-20T15:17:44+00:00 Andrew Jeffery andrew@aj.id.au 2021-07-09T12:28:52+00:00 urn:sha1:21684ad6849a9a6b09afb42926a78476b773b3e2 Replaces the obsolete MCTP LPC driver. Change-Id: Ic5f7f6ec796bff8f0628d53e09a7437a74399ef4 Signed-off-by: Andrew Jeffery <andrew@aj.id.au> 2021-07-08T13:41:13+00:00 Bruce Mitchell bruce.mitchell@linux.vnet.ibm.com 2021-07-06T23:47:56+00:00 urn:sha1:8b316db58e63a489eb8d32876222d486f6676ae6 This sensor on the Op_Panel, one of them being a SI7020 type sensor which needed to be enabled. Signed-off-by: Bruce Mitchell <bruce.mitchell@linux.vnet.ibm.com> Change-Id: Ib6a86a6fae52414ad9c6901e5f6f8aa8c8a383c3 2021-06-17T13:17:10+00:00 Andrew Jeffery andrew@aj.id.au 2021-05-04T07:40:21+00:00 urn:sha1:05571557254cddd1c6a87bf3abd612e405ac3280 Currently /proc/sysrq-trigger is the only supported backend for debug-trigger. Once we have kdump support, we'll add a kexec backend and drop the magic sysrq. Change-Id: I07dfa50474d9f6333428b6fb38020c7b7fd0adec Signed-off-by: Andrew Jeffery <andrew@aj.id.au> 2021-04-08T16:38:31+00:00 Adriana Kobylak anoo@us.ibm.com 2021-03-25T16:35:45+00:00 urn:sha1:999c9e7a9698ccaca6b1834f608f9dd822d70d58 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-03-25T20:26:05+00:00 Matt Spinler spinler@us.ibm.com 2021-02-25T18:24:47+00:00 urn:sha1:138e8b74067f7a5d74c55d73118b35eaa4b6c896 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 2020-10-07T18:59:32+00:00 Andrew Jeffery andrew@aj.id.au 2020-10-02T03:25:54+00:00 urn:sha1:f4c2ebbb9cb8b1970d103d6ae5c32e18ed067e85 (From meta-ibm rev: 03ff1fa3f6ce475760535c08dfea9b751aa71f65) Change-Id: I17ddb7eef0853cb0a3ae23ab0f67043b931afc34 Signed-off-by: Andrew Jeffery <andrew@aj.id.au> Signed-off-by: Andrew Geissler <geissonator@yahoo.com>