trogdor: Strappings_update_final3.1_second_thisistherealone.patch
Apparently what I thought was lazor-rev2 is actually lazor-rev3 and nobody is really sure what lazor-rev4 is going to be at this point or how we proceed from there. What seems to be somewhat agreed upon is that for now all Lazor revisions use the "old" GPIO mapping and it's not very clear if that's ever going to change for Lazor, so let's take the revision restriction out from Lazor for now. Signed-off-by: Julius Werner <jwerner@chromium.org> Change-Id: I4939ccfd8464da6e72b5e01a58489b8c80f5b4df Reviewed-on: https://review.coreboot.org/c/coreboot/+/45225 Tested-by: build bot (Jenkins) <no-reply@coreboot.org> Reviewed-by: Douglas Anderson <dianders@chromium.org> Reviewed-by: Philip Chen <philipchen@google.com>
This commit is contained in:
parent
b2545cc3c6
commit
8678d47deb
|
@ -16,11 +16,12 @@ uint32_t board_id(void)
|
|||
return id;
|
||||
}
|
||||
|
||||
/* Whether a revision was built before or after the great pin migration of August 2020. */
|
||||
/* Some boards/revisions use one GPIO mapping and others use another. There's no real rhyme or
|
||||
reason to it. Don't try to think about it too much... */
|
||||
static bool use_old_pins(void)
|
||||
{
|
||||
return ((CONFIG(BOARD_GOOGLE_TROGDOR) && board_id() < 2) ||
|
||||
(CONFIG(BOARD_GOOGLE_LAZOR) && board_id() < 3) ||
|
||||
CONFIG(BOARD_GOOGLE_LAZOR) ||
|
||||
(CONFIG(BOARD_GOOGLE_POMPOM) && board_id() < 1));
|
||||
}
|
||||
|
||||
|
|
Loading…
Reference in New Issue