| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
Currently required for the debug-trigger application.
Change-Id: I585ccc5591b3f66db41bfd9799df05cec902403d
Signed-off-by: Andrew Jeffery <andrew@aj.id.au>
|
|
Replaces the obsolete MCTP LPC driver.
Change-Id: Ic5f7f6ec796bff8f0628d53e09a7437a74399ef4
Signed-off-by: Andrew Jeffery <andrew@aj.id.au>
|
|
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
|
|
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>
|
|
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>
|
|
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
|
|
(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>
|
|
Mihawk can use up to eight 250-soc.
Tested:
The user can see the temperature when using 250-soc.
(From meta-ibm rev: 74b7557b08ed2582861cd7da390d84371ec2ff86)
Change-Id: I17b0d969d0902f6470287c6164f542ad84412f7d
Signed-off-by: Ben Pai <Ben_Pai@wistron.com>
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
The metadata common to all IBM systems is confusingly split between
meta-ibm and meta-witherspoon. Move everything to meta-ibm.
The meta-ibm README is re-written to more accurately reflect the scope
of the layer.
Allow the configuration samples (bblayers.conf.sample,
local.conf.sample) to be sourced from either meta-ibm or
meta-witherspoon until such a time that any workflows and tooling have
had the opportunity to move to meta-ibm.
(From meta-ibm rev: 6e05ef2e90b214eaf4e43ee7027bbbb1d8d09442)
Change-Id: I3ec890d5300f9649c974ea6b9dca93a2e8a889ab
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
