cater for moving ocmb out of proc in device tree - WILL WORK ON THIS IN P11 TIME FRAME - NOW PARKING #85
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
devenrao
force-pushed
the
dtree
branch
7 times, most recently
from
664173c
to
7445f63
Compare
1) As present ocmb is added under proc chip even though ocmb is a chip itself. 2) Moved ocmb out of proc chip as it needs to use its own pib and iic bus 3) cater for moving ocmb out of proc chip in device tree 4) Ensured that ddr4 ocmb targets still use proc pib, fsi bus Tested: i------------kernel pib read----------- PDBG:Translating target addr 0x50001 -> 0x50001 on /proc0/ocmb2 PDBG:pib_read_helper[158]: rc = 0, addr = 0x0000000000050001, data = 0x80c0000200000000, target = /proc0/ocmb2 ody kernel pib read address 0x50001 orig value 0x80c0000200000000 rc =0 -----ocmb ddr5 getscom -------------- get_backend_target FOUND classs sbefifo-ody index = 0x2 ocmb index = 0x2 odyssesy chip ocmb_getscom ocmb index=2 addr= c0002040 orig value 0x4001000a000640 ret 0 -------------cfam------------------------------- PDBG:Translating target addr 0x2804 -> 0x2804 on /hmfsi-ody@810 PDBG:Failed to read from 0x00002810 (0000000000002804) PDBG:fsi_read_helper[314]: rc = 6, addr = 0x02804, data = 0x10000010, target = /hmfsi-ody@810 --------------dump & ffdc----------------------- sucessfully collected dump data len is 20184 sbefifo_op_ody_ffdc_get calling fsi_ody_read PDBG:Translating target addr 0x2809 -> 0x2809 on /hmfsi-ody@110 PDBG:fsi_read_helper[312]: rc = 0, addr = 0x02809, data = 0x9133603f, target = /hmfsi-ody@110 DDR4 system validation 1) IPLed the system and ensured it reached runtime Tested hardeare dump Jan 28 06:04:20 ever6bmc phosphor-dump-manager[12876]: getDump callig sbe_dump Jan 28 06:04:33 ever6bmc phosphor-dump-manager[12876]: dataLen received is 0x00004ED8 /n Jan 28 06:04:33 ever6bmc phosphor-dump-manager[12877]: PDBG Initilization started Signed-off-by: Marri Devender Rao <devenrao@in.ibm.com> Change-Id: Icf9bbee5f5f47659ae005777d21bd8c8bc60ea39
devenrao
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As present ocmb is added under proc chip even though ocmb is a chip itself.
Moved ocmb out of proc chip as it needs to use its own pib and iic bus
cater for moving ocmb out of proc chip in device tree
Ensured that ddr4 ocmb targets still use proc pib, fsi bus
Tested:
i------------kernel pib read-----------
PDBG:Translating target addr 0x50001 -> 0x50001 on /proc0/ocmb2 PDBG:pib_read_helper[158]: rc = 0, addr = 0x0000000000050001, data = 0x80c0000200000000, target = /proc0/ocmb2 ody kernel pib read address 0x50001 orig value 0x80c0000200000000 rc =0
-----ocmb ddr5 getscom --------------
get_backend_target FOUND classs sbefifo-ody index = 0x2 ocmb index = 0x2 odyssesy chip ocmb_getscom ocmb index=2 addr= c0002040 orig value 0x4001000a000640 ret 0
-------------cfam-------------------------------
PDBG:Translating target addr 0x2804 -> 0x2804 on /hmfsi-ody@810 PDBG:Failed to read from 0x00002810 (0000000000002804) PDBG:fsi_read_helper[314]: rc = 6, addr = 0x02804, data = 0x10000010, target = /hmfsi-ody@810
--------------dump & ffdc-----------------------
sucessfully collected dump data len is 20184
sbefifo_op_ody_ffdc_get calling fsi_ody_read
PDBG:Translating target addr 0x2809 -> 0x2809 on /hmfsi-ody@110 PDBG:fsi_read_helper[312]: rc = 0, addr = 0x02809, data = 0x9133603f, target = /hmfsi-ody@110
Change-Id: Icf9bbee5f5f47659ae005777d21bd8c8bc60ea39