drivers: hwinfo: implemented hardware info support for Smartbond #64125
Conversation
zephyrbot
added
platform: Renesas SmartBond
kasjer
force-pushed
the
kasjer/da1469x-hwinfo
branch
from
e89b7cb
to
fa87c66
Compare
|
This pull request has been marked as stale because it has been open (more than) 60 days with no activity. Remove the stale label or add a comment saying that you would like to have the label removed otherwise this pull request will automatically be closed in 14 days. Note, that you can always re-open a closed pull request at any time. |
|
It's hard to make anyone here to review things, let's prolong for another 60 days. |
kasjer
force-pushed
the
kasjer/da1469x-hwinfo
branch
from
fa87c66
to
0216019
Compare
|
@kasjer thanks for the quick fixes. Were you able to test on HW? |
|
@kasjer are there boards in the tree where you could add the hwinfo as supported features? |
|
@alexanderwachter I tested it on da1469x_dk_pro, could you give me a hint on how add supported feature (I'm very new to zephyr) |
|
Just add - hwinfo here: |
Only reset cause is supported as there is no common unique id present on those chips. Unique ID can be put in OTP but there is no single specification for this. Signed-off-by: Jerzy Kasenberg <jerzy.kasenberg@codecoup.pl>
kasjer
force-pushed
the
kasjer/da1469x-hwinfo
branch
from
0216019
to
22b92e6
Compare
|
@alexanderwachter I added hwinfo feature to both boards. I had to rebase branch to include da14695_dk_usb board though so force-pushed changes may look unrelated |
No problem I added this because I really needed to know reset cause in work on other PR so there was no rush, thanks for review and for your help with polishing things. |
Only reset cause is supported as there is no common unique id present on those chips.
Unique ID can be put in OTP but there is no single specification for this.