From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <stable-owner@vger.kernel.org>
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 97B0DC54EBE
	for <stable@archiver.kernel.org>; Mon, 16 Jan 2023 15:09:22 +0000 (UTC)
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S229529AbjAPPJV (ORCPT <rfc822;stable@archiver.kernel.org>);
        Mon, 16 Jan 2023 10:09:21 -0500
Received: from lindbergh.monkeyblade.net ([23.128.96.19]:35262 "EHLO
        lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S232704AbjAPPIS (ORCPT
        <rfc822;stable@vger.kernel.org>); Mon, 16 Jan 2023 10:08:18 -0500
Received: from ams.source.kernel.org (ams.source.kernel.org [IPv6:2604:1380:4601:e00::1])
        by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 77C9124499
        for <stable@vger.kernel.org>; Mon, 16 Jan 2023 06:55:40 -0800 (PST)
Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140])
        (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
        (No client certificate requested)
        by ams.source.kernel.org (Postfix) with ESMTPS id D7B35B80E37
        for <stable@vger.kernel.org>; Mon, 16 Jan 2023 14:55:38 +0000 (UTC)
Received: by smtp.kernel.org (Postfix) with ESMTPSA id 42061C433EF;
        Mon, 16 Jan 2023 14:55:37 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org;
        s=korg; t=1673880937;
        bh=a7mfhxs1IJ0qgmwTpBDjG1aCLSn1vMu4iLKAxbhH+3w=;
        h=Date:From:To:Cc:Subject:References:In-Reply-To:From;
        b=x2YFFVoOosuhZ9vWuovYOQrvC4yROXFK0RGh3SsLMw1EfHb51YlOIbiGSwyVt4/rK
         DuAxCt/WxkJy+OGQQ0jCPAY3bhHwgq0/NQa2tRwFuraLg5yZ/TgY1oUegnjMd1qI3+
         Fw6wdfAxpDu1wAcoavJZVA8Sm7UT1D7j6KZLYvVQ=
Date:   Mon, 16 Jan 2023 15:55:35 +0100
From:   Greg KH <gregkh@linuxfoundation.org>
To:     "Limonciello, Mario" <Mario.Limonciello@amd.com>
Cc:     "stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: Backport a patch to enable debugging GPIO issues
Message-ID: <Y8VlZ2giazTooakQ@kroah.com>
References: <MN0PR12MB61014D5E4750F45AFD3F26F9E2C19@MN0PR12MB6101.namprd12.prod.outlook.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <MN0PR12MB61014D5E4750F45AFD3F26F9E2C19@MN0PR12MB6101.namprd12.prod.outlook.com>
Precedence: bulk
List-ID: <stable.vger.kernel.org>
X-Mailing-List: stable@vger.kernel.org

On Mon, Jan 16, 2023 at 02:24:17PM +0000, Limonciello, Mario wrote:
> [Public]
> 
> Hi,
> 
> A patch was introduced into 6.2 that will allow outputting what GPIO is active at a given time for pinctrl-amd with dynamic debugging.  This patch is useful particularly for debugging the wakeup source when it says that it's the GPIO controller.
> I've asked at least 4 people to apply it on 6.1.y kernels and turn on those statements in /sys/kernel/debug/dynamic_debug/control to debug issues of spurious wakeups which has me realizing it would make sense to just generally being in 6.1.y.
> 
> Would you please cherry-pick this commit?
> 
> 1d66e379731f ("pinctrl: amd: Add dynamic debugging for active GPIOs")

Now queued up, thanks.

greg k-h