Fix MD040 warnings

The following warnings are generated by using markdownlint analysis:
```
MD040/fenced-code-language Fenced code blocks should have a language specified [Context: "```"]
```
Refer

Fix MD040 warnings

The following warnings are generated by using markdownlint analysis:
```
MD040/fenced-code-language Fenced code blocks should have a language specified [Context: "```"]
```
Refer to markdown-lint [1] to fix MD040
[1]: https://github.com/updownpress/markdown-lint/blob/master/rules/040-fenced-code-language.md

Signed-off-by: George Liu <liuxiwei@ieisystem.com>
Change-Id: Ie866ac8c3d8e33d2c8811f7c6a5965d6dad1f88a

show more ...

Fix MD033 warnings

The following warnings are generated by using markdownlint analysis:
```
MD033/no-inline-html Inline HTML [Element: code]
MD033/no-inline-html Inline HTML [Element: pre]
MD033/no-

Fix MD033 warnings

The following warnings are generated by using markdownlint analysis:
```
MD033/no-inline-html Inline HTML [Element: code]
MD033/no-inline-html Inline HTML [Element: pre]
MD033/no-inline-html Inline HTML [Element: b]
MD033/no-inline-html Inline HTML [Element: i]
```
Refer to markdown-lint [1] to fix MD033
[1]: https://github.com/updownpress/markdown-lint/blob/master/rules/033-no-inline-html.md

Signed-off-by: George Liu <liuxiwei@ieisystem.com>
Change-Id: I7dfb63e9f3a663cfea60b5d0a0a4ae8540ddd1d6

show more ...

docs/presence/rpolicy.md: Fix MD033 warnings

