| commit | 08319c8f9c705080bd74aa1dfc63f8d9d8dea1c5 | [log] [tgz] |
|---|---|---|
| author | Jayanth Othayoth <ojayanth@gmail.com> | Thu Dec 25 06:29:29 2025 -0600 |
| committer | Jayanth Othayoth <ojayanth@gmail.com> | Mon Dec 29 08:08:56 2025 -0600 |
| tree | 554e78131804a675c86035bf59a8a2dacbebb432 | |
| parent | efe7bd811a144b9aa7599d21d0150d949bb6a056 [diff] |
clang-tidy: Initial commit Added initial .clang-tidy configuration file with recommended C++ checks aligned with the OpenBMC-approved checklist. This setup enforces modern C++ best practices and helps catch common issues early in development. Change-Id: I529af91945aeadc609b132e832813f21d7dcc263 Signed-off-by: Jayanth Othayoth <ojayanth@gmail.com>
Sample config options available to configure :
Single channel with one me and ipmb :
{ "channels": [ { "type": "me", "slave-path": "/dev/ipmb-4", "bmc-addr": 32, "remote-addr": 44 }, { "type": "ipmb", "slave-path": "/dev/ipmb-9", "bmc-addr": 32, "remote-addr": 96 } ] }
Multiple sub channels with me and ipmb :
{ "channels": [ { "type": "me", "slave-path": "/dev/ipmb-1", "bmc-addr": 32, "remote-addr": 64, "devIndex": 0 }, { "type": "ipmb", "slave-path": "/dev/ipmb-3", "bmc-addr": 32, "remote-addr": 64, "devIndex": 0 }, { "type": "me", "slave-path": "/dev/ipmb-5", "bmc-addr": 32, "remote-addr": 64, "devIndex": 1 }, { "type": "ipmb", "slave-path": "/dev/ipmb-7", "bmc-addr": 32, "remote-addr": 64, "devIndex": 1 } ] }
Config fields : type : This points to the ChannelType. It can be ME or ipmb channel. slave-path : The ipmb device path. bmc-addr : This is BMC target address to communicate between BMC and device. remote-addr : This is Remote/requester target address to communicate between BMC and device. devIndex : This devIndex used to identify the particular device/host.