<feed xmlns='http://www.w3.org/2005/Atom'>
<title>BMC/Intel-BMC/linux.git/drivers/hwmon, branch dev-4.17</title>
<subtitle>Intel OpenBMC Linux kernel source tree (mirror)</subtitle>
<id>https://git.radix-linux.su/BMC/Intel-BMC/linux.git/atom?h=dev-4.17</id>
<link rel='self' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/atom?h=dev-4.17'/>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/'/>
<updated>2018-07-05T01:41:27+00:00</updated>
<entry>
<title>Merge tag 'v4.17.4' into dev-4.17</title>
<updated>2018-07-05T01:41:27+00:00</updated>
<author>
<name>Joel Stanley</name>
<email>joel@jms.id.au</email>
</author>
<published>2018-07-05T01:41:23+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/commit/?id=8fb9a0714f8ff91756a9746707c4f884b3745a40'/>
<id>urn:sha1:8fb9a0714f8ff91756a9746707c4f884b3745a40</id>
<content type='text'>
This is the 4.17.4 stable release

Signed-off-by: Joel Stanley &lt;joel@jms.id.au&gt;
</content>
</entry>
<entry>
<title>hwmon: (k10temp) Add support for Stoney Ridge and Bristol Ridge CPUs</title>
<updated>2018-07-03T09:26:46+00:00</updated>
<author>
<name>Guenter Roeck</name>
<email>linux@roeck-us.net</email>
</author>
<published>2018-04-29T16:16:45+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/commit/?id=bfef6597752eb8f7b14c2c464121f0085ce80057'/>
<id>urn:sha1:bfef6597752eb8f7b14c2c464121f0085ce80057</id>
<content type='text'>
commit ccaf63b4d6eaf3447037cefbb0b1038fa80c6639 upstream.

Add support for Stoney Ridge and Bristol Ridge (Family 15h Model 0x70)
CPUs. Registers match those of Family 15h Model 0x60.

Cc: stable@vger.kernel.org # v4.16+
Tested-by: Gabriel Craciunescu &lt;nix.or.die@gmail.com&gt;
Signed-off-by: Guenter Roeck &lt;linux@roeck-us.net&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>hwmon: Add On-Chip Controller (OCC) hwmon driver</title>
<updated>2018-06-19T03:05:38+00:00</updated>
<author>
<name>Edward A. James</name>
<email>eajames@us.ibm.com</email>
</author>
<published>2017-11-20T23:53:34+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/commit/?id=5f96180350afeb12e5f7d22e8cbb27a4ffaf14a4'/>
<id>urn:sha1:5f96180350afeb12e5f7d22e8cbb27a4ffaf14a4</id>
<content type='text'>
The OCC is a device embedded on a POWER processor that collects and
aggregates sensor data from the processor and system. The OCC can
provide the raw sensor data as well as perform thermal and power
management on the system.

This driver provides a hwmon interface to the OCC from a service
processor (e.g. a BMC). The driver supports both POWER8 and POWER9 OCCs.
Communications with the POWER8 OCC are established over standard I2C
bus. The driver communicates with the POWER9 OCC through the FSI-based
OCC driver, which handles the lower-level communication details.

OpenBMC-Staging-Count: 3
Signed-off-by: Edward A. James &lt;eajames@us.ibm.com&gt;
Signed-off-by: Benjamin Herrenschmidt &lt;benh@kernel.crashing.org&gt;
Signed-off-by: Joel Stanley &lt;joel@jms.id.au&gt;
</content>
</entry>
<entry>
<title>pmbus (max31785): Wrap all I2C accessors in one-shot failure handlers</title>
<updated>2018-06-19T03:05:38+00:00</updated>
<author>
<name>Andrew Jeffery</name>
<email>andrew@aj.id.au</email>
</author>
<published>2018-04-03T14:26:55+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/commit/?id=f2b9537ac6bb116c4e79bf043d2735d1fb0a7916'/>
<id>urn:sha1:f2b9537ac6bb116c4e79bf043d2735d1fb0a7916</id>
<content type='text'>
The MAX31785(A) has shown erratic behaviour across multiple system
designs, unexpectedly clock stretching and NAKing transactions. Perform
a one-shot retry if necessary for all access attempts.

OpenBMC-Staging-Count: 3
Signed-off-by: Andrew Jeffery &lt;andrew@aj.id.au&gt;
Tested-by: George Keishing &lt;gkeishin@in.ibm.com&gt;
</content>
</entry>
<entry>
<title>pmbus (core): Use driver callbacks in pmbus_get_fan_rate()</title>
<updated>2018-06-19T03:05:38+00:00</updated>
<author>
<name>Andrew Jeffery</name>
<email>andrew@aj.id.au</email>
</author>
<published>2018-04-03T14:26:54+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/commit/?id=6c790b22420404f216324e5894177d8e527fa76e'/>
<id>urn:sha1:6c790b22420404f216324e5894177d8e527fa76e</id>
<content type='text'>
The driver may have overridden the pmbus_read_byte_data() callback, so
make sure we use that to achieve expected behaviour.

This helps in the MAX31785 case where we may need to perform a one-shot
retry of transfers in the face of a failure.

