1# PLDM daemon options 2option( 3 'tests', 4 type: 'feature', 5 value: 'enabled', 6 description: 'Build tests' 7) 8 9option( 10 'oe-sdk', 11 type: 'feature', 12 description: 'Enable OE SDK' 13) 14 15option( 16 'utilities', 17 type: 'feature', 18 value: 'enabled', 19 description: 'Enable debug utilities' 20) 21 22option( 23 'libpldmresponder', 24 type: 'feature', 25 value: 'enabled', 26 description: 'Enable libpldmresponder' 27) 28 29option( 30 'systemd', 31 type: 'feature', 32 value: 'enabled', 33 description: 'Include systemd support' 34) 35 36option( 37 'transport-implementation', 38 type: 'combo', 39 choices: ['mctp-demux', 'af-mctp'], 40 description: 'transport via af-mctp or mctp-demux' 41) 42 43# As per PLDM spec DSP0240 version 1.1.0, in Timing Specification for PLDM messages (Table 6), 44# the instance ID for a given response will expire and become reusable if a response has not been 45# received within a maximum of 6 seconds after a request is sent. By setting the dbus timeout 46# value to 5 seconds we ensure that PLDM does not wait for a response from a dbus call even after 47# the instance ID has expired. If the option is set to 5 seconds, any dbus call originated from 48# PLDM daemon will timeout after 5 seconds. 49option( 50 'dbus-timeout-value', 51 type: 'integer', 52 min: 3, 53 max: 10, 54 value: 5, 55 description: '''The amount of time pldm waits to get a response for a dbus 56 message before timing out''' 57) 58 59option( 60 'heartbeat-timeout-seconds', 61 type: 'integer', 62 value: 120, 63 description: '''The amount of time host waits for BMC to respond to pings 64 from host, as part of host-bmc surveillance''' 65) 66 67# Flight Recorder for PLDM Daemon 68option( 69 'flightrecorder-max-entries', 70 type:'integer', 71 min:0, 72 max:30, 73 value: 10, 74 description: '''The max number of pldm messages that can be stored in the 75 recorder, this feature will be disabled if it is set to 0''' 76) 77 78# PLDM Daemon Terminus options 79option( 80 'terminus-id', 81 type:'integer', 82 min:0, 83 max: 255, 84 value:1, 85 description: '''The terminus id value of the device that is running this 86 pldm stack''' 87) 88 89option( 90 'terminus-handle', 91 type:'integer', 92 min:0, 93 max:65535, 94 value:1, 95 description: '''The terminus handle value of the device that is running this 96 pldm stack''' 97) 98 99# Timing specification options for PLDM messages 100option( 101 'number-of-request-retries', 102 type: 'integer', 103 min: 2, 104 max: 30, 105 value: 2, 106 description: '''The number of times a requester is obligated to retry a 107 request''' 108) 109 110option( 111 'instance-id-expiration-interval', 112 type: 'integer', 113 min: 5, 114 max: 6, 115 value: 5, 116 description: 'Instance ID expiration interval in seconds' 117) 118 119# Default response-time-out set to 2 seconds to facilitate a minimum retry of 120# the request of 2. 121option( 122 'response-time-out', 123 type: 'integer', 124 min: 300, 125 max: 4800, 126 value: 2000, 127 description: '''The amount of time a requester has to wait for a response 128 message in milliseconds''' 129) 130 131# Firmware update configuration parameters 132option( 133 'maximum-transfer-size', 134 type: 'integer', 135 min: 16, 136 max: 4294967295, 137 value: 4096, 138 description: '''Maximum size in bytes of the variable payload allowed to be 139 requested by the FD, via RequestFirmwareData command''' 140) 141 142# PLDM Soft Power off options 143option( 144 'softoff', 145 type: 'feature', 146 value: 'enabled', 147 description: 'Build soft power off application' 148) 149 150option( 151 'softoff-timeout-seconds', 152 type: 'integer', 153 value: 7200, 154 description: 'softoff: Time to wait for host to gracefully shutdown' 155) 156 157# Vendor Specific Options 158 159## OEM IBM Options 160option( 161 'oem-ibm', 162 type: 'feature', 163 value: 'enabled', 164 description: 'Enable IBM OEM PLDM' 165) 166 167option( 168 'oem-ibm-dma-maxsize', 169 type: 'integer', 170 min:4096, 171 max: 16773120, 172 value: 8384512, 173 description: 'OEM-IBM: max DMA size' 174) 175