<feed xmlns='http://www.w3.org/2005/Atom'>
<title>phosphor-pid-control/pid, 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-07-16T22:17:11+00:00</updated>
<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 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>explicitly expect a directory for logging</title>
<updated>2019-05-08T22:13:06+00:00</updated>
<author>
<name>Patrick Venture</name>
<email>venture@google.com</email>
</author>
<published>2019-05-08T22:02:55+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/phosphor-pid-control/commit/?id=89002dbdd13eb4fa7f35f2db7566291f720fd885'/>
<id>urn:sha1:89002dbdd13eb4fa7f35f2db7566291f720fd885</id>
<content type='text'>
Verify the logging parameter is explicitly a directory.  Treat the path
as a directory for creating the logging files.

Signed-off-by: Patrick Venture &lt;venture@google.com&gt;
Change-Id: I84d6be79780df3f52deeb1ff1b7a50de6175c055
</content>
</entry>
<entry>
<title>split parameters for logging and tuning</title>
<updated>2019-05-08T22:11:43+00:00</updated>
<author>
<name>Patrick Venture</name>
<email>venture@google.com</email>
</author>
<published>2019-05-08T21:50:00+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/phosphor-pid-control/commit/?id=de79ee05abd7e1b29b3074b0150b5f4eabf7cf9e'/>
<id>urn:sha1:de79ee05abd7e1b29b3074b0150b5f4eabf7cf9e</id>
<content type='text'>
add a flag to enable/disable tuning: default off
add an option for specifying a folder for outputting logs.

Closes: #10
Signed-off-by: Patrick Venture &lt;venture@google.com&gt;
Change-Id: I43864768f1dee8672f13288d3cf5a0c87c373aed
</content>
</entry>
<entry>
<title>Remove threads</title>
<updated>2019-04-07T16:34:02+00:00</updated>
<author>
<name>James Feist</name>
<email>james.feist@linux.intel.com</email>
</author>
<published>2019-03-12T18:20:16+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/phosphor-pid-control/commit/?id=ce6a3f36cedc2f822fb446bc5094eaeab47eb4af'/>
<id>urn:sha1:ce6a3f36cedc2f822fb446bc5094eaeab47eb4af</id>
<content type='text'>
This converts phosphor-pid-control into an async
single threaded application. The reason for doing this
is on our systems phosphor-pid-control had the largest
VSZ when viewed under top. Before this patch the VSZ
was at 50720, after it is at 7760.

Tested-by: Could still interact with all interfaces
under rest-dbus and sensor override worked to ramp fans
when changing cpu temps.

Change-Id: Ie0a837bdf0d1b1df61dc7aff87e5d503b9e0e875
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>
</feed>
