A few questions regarding porting to a new board

[Lei YU]

> Here are some issues I’ve run into and I’m wondering if anyone has any answers or tips they could help out with.

> I’ve been trying to set up some GPIOs and I was able to add LED and GPIO Keys, but I’m having trouble with power related pins. I added a gpio_defs.json file and tried a rebuild but noticed that it wasn’t ending up in the target rootfs. I noticed then that by including conf/machine/include/openpower.inc in my machine.conf file that it would.
>
> Is the workbook still a requirement? Do I need to make a .py file as my workbook? Is there one location where all GPIOs should be defined or are they separated out into different services now?
> Should conf/machine/include/openpower.inc be the first thing to add to a machine.conf file or is it better to select the features manually?
>
> Are there any default configurations that are needed in new machines? From looking at a few different ones (ast2500/Romulus/etc) there doesn’t seem to me to be a standard structure.

The doc [add-new-system.md][1] is updated to include these topics.
You could refer to the LED, GPIO sections.

>
> From what I can tell I have phosphor-state-manager included in my build, but obmcutil is not present. Is there a way to verify that I’m using the correct phosphor-state-manager and to include obmcutil?

obmcutil is a standalone utility, not part of phosphor-state-manager.
It is defined in meta-phosphor/recipes-phosphor/devtools/obmc-pydevtools_git.bb,
and installed by
meta-openpower/recipes-phosphor/packagegroups/packagegroup-obmc-apps.bbappend

[1]: https://github.com/openbmc/docs/blob/master/development/add-new-system.md