Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 89EF9C64EC7 for ; Mon, 13 Feb 2023 18:00:13 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230374AbjBMSAL (ORCPT ); Mon, 13 Feb 2023 13:00:11 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:43766 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230312AbjBMSAH (ORCPT ); Mon, 13 Feb 2023 13:00:07 -0500 Received: from mga02.intel.com (mga02.intel.com [134.134.136.20]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 5EB841F5D3; Mon, 13 Feb 2023 09:59:59 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1676311199; x=1707847199; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=IAYfQxj3OmelMwV5h9UuiFc/JbOUINQ2ZHqpvYayBxI=; b=LkjRrS6gVHzk7TZW3NJsUWstYJ+L56yaXwHReoMFuCc/l6Qb8MOvJtqZ LEfJcCBSJlCs4aXJHTXEljJBi6MTZFbIFe50cpxjwkecppuXhwwWZ6YX1 RBFuP2qcwNRakMa0CU9fcBBp087/euuJBsfk4ep+sPehPtLkqXBIiygYY xPeN87zgSpzvH0Po4ShHHgogSOwak+sCP/RvNuu1l5uGzyR/AkDf/X1/e NtGJV15bV25tPQsJt1lXuCFfLqzbyQp2N1ww6AxIPZ5cN8uIbfTDYF4Ed chciteqTDn2WAgB8o8gzYnCVgGP5XkC3gE8QAQkpKqhPU+PwfdmJ2yVE6 A==; X-IronPort-AV: E=McAfee;i="6500,9779,10620"; a="318975416" X-IronPort-AV: E=Sophos;i="5.97,294,1669104000"; d="scan'208";a="318975416" Received: from orsmga006.jf.intel.com ([10.7.209.51]) by orsmga101.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 13 Feb 2023 09:59:58 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=McAfee;i="6500,9779,10620"; a="646453952" X-IronPort-AV: E=Sophos;i="5.97,294,1669104000"; d="scan'208";a="646453952" Received: from smile.fi.intel.com ([10.237.72.54]) by orsmga006.jf.intel.com with ESMTP; 13 Feb 2023 09:59:55 -0800 Received: from andy by smile.fi.intel.com with local (Exim 4.96) (envelope-from ) id 1pRd7J-006Tlv-1t; Mon, 13 Feb 2023 19:59:53 +0200 Date: Mon, 13 Feb 2023 19:59:53 +0200 From: Andy Shevchenko To: Raul Rangel Cc: Werner Sembach , Mario Limonciello , mika.westerberg@linux.intel.com, linus.walleij@linaro.org, brgl@bgdev.pl, linux-gpio@vger.kernel.org, linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org, Alex Deucher Subject: Re: [PATCH] gpiolib: acpi: Add a ignore wakeup quirk for Clevo NH5xAx Message-ID: References: <20230210164636.628462-1-wse@tuxedocomputers.com> <029b8d80-db28-cdb2-5c39-334be6968fad@tuxedocomputers.com> <86db79fa-5efb-caad-3310-60928907cc58@amd.com> <97026dc5-e92e-62fe-43ae-33533125d900@tuxedocomputers.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Feb 13, 2023 at 07:57:55PM +0200, Andy Shevchenko wrote: > On Mon, Feb 13, 2023 at 07:50:02PM +0200, Andy Shevchenko wrote: > > On Mon, Feb 13, 2023 at 10:20:41AM -0700, Raul Rangel wrote: > > > On Mon, Feb 13, 2023 at 7:47 AM Werner Sembach wrote: > > > > Am 13.02.23 um 15:37 schrieb Andy Shevchenko: ... > > > > Schematics for the NH5xAx can also be found on this unofficial clevo mirror > > > > (service manuals, scroll to end for schematics): > > > > > > > > http://repo.palkeo.com/clevo-mirror/NH5xACx_AFx_ADx/NH50AC.zip > > > > > > > > http://repo.palkeo.com/clevo-mirror/NH5xACx_AFx_ADx/NH50AF1.zip > > > > > > > > User: repo > > > > > > > > PW: repo > > > > > > > > >> The schematics were shared by the reporter for the original issue which is > > > > >> how we reached the conclusion there was a mistake. > > > > >> > > > > >> As they're both Clevo designs it's certainly possible they have the same > > > > >> mistake in two systems. > > > > > > > > Thank you! > > > > > I have looked at the schematics and read discussion. > > > > > > > > > > So, the conclusion that this is a BIOS bug is incorrect in my opinion. > > > > > The problem is either in the PMIC/EC firmware that shouldn't shut down 3.3VS > > > > > signal for a while or on the PCB level, so that pull up should be connected > > > > > to another power source that stays on. > > > > > > > > > > This means the description on the initial patch with the same issue is > > > > > incorrect. > > > > > > > > > > Do we know the power sequence on the suspend to see which and how on the > > > > > time line the power sources are off/on? > > > > > > If you look at the load switch for 3.3VS, its EN2 pin is connected to > > > SUSB#_EN which is connected to SUSB# which is connected to > > > AND(SUSB#_PCH -> SLP_S3_L, PM_SLP_S0 -> S0A3_GPIO). So there is no > > > PMIC/EC firmware that is incharge of this. I guess I'm not quite sure > > > how they have S0A3_GPIO configured, so maybe I have an invert wrong. > > > > > > The EC does control DD_ON which controls the 3.3V and 5V rails. > > > > On page 6 of the schematics I see the U7 that forms SUSB# from SUSB#_APU > > (which corresponds to what you said) _and_ EC_EN, which is GPIO from IT5570, > > which is EC. > > > > Are you using different schematics? I'm using the one from FDO bug report. > > Just checked this one: > http://repo.palkeo.com/clevo-mirror/NH5xACx_AFx_ADx/NH50AC.zip > > Also uses EC (SUSB_EC#). So this all makes me thing that either EC firmware is buggy or we have ACPI EC code in the kernel to fix. -- With Best Regards, Andy Shevchenko