<feed xmlns='http://www.w3.org/2005/Atom'>
<title>phosphor-fan-presence/control/example, branch 04-16-2019</title>
<subtitle>OpenBMC Phosphor fan detection and control sources</subtitle>
<id>https://git.raptorcs.com/git/phosphor-fan-presence/atom?h=04-16-2019</id>
<link rel='self' href='https://git.raptorcs.com/git/phosphor-fan-presence/atom?h=04-16-2019'/>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/phosphor-fan-presence/'/>
<updated>2018-02-26T02:34:36+00:00</updated>
<entry>
<title>Add target interface for fan control</title>
<updated>2018-02-26T02:34:36+00:00</updated>
<author>
<name>Lei YU</name>
<email>mine260309@gmail.com</email>
</author>
<published>2018-01-31T08:47:37+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/phosphor-fan-presence/commit/?id=069e4405a6926cdacc33c0826075356da2cd9dbd'/>
<id>urn:sha1:069e4405a6926cdacc33c0826075356da2cd9dbd</id>
<content type='text'>
Current fan control assumes the use of the FanSpeed interface for fan
targets.
For fans controlled by pwm, FanPwm interface is added.

This commit adds "target_interface" config parameter, so that user can
specify the interface for the fan targets.

E.g.

  - inventory: /system/chassis/motherboard/fan0
    cooling_zone: 0
    cooling_profile: air
    sensors:
      - fan0
    target_interface: xyz.openbmc_project.Control.FanPwm

The config is optional and defaults to FanSpeed, so the current code
will not be affected.

Tested: Use this config on Romulus, ensures the fan control sets
        target on FanPwm interface and works fine.

Change-Id: I73adccaa770d657b5d7aaeb307917f89588524de
Signed-off-by: Lei YU &lt;mine260309@gmail.com&gt;
</content>
</entry>
<entry>
<title>Generate selected match strings and signals</title>
<updated>2017-11-07T19:54:35+00:00</updated>
<author>
<name>Matthew Barth</name>
<email>msbarth@us.ibm.com</email>
</author>
<published>2017-09-22T17:43:57+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/phosphor-fan-presence/commit/?id=67967f9a3f8e779d897a66cc6d559783911b2c14'/>
<id>urn:sha1:67967f9a3f8e779d897a66cc6d559783911b2c14</id>
<content type='text'>
The available matches and their associated signals are now listed
within the events yaml and can be added to the list of matches to
register for per event.

Change-Id: I65f657038afe7c68a421adb4820ea09e275be06d
Signed-off-by: Matthew Barth &lt;msbarth@us.ibm.com&gt;
</content>
</entry>
<entry>
<title>DOC ONLY: Add preconditions section description</title>
<updated>2017-11-06T19:47:49+00:00</updated>
<author>
<name>Matthew Barth</name>
<email>msbarth@us.ibm.com</email>
</author>
<published>2017-09-28T19:37:41+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/phosphor-fan-presence/commit/?id=e3bab01d16c1b2b126b37295b13911bf17bfb0bd'/>
<id>urn:sha1:e3bab01d16c1b2b126b37295b13911bf17bfb0bd</id>
<content type='text'>
Change-Id: I260319dbfc4cb87bfed8fd724ffc4978f34e7325
Signed-off-by: Matthew Barth &lt;msbarth@us.ibm.com&gt;
</content>
</entry>
<entry>
<title>DOC ONLY: Example events yaml format update</title>
<updated>2017-09-18T15:35:19+00:00</updated>
<author>
<name>Matthew Barth</name>
<email>msbarth@us.ibm.com</email>
</author>
<published>2017-09-14T14:40:35+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/phosphor-fan-presence/commit/?id=dd5cad66253f9d3b3e33a4668c9c8ac5ebf9d914'/>
<id>urn:sha1:dd5cad66253f9d3b3e33a4668c9c8ac5ebf9d914</id>
<content type='text'>
Made updates to the example events.yaml to reflect the new format and
use.

Change-Id: I13b323487565f0c1c29eb97d9ddcf8da3295b21c
Signed-off-by: Matthew Barth &lt;msbarth@us.ibm.com&gt;
</content>
</entry>
<entry>
<title>Update parser to support optional preconditions</title>
<updated>2017-08-08T21:24:15+00:00</updated>
<author>
<name>Matthew Barth</name>
<email>msbarth@us.ibm.com</email>
</author>
<published>2017-08-08T19:20:43+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/phosphor-fan-presence/commit/?id=9af190cd94e68b378da4e25accb5c03258a2fb31'/>
<id>urn:sha1:9af190cd94e68b378da4e25accb5c03258a2fb31</id>
<content type='text'>
Set speed events are now allowed to have preconditions defined within
the event where those preconditions must be met before the set speed
event is enabled and active. The supported precondition added is against
a list of groups and their properties matching a given value.

