mb/google/hatch/var/jinlon: Ensure LCD backlight controls generated

Jinlon disables the eps device if no privacy screen is present, so add
a second generic gfx device 'no_eps' to handle that case, so that ACPI
backlight controls are generated either way. Add logic to ensure only
one of the two devices is active.

TEST=build/boot Win11 on google/hatch (jinlon), ensure LCD backlight
controls present and functional on device both with and without a
privacy screen.

Change-Id: Icf20de97d26c8be76c84e87d5dc6ed1a4b6dbfbc
Signed-off-by: Matt DeVillier <matt.devillier@gmail.com>
Reviewed-on: https://review.coreboot.org/c/coreboot/+/80178
Reviewed-by: Felix Singer <service+coreboot-gerrit@felixsinger.de>
Reviewed-by: Eric Lai <ericllai@google.com>
Tested-by: build bot (Jenkins) <no-reply@coreboot.org>

1 files changed, 2 insertions, 0 deletions

diff --git a/src/mainboard/google/hatch/variants/jinlon/mainboard.c b/src/mainboard/google/hatch/variants/jinlon/mainboard.c
index 51ef3465eb..009a6ad239 100644
--- a/src/mainboard/google/hatch/variants/jinlon/mainboard.c
+++ b/src/mainboard/google/hatch/variants/jinlon/mainboard.c
@@ -21,9 +21,11 @@ static bool eps_sku(uint32_t sku_id)
 static void check_for_eps(uint32_t sku_id)
 {
 	struct device *eps_dev = DEV_PTR(eps);
+	struct device *no_eps_dev = DEV_PTR(no_eps);
 
 	if (eps_sku(sku_id)) {
 		printk(BIOS_INFO, "SKU ID %u has EPS\n", sku_id);
+		no_eps_dev->enabled = 0;
 		return;
 	}