<feed xmlns='http://www.w3.org/2005/Atom'>
<title>talos-skiboot/hdata/test, branch master</title>
<subtitle>Talos™ II skiboot sources</subtitle>
<id>https://git.raptorcs.com/git/talos-skiboot/atom?h=master</id>
<link rel='self' href='https://git.raptorcs.com/git/talos-skiboot/atom?h=master'/>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/talos-skiboot/'/>
<updated>2018-04-30T06:11:07+00:00</updated>
<entry>
<title>hdat_to_dt: hash_prop the same on all platforms</title>
<updated>2018-04-30T06:11:07+00:00</updated>
<author>
<name>Stewart Smith</name>
<email>stewart@linux.ibm.com</email>
</author>
<published>2018-04-19T05:46:49+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/talos-skiboot/commit/?id=c90fb6cd796e0ca8c2fcffef8d1f8a8e6245b8ae'/>
<id>urn:sha1:c90fb6cd796e0ca8c2fcffef8d1f8a8e6245b8ae</id>
<content type='text'>
Signed-off-by: Stewart Smith &lt;stewart@linux.ibm.com&gt;
</content>
</entry>
<entry>
<title>hdata: Fix DIMM size property</title>
<updated>2018-04-23T05:02:43+00:00</updated>
<author>
<name>Vasant Hegde</name>
<email>hegdevasant@linux.vnet.ibm.com</email>
</author>
<published>2018-04-12T14:22:19+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/talos-skiboot/commit/?id=c4a094a7df80463408d7a9144377584245364fc5'/>
<id>urn:sha1:c4a094a7df80463408d7a9144377584245364fc5</id>
<content type='text'>
Today we parse vpd blob to get DIMM size information. This is limited
to FSP based system. HDAT provides DIMM size value. Lets use that to
populate device tree. So that we can get size information on BMC based
system as well.

Signed-off-by: Vasant Hegde &lt;hegdevasant@linux.vnet.ibm.com&gt;
CC: Oliver O'Halloran &lt;oohall@gmail.com&gt;
Signed-off-by: Stewart Smith &lt;stewart@linux.ibm.com&gt;
</content>
</entry>
<entry>
<title>hdata/spira: parse vpd to add part-number and serial-number to xscom@ node</title>
<updated>2018-04-11T22:59:57+00:00</updated>
<author>
<name>Stewart Smith</name>
<email>stewart@linux.vnet.ibm.com</email>
</author>
<published>2018-04-06T05:16:45+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/talos-skiboot/commit/?id=086f3277bc3f50afe07f6ab07562ba422fc5baab'/>
<id>urn:sha1:086f3277bc3f50afe07f6ab07562ba422fc5baab</id>
<content type='text'>
Expected by FWTS and associates our processor with the part/serial
number, which is obviously a good thing for one's own sanity.

Signed-off-by: Stewart Smith &lt;stewart@linux.vnet.ibm.com&gt;
Reviewed-by: Vasant Hegde &lt;hegdevasant@linux.vnet.ibm.com&gt;
Signed-off-by: Stewart Smith &lt;stewart@linux.ibm.com&gt;
</content>
</entry>
<entry>
<title>hdata/vpd: Fix DTC warnings</title>
<updated>2018-01-15T04:38:55+00:00</updated>
<author>
<name>Oliver O'Halloran</name>
<email>oohall@gmail.com</email>
</author>
<published>2018-01-12T04:56:22+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/talos-skiboot/commit/?id=ff8b83c06c26a3f1a03be24269a7fd7dc4ec8026'/>
<id>urn:sha1:ff8b83c06c26a3f1a03be24269a7fd7dc4ec8026</id>
<content type='text'>
All the nodes under the vpd heirachy have a unit address (their SLCA
index) but no reg properties. Add them and their size/address cells
to squash the warnings.

Signed-off-by: Oliver O'Halloran &lt;oohall@gmail.com&gt;
Signed-off-by: Stewart Smith &lt;stewart@linux.vnet.ibm.com&gt;
</content>
</entry>
<entry>
<title>lock: Add additional lock auditing code</title>
<updated>2017-12-21T04:15:36+00:00</updated>
<author>
<name>Benjamin Herrenschmidt</name>
<email>benh@kernel.crashing.org</email>
</author>
<published>2017-12-20T02:16:23+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/talos-skiboot/commit/?id=76d9bcdca58936d761458f8f05960239c4dd8dec'/>
<id>urn:sha1:76d9bcdca58936d761458f8f05960239c4dd8dec</id>
<content type='text'>
Keep track of lock owner name and replace lock_depth counter
with a per-cpu list of locks held by the cpu.

This allows us to print the actual locks held in case we hit
the (in)famous message about opal_pollers being run with a
lock held.

It also allows us to warn (and drop them) if locks are still
held when returning to the OS or completing a scheduled job.

Signed-off-by: Benjamin Herrenschmidt &lt;benh@kernel.crashing.org&gt;
Reviewed-by: Nicholas Piggin &lt;npiggin@gmail.com&gt;
[stewart: fix unit tests]
Signed-off-by: Stewart Smith &lt;stewart@linux.vnet.ibm.com&gt;
</content>
</entry>
<entry>
<title>hdata/tpmrel.c: add firmware event log info to the tpm node</title>
<updated>2017-12-19T03:30:57+00:00</updated>
<author>
<name>Claudio Carvalho</name>
<email>cclaudio@linux.vnet.ibm.com</email>
</author>
<published>2017-12-09T04:52:30+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/talos-skiboot/commit/?id=7da364fd3646013166b90baf26fc55078a446a21'/>
<id>urn:sha1:7da364fd3646013166b90baf26fc55078a446a21</id>
<content type='text'>
This parses the firmware event log information from the
secureboot_tpm_info HDAT structure and add it to the tpm device tree
node.

