<feed xmlns='http://www.w3.org/2005/Atom'>
<title>phosphor-pid-control/test, branch master</title>
<subtitle>OpenBMC Phosphor PID controller daemon sources</subtitle>
<id>https://git.raptorcs.com/git/phosphor-pid-control/atom?h=master</id>
<link rel='self' href='https://git.raptorcs.com/git/phosphor-pid-control/atom?h=master'/>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/phosphor-pid-control/'/>
<updated>2019-09-10T17:47:17+00:00</updated>
<entry>
<title>conf: add ignoreDbusMinMax option</title>
<updated>2019-09-10T17:47:17+00:00</updated>
<author>
<name>Patrick Venture</name>
<email>venture@google.com</email>
</author>
<published>2019-09-10T16:18:28+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/phosphor-pid-control/commit/?id=6b9f59991b7f694866c98775b4179ae97c5e69a8'/>
<id>urn:sha1:6b9f59991b7f694866c98775b4179ae97c5e69a8</id>
<content type='text'>
Add an optional field to the sensor configuration, s.t. it'll tell a
dbus passive sensor to ignore the MinValue and MaxValue properties from
dbus.

Signed-off-by: Patrick Venture &lt;venture@google.com&gt;
Change-Id: Ia6a8c802c2dc5bf41e5e860b21d7764cc09e6b6b
</content>
</entry>
<entry>
<title>rename away from RPM</title>
<updated>2019-07-16T22:17:11+00:00</updated>
<author>
<name>Patrick Venture</name>
<email>venture@google.com</email>
</author>
<published>2019-07-16T21:31:13+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/phosphor-pid-control/commit/?id=f7a2dd5cbdd2dd5c3b892152f5a2e46d280f98de'/>
<id>urn:sha1:f7a2dd5cbdd2dd5c3b892152f5a2e46d280f98de</id>
<content type='text'>
The SetPoint output from a thermal PID is likely RPM, and that value is
then fed into a fan controller PID as the set-point (unit: RPM).  This
does not have to be RPM, however.  Continue renaming variables and
methods to remove the explicit unit-naming.

Signed-off-by: Patrick Venture &lt;venture@google.com&gt;
Change-Id: I570dee0c688338f9a458cac7123314717bee2b42
</content>
</entry>
<entry>
<title>rename RPMSetPoint to SetPoint</title>
<updated>2019-07-16T21:16:01+00:00</updated>
<author>
<name>Patrick Venture</name>
<email>venture@google.com</email>
</author>
<published>2019-07-16T17:50:37+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/phosphor-pid-control/commit/?id=9bbf333d0c4b6bb47959ef6d0395949fa0fe386c'/>
<id>urn:sha1:9bbf333d0c4b6bb47959ef6d0395949fa0fe386c</id>
<content type='text'>
The PIDs were originally focused on collecting RPM set points from
thermal PIDs and then having fan PIDs use the highest value collected,
it doesn't need to be strictly an RPM set point.

It does however need to be one type of value.

Signed-off-by: Patrick Venture &lt;venture@google.com&gt;
Change-Id: I1d589cf4b2688d7e86030c10496d737dc5bbdadf
</content>
</entry>
<entry>
<title>Add Fan Redundancy Support</title>
<updated>2019-06-05T17:21:16+00:00</updated>
<author>
<name>James Feist</name>
<email>james.feist@linux.intel.com</email>
</author>
<published>2019-06-03T23:24:53+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/phosphor-pid-control/commit/?id=98b704e179f12d987179fe6b0ea6234d1bace48f'/>
<id>urn:sha1:98b704e179f12d987179fe6b0ea6234d1bace48f</id>
<content type='text'>
This adds fan redundancy support to passive sensors.
If there are redundancy interfaces on dbus, we'll fail
a sensor if the status is set to failed.

Tested: Set Redundancy to Failed On Dbus, saw all fans
in collection boost. Then restarted swampd, came up
and still boosted. Set redundancy OK, and they all slowed
down.

Change-Id: I8879bef1471bbc168435d6b22dd20006b9dca133
Signed-off-by: James Feist &lt;james.feist@linux.intel.com&gt;
</content>
</entry>
<entry>
<title>Add stepwise parser</title>
<updated>2019-05-28T20:11:54+00:00</updated>
<author>
<name>Hank Liou</name>
<email>Hank.Liou@quantatw.com</email>
</author>
<published>2019-03-29T12:15:42+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/phosphor-pid-control/commit/?id=375f7098c232d38adcaab99b2f3ee561ded8c256'/>
<id>urn:sha1:375f7098c232d38adcaab99b2f3ee561ded8c256</id>
<content type='text'>
The json parser cannot read stepwise setting from config.
This change adds support to stepwise type of pid.

