fit: Check all compat strings for highest match

The compat string matching code was mostly copied from depthcharge. One
of the few differences is that we now store the list of compat strings
we're willing to match in a list rather than an array. Since our lists
insert at the front, that means the strings are now ordered lowest to
highest (not highest to lowest like in depthcharge).

We did rewrite the compat_rank matching code to accomodate for that...
however, what we didn't do is remove the break-statement in the loop
that matches all compat strings. When we search the lowest priority
first, we can't abort the search as soon as we found a match -- we have
to keep looking because we might find a higher priority match later.

This patch fixes the issue so that my Kevin can actually match for
google,kevin-rev5 (and doesn't just jump at the first best google,kevin
match).

Change-Id: Ibe3d84bbce6de3cd49c746a667ae1ccfdc843105
Signed-off-by: Julius Werner <jwerner@chromium.org>
Reviewed-on: https://review.coreboot.org/c/coreboot/+/32874
Reviewed-by: Hung-Te Lin <hungte@chromium.org>
Tested-by: build bot (Jenkins) <no-reply@coreboot.org>

1 files changed, 0 insertions, 1 deletions

diff --git a/src/lib/fit.c b/src/lib/fit.c
index 6ac0a8917e..37dfc8de98 100644
--- a/src/lib/fit.c
+++ b/src/lib/fit.c
@@ -463,7 +463,6 @@ static int fit_update_compat(struct fit_config_node *config)
 			config->compat_rank = i;
 			config->compat_string =
 				compat_node->compat_string;
-			break;
 		}
 		i++;
 	}