There can be multiple secureboot_tpm_info entries with each entry
corresponding to a master processor that has a tpm device, however,
multiple tpm is not supported.

Signed-off-by: Claudio Carvalho &lt;cclaudio@linux.vnet.ibm.com&gt;
Signed-off-by: Stewart Smith &lt;stewart@linux.vnet.ibm.com&gt;
</content>
</entry>
<entry>
<title>hdata: Add memory hierarchy under xscom node</title>
<updated>2017-12-18T23:58:32+00:00</updated>
<author>
<name>Vasant Hegde</name>
<email>hegdevasant@linux.vnet.ibm.com</email>
</author>
<published>2017-10-13T11:21:18+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/talos-skiboot/commit/?id=5110b54067c0db11122ab9a57dd2dcc56f026581'/>
<id>urn:sha1:5110b54067c0db11122ab9a57dd2dcc56f026581</id>
<content type='text'>
We have memory to chip mapping but doesn't have complete memory hierarchy.
This patch adds memory hierarchy under xscom node. This is specific to
P9 system as these hierarchy may change between processor generation.

It uses memory controller ID details and populates nodes like:
  xscom@&lt;addr&gt;/mcbist@&lt;mcbist_id&gt;/mcs@&lt;mcs_id&gt;/mca@&lt;mca_id&gt;/dimm@&lt;resource_id&gt;

Also this patch adds few properties under dimm node.
Finally make sure xscom nodes created before calling memory_parse().

Signed-off-by: Vasant Hegde &lt;hegdevasant@linux.vnet.ibm.com&gt;
Signed-off-by: Stewart Smith &lt;stewart@linux.vnet.ibm.com&gt;
</content>
</entry>
<entry>
<title>make check: Make valgrind optional</title>
<updated>2017-12-18T23:58:32+00:00</updated>
<author>
<name>Michael Ellerman</name>
<email>mpe@ellerman.id.au</email>
</author>
<published>2017-11-22T12:15:50+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/talos-skiboot/commit/?id=427cc73b1eab4b4512fbaf623f9a120c6afdf09f'/>
<id>urn:sha1:427cc73b1eab4b4512fbaf623f9a120c6afdf09f</id>
<content type='text'>
To (slightly) lower the barrier for contributions, we can make valgrind
optional with just a small amount of plumbing.

This allows make check to run successfully without valgrind.

Signed-off-by: Michael Ellerman &lt;mpe@ellerman.id.au&gt;
Signed-off-by: Stewart Smith &lt;stewart@linux.vnet.ibm.com&gt;
</content>
</entry>
<entry>
<title>hdata: Add location code property to xscom node</title>
<updated>2017-12-14T04:04:58+00:00</updated>
<author>
<name>Vasant Hegde</name>
<email>hegdevasant@linux.vnet.ibm.com</email>
</author>
<published>2017-12-13T05:23:56+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/talos-skiboot/commit/?id=eaf9e0f0981b30bf1667fb6b7532555d9c7444f5'/>
<id>urn:sha1:eaf9e0f0981b30bf1667fb6b7532555d9c7444f5</id>
<content type='text'>
This patch adds chip location code property to xscom node.

Signed-off-by: Vasant Hegde &lt;hegdevasant@linux.vnet.ibm.com&gt;
Signed-off-by: Mahesh Salgaonkar &lt;mahesh@linux.vnet.ibm.com&gt;
Signed-off-by: Stewart Smith &lt;stewart@linux.vnet.ibm.com&gt;
</content>
</entry>
<entry>
<title>hdata/vpd: Rework vpd node creation logic</title>
<updated>2017-10-17T02:51:28+00:00</updated>
<author>
<name>Vasant Hegde</name>
<email>hegdevasant@linux.vnet.ibm.com</email>
</author>
<published>2017-10-10T05:40:17+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/talos-skiboot/commit/?id=77190aa7d40dde305a598fa36810db0f5598c553'/>
<id>urn:sha1:77190aa7d40dde305a598fa36810db0f5598c553</id>
<content type='text'>
Presently we traverse SLCA structure to create various FRU nodes under /vpd
node. We assumed that children are always contiguous. It happened to be
contiguous in P8 and worked fine, but failed in P9 system. So it ended up
populating duplicate node under wrong parent. Also failed to populate some
of the nodes.

Unfortunately there is no way to reach all the children of a given parent
from parent node :-( Hence we have to rework vpd creation logic.

This patch goes through all the SLCA entries serially and creates vpd node.
Assumptions:
  - SLCA index is always serial (0..n)
  - When we traverse serially parent entry comes before child
  - Redundant resources are always consecutive
  - Populate node if SLCA has 'installed' and 'VPD collected' bit set

CC: Ananth N Mavinakayanahalli &lt;ananth@linux.vnet.ibm.com&gt;
Signed-off-by: Vasant Hegde &lt;hegdevasant@linux.vnet.ibm.com&gt;
Reviewed-by: Oliver O'Halloran &lt;oohall@gmail.com&gt;
Signed-off-by: Stewart Smith &lt;stewart@linux.vnet.ibm.com&gt;
</content>
</entry>
</feed>