Change-Id: I650c5bd6a0040bf25630e33b3bd36abf388f0cd8
Signed-off-by: Hank Liou &lt;Hank.Liou@quantatw.com&gt;
</content>
</entry>
<entry>
<title>Check fans for failure</title>
<updated>2019-05-23T05:33:46+00:00</updated>
<author>
<name>Will Liang</name>
<email>will.liang@quantatw.com</email>
</author>
<published>2019-05-15T09:10:06+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/phosphor-pid-control/commit/?id=ded0ab5662212155e5d209343375e34ce9d34cdb'/>
<id>urn:sha1:ded0ab5662212155e5d209343375e34ce9d34cdb</id>
<content type='text'>
Add check the fan fail. If detect fan fail then into
the fail safe mode.

Signed-off-by: Will Liang &lt;will.liang@quantatw.com&gt;
Change-Id: I6ef9d42e131500c1b38a708e1c6fda15dc712f60
</content>
</entry>
<entry>
<title>Make dbusconfiguration reloadable without reboot</title>
<updated>2019-05-09T17:08:41+00:00</updated>
<author>
<name>James Feist</name>
<email>james.feist@linux.intel.com</email>
</author>
<published>2019-05-07T16:17:16+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/phosphor-pid-control/commit/?id=1fe08952e5bc827003a0621ae4cf7e688a458eb8'/>
<id>urn:sha1:1fe08952e5bc827003a0621ae4cf7e688a458eb8</id>
<content type='text'>
Now that asio is being used instead of threads, we can
reload the fan configuration without having to restart the
application. This moves the ownership of the passive and host
bus outside of the SensorManager so that it can be recreated
each reload.

Tested: Watched logs and saw full fan config get reloaded
after changing fan configuration

Tested: Ran on json configured system and it behaved as
expected.

Change-Id: I00e6b27f75384fd41de2017b723f159c9691ae97
Signed-off-by: James Feist &lt;james.feist@linux.intel.com&gt;
</content>
</entry>
<entry>
<title>Consolidate all util.hpp</title>
<updated>2019-05-08T22:33:33+00:00</updated>
<author>
<name>James Feist</name>
<email>james.feist@linux.intel.com</email>
</author>
<published>2019-05-08T22:33:33+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/phosphor-pid-control/commit/?id=0c8223b5f5c280276d432eab5e32694a90451239'/>
<id>urn:sha1:0c8223b5f5c280276d432eab5e32694a90451239</id>
<content type='text'>
This deletes all lower level util.hpp and cats them
into the top level util.hpp to avoid name conflicts.

Change-Id: Ia11e4a08053a3970b0aadf21d1156ab26def36bd
Signed-off-by: James Feist &lt;james.feist@linux.intel.com&gt;
</content>
</entry>
<entry>
<title>bugfix: grab hystersis parameter from pid json</title>
<updated>2019-03-26T14:13:12+00:00</updated>
<author>
<name>Patrick Venture</name>
<email>venture@google.com</email>
</author>
<published>2019-03-26T14:10:59+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/phosphor-pid-control/commit/?id=e3eeef45a722b57d4c3bb379df165e0bd14993bd'/>
<id>urn:sha1:e3eeef45a722b57d4c3bb379df165e0bd14993bd</id>
<content type='text'>
The code incorrectly attempts to read the hystersis parameters from the
wrong scope of the json object.  This fixes it to read from the pid
configuration's scope.

Tested: Added a new unit-test to hit this case.
Change-Id: I808bc907ec33a0b12d68a88fd316c3c9fae41516
Signed-off-by: Patrick Venture &lt;venture@google.com&gt;
</content>
</entry>
<entry>
<title>autotools: Fix for autoconf-archive 2019.01.19</title>
<updated>2019-03-19T16:10:41+00:00</updated>
<author>
<name>Patrick Venture</name>
<email>venture@google.com</email>
</author>
<published>2019-03-19T16:10:41+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/phosphor-pid-control/commit/?id=90e9dbcae6c1df3127dd3de41f9d1e1b5a438828'/>
<id>urn:sha1:90e9dbcae6c1df3127dd3de41f9d1e1b5a438828</id>
<content type='text'>
The code coverage macros from the archive changed in a backward
incompatible way. This adds a workaround to autodetect either version
and do the right thing.

Change-Id: I63d1cdf6edb125d75872d6dae38f8602fc043431
Signed-off-by: Patrick Venture &lt;venture@google.com&gt;
</content>
</entry>
</feed>