The following warnings are generated by using markdownlint analysis:
```
docs/presence/rpolicy.md:37:6 MD033/no-inline-html Inline HTML [Element: code]
d

docs/presence/rpolicy.md: Fix MD033 warnings

The following warnings are generated by using markdownlint analysis:
```
docs/presence/rpolicy.md:37:6 MD033/no-inline-html Inline HTML [Element: code]
docs/presence/rpolicy.md:37:1 MD033/no-inline-html Inline HTML [Element: pre]
docs/presence/rpolicy.md:50:5 MD033/no-inline-html Inline HTML [Element: b]
docs/presence/rpolicy.md:50:8 MD033/no-inline-html Inline HTML [Element: i]
```
Refer to markdown-lint [1] to fix MD033
[1]: https://github.com/updownpress/markdown-lint/blob/master/rules/033-no-inline-html.md

Signed-off-by: George Liu <liuxiwei@ieisystem.com>
Change-Id: I31748039b2f6a5bae46245a416dbde2eed4f3699

show more ...

docs/presence/rpolicy.md: Fix MD040 warnings

The following warnings are generated by using markdownlint analysis:
```
MD040/fenced-code-language Fenced code blocks should have a language specified [

docs/presence/rpolicy.md: Fix MD040 warnings

The following warnings are generated by using markdownlint analysis:
```
MD040/fenced-code-language Fenced code blocks should have a language specified [Context: "```"]
```
Refer to markdown-lint [1] to fix MD040
[1]: https://github.com/updownpress/markdown-lint/blob/master/rules/040-fenced-code-language.md

Signed-off-by: George Liu <liuxiwei@ieisystem.com>
Change-Id: Ic2ddba30a55a328af2528afc56a2147c7ceb6f59

show more ...

docs/presence/README.md: Fix MD040 warnings

The following warnings are generated by using markdownlint analysis:
```
MD040/fenced-code-language Fenced code blocks should have a language specified [C

docs/presence/README.md: Fix MD040 warnings

The following warnings are generated by using markdownlint analysis:
```
MD040/fenced-code-language Fenced code blocks should have a language specified [Context: "```"]
```
Refer to markdown-lint [1] to fix MD040
[1]: https://github.com/updownpress/markdown-lint/blob/master/rules/040-fenced-code-language.md

Signed-off-by: George Liu <liuxiwei@ieisystem.com>
Change-Id: Icb601fbd199f536600d35322b7aca19371be00a4

show more ...

Use generic interface to look for configs

IBM has specific interface IBMCompatibleSystem to look for the
compatible system location under which the configs are placed. The
Entity Manager schema for

Use generic interface to look for configs

IBM has specific interface IBMCompatibleSystem to look for the
compatible system location under which the configs are placed. The
Entity Manager schema for the property under this interface and the
interface name itself can't be generic for other meta systems.
To find a more common interface, this should be the one that is probed
together with chassis and has its property value corresponding to
system's name.

This commit proposes the use of the property Names under the interface
xyz.openbmc_project.Inventory.Decorator.Compatible [1]. The property
can be configured in chassis's Entity Manager json configuration with
a list of one or more compatible system strings. The usage of this
interface was mentioned in document [2].

[1] https://github.com/openbmc/phosphor-dbus-interfaces/blob/master/\
yaml/xyz/openbmc_project/Inventory/Decorator/Compatible.interface.yaml
[2] https://github.com/openbmc/phosphor-dbus-interfaces/blob/master/\
yaml/xyz/openbmc_project/Software/README.md#compatibility

Tested in Ampere's Mt.Mitchell platform.

1. Configure the interface in Motherboard's Entity Manager config:
"xyz.openbmc_project.Inventory.Decorator.Compatible": {
"Names": ["com.ampere.Hardware.Chassis.Model.MtMitchell"]
}
2. Configs are already placed under
/usr/share/phosphor-fan-presence/<daemon>/\
com.ampere.Hardware.Chassis.Model.MtMitchell/
3. When Entity Manager config is probed:
$ busctl call -j xyz.openbmc_project.ObjectMapper \
/xyz/openbmc_project/object_mapper xyz.openbmc_project.ObjectMapper \
GetSubTreePaths sias / 0 1
xyz.openbmc_project.Inventory.Decorator.Compatible
{
"type": "a{sa{sas}}",
"data": [
[
"/xyz/openbmc_project/inventory/system/board/\
Mt_Mitchell_Motherboard" : {
"xyz.openbmc_project.EntityManager" : [
...
"xyz.openbmc_project.Inventory.Decorator.Compatible
]
}
]
]
}

$ busctl get-property xyz.openbmc_project.EntityManager \
/xyz/openbmc_project/inventory/system/board/Mt_Mitchell_Motherboard \
xyz.openbmc_project.Inventory.Decorator.Compatible Names
as 1 "com.ampere.Hardware.Chassis.Model.MtMitchell"
4. When phosphor-fan's daemon starts, it can successfully find
configs under the folder "com.ampere.Hardware.Chassis.Model.MtMitchell"

Signed-off-by: Chau Ly <chaul@amperecomputing.com>
Change-Id: I55107f1c2a78e78ba7cea650b8eaeaf4fd615d2b

show more ...

prettier: re-format

Prettier is enabled in openbmc-build-scripts on Markdown, JSON, and YAML
files to have consistent formatting for these file types. Re-run the
formatter on the whole repository.

prettier: re-format

Prettier is enabled in openbmc-build-scripts on Markdown, JSON, and YAML
files to have consistent formatting for these file types. Re-run the
formatter on the whole repository.

Change-Id: I961ec77b2617da3e097e64e0d8e8980bb7e5b426
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>

show more ...

pres: Add way to bind fan eeprom driver after plug

Some fans have EEPROMs on them that are read by other BMC code so the
contents can be added to the BMC inventory. Since fans can usually be
hotplu

pres: Add way to bind fan eeprom driver after plug

Some fans have EEPROMs on them that are read by other BMC code so the
contents can be added to the BMC inventory. Since fans can usually be
hotplugged, this means those EEPROMs need to be read after a fan is
plugged, and there was previously no method to trigger that.

This commit adds functionality to phosphor-fan-presence-tach to bind the
EEPROM driver to the new device after a fan with an EEPROM is plugged.
This triggers a udev event which triggers EEPROM reads if the platform
is configured to do so.

This is done with a new optional JSON section in the config.json, which
looks like:
"eeprom": {
"bus_address": "31-0050",
"driver_name": "at24",
"bind_delay_ms": 1000
}

The 'bus_address' field is the device's I2C bus and address string as it
is represented in the I2C subsystem in sysfs. The 'driver_name' field
is the name of the device driver that manages that device. The
'bind_delay_ms' field allows there to be a defined amount of time
between when the device is plugged and when the driver is bound, in case
a certain amount of time is required for the device to come online after
it receives power.

Signed-off-by: Matt Spinler <spinler@us.ibm.com>
Change-Id: I10d36efab954393239e6face96244ecd34035596

show more ...

docs: Update presence GPIO I2C path

Use the shorter /sys/bus/i2c/devices/ path.

Signed-off-by: Matt Spinler <spinler@us.ibm.com>
Change-Id: I57c1f1175c855cae32d7fd63f778324450b2dc63

docs:presence: Configuration content and syntax

Fill in fan presence JSON configuration content and syntax documentation
for each attribute available in configuring how a fan is detected to be
prese

docs:presence: Configuration content and syntax

Fill in fan presence JSON configuration content and syntax documentation
for each attribute available in configuring how a fan is detected to be
present or not.

Signed-off-by: Matthew Barth <msbarth@us.ibm.com>
Change-Id: Ie137031b76d956a352967339cd5553d1179bcfa5

show more ...

docs: Initial config details for each fan app

Created initial README.md files for each fan app to outline the details
and the framework of their configuration file(s). This was placed in a
`docs` di

docs: Initial config details for each fan app

Created initial README.md files for each fan app to outline the details
and the framework of their configuration file(s). This was placed in a
`docs` directory instead of each app's directory as the intention is to
have a `src` directory containing all the apps in the future. Additional
details to these READMEs will be added as each fan app solidifies on its
JSON configuration structure and usage.

*Note: A future commit will add all the details to fan presence's README
as the majority of its JSON configuration framework is complete.

*Note: A follow-on commit to this will create a fan monitor JSON
configuration example.

Signed-off-by: Matthew Barth <msbarth@us.ibm.com>
Change-Id: If80a7567fb7a121e8e7dfee3eb0842a6931ecb6b

show more ...