Fix MD030 warnings

The following warnings are generated by using markdownlint analysis:
```
tuning.md:68:1 MD030/list-marker-space Spaces after list markers [Expected: 1; Actual: 2]
tuning.md:69:1 M

Fix MD030 warnings

The following warnings are generated by using markdownlint analysis:
```
tuning.md:68:1 MD030/list-marker-space Spaces after list markers [Expected: 1; Actual: 2]
tuning.md:69:1 MD030/list-marker-space Spaces after list markers [Expected: 1; Actual: 2]
tuning.md:72:1 MD030/list-marker-space Spaces after list markers [Expected: 1; Actual: 2]
tuning.md:74:1 MD030/list-marker-space Spaces after list markers [Expected: 1; Actual: 2]
tuning.md:75:1 MD030/list-marker-space Spaces after list markers [Expected: 1; Actual: 2]
tuning.md:76:1 MD030/list-marker-space Spaces after list markers [Expected: 1; Actual: 2]
```
Refer to markdown-lint [1] to fix MD030
[1]: https://github.com/updownpress/markdown-lint/blob/master/rules/030-list-marker-space.md

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

show more ...

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: I3106563ab231739d23314fc11de30082e959b87e

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: I834909dc663e8762217517eab4a4294174d3bcf2
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>

show more ...

Adding new feature of core PID loop logging

This differs from the normal logging,
as this focuses on the core of the PID loop computations.

All variables within the core pid/ec/pid.cpp pid()
functi

Adding new feature of core PID loop logging

This differs from the normal logging,
as this focuses on the core of the PID loop computations.

All variables within the core pid/ec/pid.cpp pid()
function are now logged, so math can be debugged.

Output is throttled to only log a new line
when it changes, or when 60 seconds have elapsed.

Creates 2 files for each PID loop,
one showing coefficients that were configured for it,
and one showing the variables changing over time.

Enable by --corelogging command line option,
or by creating /etc/thermal.d/corelogging file.

Tested:
Log files appear as expected, when enabled.
No changes noticed, when this feature is disabled.

Signed-off-by: Josh Lehan <krellan@google.com>
Change-Id: I3f37fe918e7cbc6fb885ffa2f268600d5a317d32

show more ...

s/swampd.service/phosphor-pid-control.service/g

Signed-off-by: Patrick Venture <venture@google.com>
Change-Id: Ia1f08915f5541142cb3e10aa68043d3d2cad0167

docs: Add a small guide for thermal tuning

Add a guide explaining the tuning procedure and logging
format, and point README to it

Signed-off-by: Kun Yi <kunyi731@gmail.com>
Change-Id: I287b0ef4a5ed

docs: Add a small guide for thermal tuning

Add a guide explaining the tuning procedure and logging
format, and point README to it

Signed-off-by: Kun Yi <kunyi731@gmail.com>
Change-Id: I287b0ef4a5ede1c62751d1671e2eec188133a074

show more ...