mctp-controller-init: add i2c bus config

At the moment, the config for add i2c bug is done in
${machine}-mctp-i2c-bus-config.bb. It would be easier to ensure the i2c
bus be config here and make it fail to build if it's not.

Also, remove some configs don't take any effect.

Tested:
- building mctp-controller-init for my system without overriding:
```
| DEBUG: Executing shell function do_install
| Missing GBMC_MCTP_BUSES
```
- building mctp-controller-init for my system with go/gbmcl/156051:
```
cat tmp/work/*/mctp-controller-init/*/package/usr/share/mctp/i2c-bus-config.sh
bus="1 2 3 4 5 6 7 8 9"
```

Google-Bug-Id: 299414396
Signed-off-by: Tom Tung <tomtung@google.com>
Change-Id: I26f9d848ece69096ce8b1a155c3b3ea2ea36be6e
(cherry picked from commit d6196b85f18c1028f7855a424e54c6368cf979e3)
1 file changed
tree: ad16c9e3f8f944671dc4fda53aaa8358666de3f0
  1. conf/
  2. dynamic-layers/
  3. recipes-bsp/
  4. recipes-connectivity/
  5. recipes-core/
  6. recipes-devtools/
  7. recipes-extended/
  8. recipes-google/
  9. recipes-kernel/
  10. recipes-phosphor/
  11. LICENSE
  12. README.md
README.md

meta-gbmc-staging

This repository contains additions to the openbmc/meta-google layer that are not yet ready for OpenBMC inclusion.

How to use this layer

  1. Clone openbmc/openbmc from GitHub.
  2. Clone this layer from GitHub into a subdirectory of openbmc.