<feed xmlns='http://www.w3.org/2005/Atom'>
<title>blackbird-obmc-linux/drivers, branch dev-5.0-raptor-04-16-2019</title>
<subtitle>Blackbird™ Linux sources for OpenBMC</subtitle>
<id>https://git.raptorcs.com/git/blackbird-obmc-linux/atom?h=dev-5.0-raptor-04-16-2019</id>
<link rel='self' href='https://git.raptorcs.com/git/blackbird-obmc-linux/atom?h=dev-5.0-raptor-04-16-2019'/>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/blackbird-obmc-linux/'/>
<updated>2019-05-10T21:20:52+00:00</updated>
<entry>
<title>hwmon/aspeed-pwm-tacho: Increase tachometer read time</title>
<updated>2019-05-10T21:20:52+00:00</updated>
<author>
<name>Raptor Engineering Development Team</name>
<email>support@raptorengineering.com</email>
</author>
<published>2019-05-10T21:19:12+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/blackbird-obmc-linux/commit/?id=551af99b5cadeeff8bb97b97b3afa82421b7eca0'/>
<id>urn:sha1:551af99b5cadeeff8bb97b97b3afa82421b7eca0</id>
<content type='text'>
On the Blackbird desk-side systems we expect users will be running
large fans very slowly.  The current tachometer reading drops to
zero under those conditions, resulting in failed fan detection
systems kicking in.

Increase the tachometer read time to allow for slower fans to
return a valid speed.  This does make read slower, but more
advance fan control software should be able to compensate via
e.g. PID loops.

Signed-off-by: Timothy Pearson &lt;tpearson@raptorengineering.com&gt;
</content>
</entry>
<entry>
<title>hwmon/aspeed-pwm-tacho: Return 0 RPM if fan disconnected / failed</title>
<updated>2019-05-10T21:18:33+00:00</updated>
<author>
<name>Raptor Engineering Development Team</name>
<email>support@raptorengineering.com</email>
</author>
<published>2019-05-10T05:28:43+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/blackbird-obmc-linux/commit/?id=6a2f7452a635071a267d8a888a21038263efbca5'/>
<id>urn:sha1:6a2f7452a635071a267d8a888a21038263efbca5</id>
<content type='text'>
Having a tachometer read return an -ETIMEDOUT error condition
instead of 0 RPM due to a disconnected or failed fan is highly
unexpected, and depending on higher level software can cause
application failures.

Return 0 RPM if tachometer cannot be read.  This should trigger
the same error paths in any sane fan control implementation without
requiring special handling for the AST2x00 devices.

Signed-off-by: Timothy Pearson &lt;tpearson@raptorengineering.com&gt;
</content>
</entry>
<entry>
<title>pinctrl/aspeed: Remove COND2 condition from GPIOR1</title>
<updated>2019-05-03T09:47:38+00:00</updated>
<author>
<name>Raptor Engineering Development Team</name>
<email>support@raptorengineering.com</email>
</author>
<published>2019-05-03T09:44:50+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/blackbird-obmc-linux/commit/?id=e97ed63c2118273a987e4efd922e479ea54ac4c6'/>
<id>urn:sha1:e97ed63c2118273a987e4efd922e479ea54ac4c6</id>
<content type='text'>
On Blackbird hardware, ball T19 is set to FWSPICS2# even when
COND2 (SCU94[1:0] == 0x0) is not met.  Since COND2 is listed
as a requirement for FWSPICS2#, the pinmux controller can choose
to set SCU88[25]=1 even when GPIOR1 is hogged.  Due to the
documentation error, this results in ball T19 assigned to
FWSPICS2# instead of GPIOR1, leading to a failure of the Blackbird
platform.

Tested on Blackbird harwdare; GPIOR1 functions normally with
this patch and does not reliably function without it.

Signed-off-by: Timothy Pearson &lt;tpearson@raptorengineering.com&gt;
</content>
</entry>
<entry>
<title>aspeed/pinctrl: Fix simultaneous DVO and serial outputs on AST2500 devices</title>
<updated>2019-05-03T05:07:01+00:00</updated>
<author>
<name>Raptor Engineering Development Team</name>
<email>support@raptorengineering.com</email>
</author>
<published>2019-05-01T21:32:08+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/blackbird-obmc-linux/commit/?id=d32565cb60fbf6a13801dca1373b5c46dcb631b6'/>
<id>urn:sha1:d32565cb60fbf6a13801dca1373b5c46dcb631b6</id>
<content type='text'>
There appears to be a significant error in the pinmux table starting on
page 127 of the AST2500 datasheet v1.6.  Specifically, the COND2 (DVO)
requirement is incorrectly applied to multiple digital video input (DVI)
muxed pins, and no DVI-specific condition is provided.  This results in
the serial devices incorrectly overriding the DVO pinmuxes and disabling
the DVO pins.

Create a new condition code (COND6) for DVI enable, and update the most
seriously affected pins to use the new condition code.