OpenBMC-Staging-Count: 3
Signed-off-by: Andrew Jeffery &lt;andrew@aj.id.au&gt;
Reviewed-by: Eddie James &lt;eajames@linux.vnet.ibm.com&gt;
Tested-by: George Keishing &lt;gkeishin@in.ibm.com&gt;
</content>
</entry>
<entry>
<title>pmbus (core): One-shot retries for failure to set page</title>
<updated>2018-06-19T03:05:38+00:00</updated>
<author>
<name>Andrew Jeffery</name>
<email>andrew@aj.id.au</email>
</author>
<published>2018-04-03T14:26:53+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/commit/?id=19576917bac8ce3ae382f393f35c78dfdb09e95f'/>
<id>urn:sha1:19576917bac8ce3ae382f393f35c78dfdb09e95f</id>
<content type='text'>
Work around the shonky behaviour seen with the MAX31785 where we fail
to set the page register in some circumstances.

There's no real elegant way to do this. We can propagate the error up,
but that forces us to retry the operation way up the call tree in any
number of places. It also forces callers to split out pmbus_set_page()
from the pmbus_{read,write}_{byte,word}_data() functions in order to
differentiate between a failure to set the page and a failure to read a
register (that might not exist, in which case an error is anticiptated).

OpenBMC-Staging-Count: 3
Cc: Eddie James &lt;eajames@linux.vnet.ibm.com&gt;
Cc: Matt Spinler &lt;mspinler@linux.vnet.ibm.com&gt;
Signed-off-by: Andrew Jeffery &lt;andrew@aj.id.au&gt;
Reviewed-by: Eddie James &lt;eajames@linux.vnet.ibm.com&gt;
Tested-by: George Keishing &lt;gkeishin@in.ibm.com&gt;
</content>
</entry>
<entry>
<title>pmbus (max31785): Add support for devicetree configuration</title>
<updated>2018-06-19T03:05:38+00:00</updated>
<author>
<name>Andrew Jeffery</name>
<email>andrew@aj.id.au</email>
</author>
<published>2018-04-03T14:26:52+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/commit/?id=ecf485012a62f6a369847e60988eeb3497a75d01'/>
<id>urn:sha1:ecf485012a62f6a369847e60988eeb3497a75d01</id>
<content type='text'>
OpenBMC-Staging-Count: 3
Signed-off-by: Andrew Jeffery &lt;andrew@aj.id.au&gt;
Tested-by: George Keishing &lt;gkeishin@in.ibm.com&gt;
</content>
</entry>
<entry>
<title>hwmon: (k10temp) Use API function to access System Management Network</title>
<updated>2018-05-13T16:00:49+00:00</updated>
<author>
<name>Guenter Roeck</name>
<email>linux@roeck-us.net</email>
</author>
<published>2018-05-04T20:01:33+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/commit/?id=3b031622f598481970400519bd5abc2a16708282'/>
<id>urn:sha1:3b031622f598481970400519bd5abc2a16708282</id>
<content type='text'>
The SMN (System Management Network) on Family 17h AMD CPUs is also accessed
from other drivers, specifically EDAC. Accessing it directly is racy.
On top of that, accessing the SMN through root bridge 00:00 is wrong on
multi-die CPUs and may result in reading the temperature from the wrong
die. Use available API functions to fix the problem.

For this to work, add dependency on AMD_NB. Also change the Raven Ridge
PCI device ID to point to Data Fabric Function 3, since this ID is used
by the API functions to find the CPU node.

Cc: stable@vger.kernel.org # v4.16+
Tested-by: Gabriel Craciunescu &lt;nix.or.die@gmail.com&gt;
Signed-off-by: Guenter Roeck &lt;linux@roeck-us.net&gt;
</content>
</entry>
<entry>
<title>hwmon: (k10temp) Fix reading critical temperature register</title>
<updated>2018-04-29T21:21:45+00:00</updated>
<author>
<name>Guenter Roeck</name>
<email>linux@roeck-us.net</email>
</author>
<published>2018-04-29T15:08:24+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/commit/?id=40626a1bf657eef557fcee9e1b8ef5b4f5b56dcd'/>
<id>urn:sha1:40626a1bf657eef557fcee9e1b8ef5b4f5b56dcd</id>
<content type='text'>
The HTC (Hardware Temperature Control) register has moved
for recent chips.

Cc: stable@vger.kernel.org # v4.16+
Tested-by: Gabriel Craciunescu &lt;nix.or.die@gmail.com&gt;
Signed-off-by: Guenter Roeck &lt;linux@roeck-us.net&gt;
</content>
</entry>
<entry>
<title>hwmon: (k10temp) Add support for AMD Ryzen w/ Vega graphics</title>
<updated>2018-04-25T12:31:06+00:00</updated>
<author>
<name>Guenter Roeck</name>
<email>linux@roeck-us.net</email>
</author>
<published>2018-04-24T15:59:45+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/Intel-BMC/linux.git/commit/?id=877d8948d0aa402fbbede138fc73432bb335b65f'/>
<id>urn:sha1:877d8948d0aa402fbbede138fc73432bb335b65f</id>
<content type='text'>
Enable k10temp for AMD Ryzen APUs w/ Vega Mobile Gfx.

Based on patch from René Rebe &lt;rene@exactcode.de&gt;. Dropped temperature
offsets since those are not supposed to apply for the affected CPUs.

Cc: stable@vger.kernel.org # v4.16+
Cc: René Rebe &lt;rene@exactcode.de&gt;
Signed-off-by: Guenter Roeck &lt;linux@roeck-us.net&gt;
</content>
</entry>
</feed>
