blob: 589bf3d5a5a124cdcc758c03b3d842b4f9753cd2 [file] [log] [blame]
Patrick Williams596f49f2023-10-23 21:21:13 -05001# Force the mctp-demux to be used until machine is ready to use in-kernel MCTP
George Liu72f95342024-01-04 09:52:52 +08002PACKAGECONFIG:append = " transport-mctp-demux oem-ibm"
Deepak Kodihalli212dd9d2019-10-14 01:43:50 -05003
Sagar Srinivasd2d23602022-04-12 23:51:04 -05004EXTRA_OEMESON += " \
5 -Dsoftoff-timeout-seconds=2700 \
6 "
7
vkaverap@in.ibm.com88ac2ed2023-07-10 01:36:50 -05008#5 second timeout defined inside PLDM has seen issues during reset reload
9#so increasing that to 10 seconds here.IBMs custom firmware stack can tolerate
10#PLDM timeouts of up to 20 seconds, so using timeout value of 10 seconds is safe.
11EXTRA_OEMESON += " \
12 -Ddbus-timeout-value=10 \
13 "
14
Andrew Geissler3775b4f2021-09-08 14:31:24 +000015SYSTEMD_SERVICE:${PN} += "${@bb.utils.contains('PACKAGECONFIG', 'oem-ibm', \
16 'pldm-create-phyp-nvram.service \
17 pldm-create-phyp-nvram-cksum.service \
Andrew Geissler3775b4f2021-09-08 14:31:24 +000018 ', '', d)}"