From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from layka.disroot.org (layka.disroot.org [178.21.23.139]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 3449C390C9F; Wed, 17 Jun 2026 08:52:59 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=178.21.23.139 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1781686381; cv=none; b=fUptVY3SlBhSMiO5YFn30tMvSAutKd74D4668PG6E45IN0oD9OJ2wNluGSwxviFXVR3jMOR/u4euNbpxUkQqDfzmMiGlp+5VCSEkpQxKarHk2Hxp+Zq61f6H7sOjOVixpFYlCcCgZB7KURLpmrR/VCaADjbHOXa+ttF3cjMWaw0= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1781686381; c=relaxed/simple; bh=SBhFBik6Q8jsMrDc/brKC2mrnipQabc3lq2zmQMLUtk=; h=From:To:Cc:Subject:Date:Message-ID:In-Reply-To:References: MIME-Version:Content-Type; b=ZQUX5+CTVpZ1wDTVIevOsHG1EQYey00Qwt+0RXjatG+rOGAdDmFZ3P/p5e7WciazXMixvFPF2sscXrR1YfS7VDnydA/myaYjq/45PjnAg//L2v3wf6XjHI2nFI3TX6jmleJbHT1oCi9nhmCaokevMWvJ09UVhNHf5DkWhJuk3cE= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=reject dis=none) header.from=disroot.org; spf=pass smtp.mailfrom=disroot.org; dkim=pass (2048-bit key) header.d=disroot.org header.i=@disroot.org header.b=lSrTmpu7; arc=none smtp.client-ip=178.21.23.139 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=reject dis=none) header.from=disroot.org Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=disroot.org Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=disroot.org header.i=@disroot.org header.b="lSrTmpu7" Received: from mail01.disroot.lan (localhost [127.0.0.1]) by disroot.org (Postfix) with ESMTP id B1B8D2758C; Wed, 17 Jun 2026 10:52:57 +0200 (CEST) X-Virus-Scanned: SPAM Filter at disroot.org Received: from layka.disroot.org ([127.0.0.1]) by localhost (disroot.org [127.0.0.1]) (amavis, port 10024) with ESMTP id xQkLN9fSq7zN; Wed, 17 Jun 2026 10:52:57 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=disroot.org; s=mail; t=1781686377; bh=SBhFBik6Q8jsMrDc/brKC2mrnipQabc3lq2zmQMLUtk=; h=From:To:Cc:Subject:Date:In-Reply-To:References; b=lSrTmpu7PuxSPHmn9OwmMFrS5dOtRj8mLnAMiVj1rsgaSWOnvFRGDwYxedKXWsOvO Zu3fnY2p1f9s3A3HSQMpRNnkf0mEkfnGOZv0VkM2AVHvSJYmH7BhN1/GD/zhHFJPWh uzAadVO/zlTPlHLgNVG/ZTAnvGaWzCgeeckp+yYGHM5pndUhoZcafAobe6GPjfBHun BvfxGVPB1O7t29agp+6OpFR84hiApkb3C80avWvLo+8iP3nmjadrFgmUlWIOLGnBlU KBS0tjkpZI3x+h28lJTZ/6+rJ04Ibc/V6e/kaesMUQOvkEZ1sofw8afOYGvubxB2au UxErZbVtjUCNw== From: Marco Scardovi To: Andy Shevchenko Cc: Mika Westerberg , Mika Westerberg , Linus Walleij , Bartosz Golaszewski , Mario Limonciello , linux-gpio@vger.kernel.org, linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] gpiolib: acpi: Add quirk for ASUS ROG Strix G614 series Date: Wed, 17 Jun 2026 10:52:35 +0200 Message-ID: In-Reply-To: References: <20260616090824.5967-1-scardracs@disroot.org> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="utf-8" > > Okay, perhaps this all needs to be elaborated and summarized in the commit > message. > > Sidenote > > Personally I'd wait for Mario for further info: after all it's him the > > maintainer for AMD side and surely knows more than me. > > Sure, I am with you on this. > What I'm saying below is purely based on my own speculations but it's the most plausible thing I can think as for now. When I tested Mario's patch back in April it totally used to work on my device: I have an idea that the value probably happened to be equal 1, like requested on the patch and making it working as intended. In the meantime I updated the BIOS (from 310 to 315, released in May), changing the value from 1 to 0 and breaking the boot time again (as said it's my own speculation, I'm not sure if it is actually possible). I didn't test the patch after the BIOS update 'cause I had the gpiolib_acpi.run_edge_events_on_boot=0 option enabled and didn't think it would stop working again.