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