Signed-off-by: Timothy Pearson &lt;tpearson@raptorengineering.com&gt;
</content>
</entry>
<entry>
<title>aspeed/pinctrl: Fix simultaneous RS-232 / PWM and DVO outputs on AST2500 devices</title>
<updated>2019-05-03T05:07:00+00:00</updated>
<author>
<name>Raptor Engineering Development Team</name>
<email>support@raptorengineering.com</email>
</author>
<published>2019-05-01T21:06:29+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/blackbird-obmc-linux/commit/?id=7518ee68db4cdc8bcd34f488aee7a402037a2c6c'/>
<id>urn:sha1:7518ee68db4cdc8bcd34f488aee7a402037a2c6c</id>
<content type='text'>
There appears to be a small error in the pinmux table on pages 130 and
131 of the AST2500 datasheet v1.6.  Specifically, the COND2 requirement
used to mux the surrounding pins to DVI was inadvertently replicated to
pins V1, W1, V2, and W2 in the table, which do not incorporate DVI
functionality.

As a result of this error, both serial TX lines and the PWM 0/1 outputs
were overriding the VPO pinmux settings when VPO was enabled in the
pinmux hogs.

This patch has been verified to function on Blackbird hardware.  Both
serial TXD pins and PWM0/PWM1 were functionally tested with SCU94[1:0]
set to 0x1.

Signed-off-by: Timothy Pearson &lt;tpearson@raptorengineering.com&gt;
</content>
</entry>
<entry>
<title>drm/aspeed: Add DVO output option to GFX driver</title>
<updated>2019-05-02T21:04:17+00:00</updated>
<author>
<name>Raptor Engineering Development Team</name>
<email>support@raptorengineering.com</email>
</author>
<published>2019-05-02T20:48:21+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/blackbird-obmc-linux/commit/?id=8e9a4348c814e3ce0e740abc981213059560f35b'/>
<id>urn:sha1:8e9a4348c814e3ce0e740abc981213059560f35b</id>
<content type='text'>
The AST2500 offers an alternate GFX output mode over DVO.
Enable DVO or VGA output mode conditionally based on two new
device tree properties, output-vga and output-dvo.

Signed-off-by: Timothy Pearson &lt;tpearson@raptorengineering.com&gt;
</content>
</entry>
<entry>
<title>drm/aspeed: Preserve DVO configuration bits during initialization</title>
<updated>2019-05-02T20:54:16+00:00</updated>
<author>
<name>Raptor Engineering Development Team</name>
<email>support@raptorengineering.com</email>
</author>
<published>2019-05-01T11:21:53+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/blackbird-obmc-linux/commit/?id=ff0ff5cc20e070ac2a2d1370023e505b635ffe15'/>
<id>urn:sha1:ff0ff5cc20e070ac2a2d1370023e505b635ffe15</id>
<content type='text'>
GFX064 contains DVO enable and mode bits.  These are hardware specific, configured
via the pinmux from the DT, and should not be cleared during startup.

Signed-off-by: Timothy Pearson &lt;tpearson@raptorengineering.com&gt;
</content>
</entry>
<entry>
<title>Add missing license declaration call to common OCC file This fixes symbol access errors and taint when built as a module</title>
<updated>2019-04-19T11:33:16+00:00</updated>
<author>
<name>Timothy Pearson</name>
<email>tpearson@raptorengineering.com</email>
</author>
<published>2018-05-15T21:28:45+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/blackbird-obmc-linux/commit/?id=695541f48b4a458c8fcbd2830337797045d3b1d2'/>
<id>urn:sha1:695541f48b4a458c8fcbd2830337797045d3b1d2</id>
<content type='text'>
Signed-off-by: Timothy Pearson &lt;tpearson@raptorengineering.com&gt;
</content>
</entry>
<entry>
<title>hwmon: (pmbus/isl68137): Update ISL68137 to upstream</title>
<updated>2019-04-19T02:29:09+00:00</updated>
<author>
<name>Patrick Venture</name>
<email>venture@google.com</email>
</author>
<published>2019-04-18T14:36:13+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/blackbird-obmc-linux/commit/?id=b1b37a25644213428f4bab4c427581dd923e35da'/>
<id>urn:sha1:b1b37a25644213428f4bab4c427581dd923e35da</id>
<content type='text'>
Apply differences from hwmon review to bring the driver code to the same
point.  There were some key differences regarding attribute placement
from the review, beyond the normal cleanup.

OpenBMC-Staging-Count: 1
Signed-off-by: Patrick Venture &lt;venture@google.com&gt;
[AJ: Rework subject]
Signed-off-by: Andrew Jeffery &lt;andrew@aj.id.au&gt;
</content>
</entry>
<entry>
<title>pmbus: support for custom sysfs attributes</title>
<updated>2019-04-19T02:27:48+00:00</updated>
<author>
<name>krzysztof.adamski@nokia.com</name>
<email>krzysztof.adamski@nokia.com</email>
</author>
<published>2019-04-18T14:36:04+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/blackbird-obmc-linux/commit/?id=d7e7edaf5887c6c01c44d1c18609705847965e06'/>
<id>urn:sha1:d7e7edaf5887c6c01c44d1c18609705847965e06</id>
<content type='text'>
This patch makes it possible to pass custom struct attribute_group array
via the pmbus_driver_info struct so that those can be added to the
attribute groups passed to hwmon_device_register_with_groups().

This makes it possible to register custom sysfs attributes by PMBUS
drivers similar to how you can do this with most other busses/classes.

Signed-off-by: Krzysztof Adamski &lt;krzysztof.adamski@nokia.com&gt;
Signed-off-by: Guenter Roeck &lt;linux@roeck-us.net&gt;
Signed-off-by: Andrew Jeffery &lt;andrew@aj.id.au&gt;
</content>
</entry>
</feed>
