-
-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Include second CPU in DT #101
Include second CPU in DT #101
Conversation
c3bde9f
to
d5268a4
Compare
bb66b33
to
14f65d9
Compare
d5268a4
to
6cab1de
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some of this is changed in #106. It seems there is much more that have to be generated by code than initially expected.
sensor@13 { | ||
compatible = "ibm,ipmi-sensor"; | ||
ipmi-sensor-type = <0x0c>; | ||
reg = <0x13>; | ||
}; | ||
|
||
sensor@15 { | ||
compatible = "ibm,ipmi-sensor"; | ||
ipmi-sensor-type = <0x0c>; | ||
reg = <0x15>; | ||
}; | ||
|
||
sensor@19 { | ||
compatible = "ibm,ipmi-sensor"; | ||
ipmi-sensor-type = <0x0c>; | ||
reg = <0x19>; | ||
}; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These are all memory
sensors, seems there is one per installed DIMM and there is one reg
reserved per unpopulated slot. These also have to be generated by code, depending on actual setup. It may require passing data from romstage, maybe worth exposing whole SPD (related issue), since Hostboot does it?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not sure if SPD plays a role in this. At the moment I suspect that sensors are selected based on HUID (I think I saw it in the code) while all possible values are simply hard-coded in talos.xml
. But HUID might depend on SPD data.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
SPD data isn't necessary, it's about position of DIMM, but I made whole mem_data
available in ramstage, so now it's possible to generate memory and SPD nodes there.
Assumption is that it can still work for one CPU. Change-Id: Ic8612b747a8036c6bb6711dc05d36515ea190346 Signed-off-by: Sergii Dmytruk <sergii.dmytruk@3mdeb.com>
Change-Id: Ib1c8831c792ccce61925408ea19fddca682b476e Signed-off-by: Sergii Dmytruk <sergii.dmytruk@3mdeb.com>
Change-Id: I51915169640631ab9406202ea3112044aec07dd7 Signed-off-by: Sergii Dmytruk <sergii.dmytruk@3mdeb.com>
Put validation into a separate function. Change-Id: Ie04da44b1beb6010afe8cda527340e5d234cc4e1 Signed-off-by: Sergii Dmytruk <sergii.dmytruk@3mdeb.com>
6cab1de
to
d6010ce
Compare
Change-Id: I58f9204eee786f9bda1e14ffa2992a75f4b773a5 Signed-off-by: Sergii Dmytruk <sergii.dmytruk@3mdeb.com>
It's needed as a source of information for building device tree. Change-Id: I306d384186c4677452d531d490cde495b1129204 Signed-off-by: Sergii Dmytruk <sergii.dmytruk@3mdeb.com>
Two nodes per installed DIMM: state (presence) and temperature sensors. Change-Id: I297c4820679491699fcdfea173d6fbd01eddbe75 Signed-off-by: Sergii Dmytruk <sergii.dmytruk@3mdeb.com>
34068fb
to
487d707
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
cbmem_entry_add()
over-allocates memory, but this is a tradeoff between speed, readability and memory footprint. We may add field specifying number of functional DIMMs to mem_data
later if reclaiming those 8K or so will be necessary.
No description provided.