The parser generates a precondition with the same layout as a set speed
event where the event is nested as the last parameter to the
precondition function. Having the set speed event as the last input
parameter to precondition functions is required.

Resolves openbmc/openbmc#1835

Change-Id: I7a247e7eb2d6b31ba9a60da1bc321a35edda9b24
Signed-off-by: Matthew Barth &lt;msbarth@us.ibm.com&gt;
</content>
</entry>
<entry>
<title>Fan control: Example yaml updates(doc only)</title>
<updated>2017-07-06T22:25:12+00:00</updated>
<author>
<name>Matthew Barth</name>
<email>msbarth@us.ibm.com</email>
</author>
<published>2017-06-29T20:12:08+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/phosphor-fan-presence/commit/?id=be605c5f8da935afb7dd13300cab24e986d3a474'/>
<id>urn:sha1:be605c5f8da935afb7dd13300cab24e986d3a474</id>
<content type='text'>
Change-Id: I30fdecd3af3dcdc7f954bdb9d535c6bc92edd67a
Signed-off-by: Matthew Barth &lt;msbarth@us.ibm.com&gt;
</content>
</entry>
<entry>
<title>Example zone conditions yaml</title>
<updated>2017-06-26T02:06:05+00:00</updated>
<author>
<name>Gunnar Mills</name>
<email>gmills@us.ibm.com</email>
</author>
<published>2017-06-05T19:08:41+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/phosphor-fan-presence/commit/?id=63605cd3b7c66f2fbfeb40f85a1fb3ce1ab87424'/>
<id>urn:sha1:63605cd3b7c66f2fbfeb40f85a1fb3ce1ab87424</id>
<content type='text'>
An example yaml file for zone conditions to be used to
create the correct fan zones.

Change-Id: I6ca339a3a9f37bc70424cde57f2229a5dcb70cbb
Signed-off-by: Gunnar Mills &lt;gmills@us.ibm.com&gt;
</content>
</entry>
<entry>
<title>Remove TBD on zone conditions in zones.yaml</title>
<updated>2017-06-26T02:06:05+00:00</updated>
<author>
<name>Gunnar Mills</name>
<email>gmills@us.ibm.com</email>
</author>
<published>2017-06-05T17:37:35+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/phosphor-fan-presence/commit/?id=620e4342f67c758bef3e8121c29236cc23a84b8b'/>
<id>urn:sha1:620e4342f67c758bef3e8121c29236cc23a84b8b</id>
<content type='text'>
Change-Id: I8eb215aaf90ef9553a52e8eaa54d3fd1a1a00ca5
Signed-off-by: Gunnar Mills &lt;gmills@us.ibm.com&gt;
</content>
</entry>
<entry>
<title>Example set speed event yaml</title>
<updated>2017-05-31T15:55:55+00:00</updated>
<author>
<name>Matthew Barth</name>
<email>msbarth@us.ibm.com</email>
</author>
<published>2017-05-11T21:35:10+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/phosphor-fan-presence/commit/?id=94b20f7a0fc9d42846d44579e90c60769e4e43cf'/>
<id>urn:sha1:94b20f7a0fc9d42846d44579e90c60769e4e43cf</id>
<content type='text'>
An example yaml file to define set speed events based on groups of dbus
object properties and a set of actions that can be performed based on
those property values

Change-Id: I2f713920f9ce25859855cfec783df0adb505f31d
Signed-off-by: Matthew Barth &lt;msbarth@us.ibm.com&gt;
</content>
</entry>
<entry>
<title>Change example/zones.yaml to full_speed</title>
<updated>2017-05-24T04:58:35+00:00</updated>
<author>
<name>Gunnar Mills</name>
<email>gmills@us.ibm.com</email>
</author>
<published>2017-05-22T19:02:18+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/phosphor-fan-presence/commit/?id=07710ef7ea44e406943a87e22ee71f2302081245'/>
<id>urn:sha1:07710ef7ea44e406943a87e22ee71f2302081245</id>
<content type='text'>
initial_speed should be full_speed in example/zones.yaml

Change-Id: I64b4803a26006cf78f6d29859bb8dd43a5cf63b3
Signed-off-by: Gunnar Mills &lt;gmills@us.ibm.com&gt;
</content>
</entry>
</feed>
