On 12/30/19 11:22 AM, Daniel Schwierzeck wrote:
Am 30.12.19 um 10:19 schrieb Mauro Condarelli:
I am having problems with this patch.
Problem is "reset"command fails (for my board) with:
=> reset resetting ... ### ERROR ### Please RESET the board ###
I traced down problem to "drivers/sysreset/sysreset-uclass.c" requesting "uclass_first_device(UCLASS_SYSRESET, &dev)", while "drivers/reset/reset-mips.c" defines:
static const struct udevice_id mtmips_reset_ids[] = { { .compatible = "mediatek,mtmips-reset" }, { } };
U_BOOT_DRIVER(mtmips_reset) = { .name = "mtmips-reset", .id = UCLASS_RESET,
... so UCLASS_SYSRESET list is empty.
What am I doing wrong? TiA! Mauro
do you have the according node with compatible string "mediatek,mtmips-reset" in your device-tree?
Yes, I do, but problem is elsewhere: "reset" command looks for a UCLASS_SYSRESET while drivers/reset/reset-mips.c (implementing "mediatek,mtmips-reset") provides a UCLASS_RESET.
I know too little about u-boot internals to understand which one I should "fix" (if any).
Thanks Mauro