[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAJZ5v0hO4hq=TLZ=tK5vXv_pA4SsAo5Gqr5K9g=EU6bFRPYU6g@mail.gmail.com>
Date: Wed, 24 May 2023 20:28:05 +0200
From: "Rafael J. Wysocki" <rafael@...nel.org>
To: andy.shevchenko@...il.com
Cc: Mario Limonciello <mario.limonciello@....com>, rafael@...nel.org,
hdegoede@...hat.com, linus.walleij@...aro.org,
linux-acpi@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-gpio@...r.kernel.org, platform-driver-x86@...r.kernel.org,
linux-pm@...r.kernel.org, Shyam-sundar.S-k@....com,
Basavaraj.Natikar@....com
Subject: Re: [PATCH v2 3/4] pinctrl: amd: Use pm_pr_dbg to show debugging messages
On Tue, May 23, 2023 at 6:55 PM <andy.shevchenko@...il.com> wrote:
>
> Mon, May 22, 2023 at 03:00:32PM -0500, Mario Limonciello kirjoitti:
> > To make the GPIO tracking around suspend easier for end users to
> > use, link it with pm_debug_messages. This will make discovering
> > sources of spurious GPIOs around suspend easier.
>
> Unfortunatelly this has two regressions.
>
> ...
>
> > - dev_dbg(&gpio_dev->pdev->dev,
> > - "GPIO %d is active: 0x%x",
> > - irqnr + i, regval);
> > + pm_pr_dbg("GPIO %d is active: 0x%x",
> > + irqnr + i, regval);
>
> Regression 1: The device is now omitted from the output.
Right.
> Regression 2: See https://stackoverflow.com/a/43957671/2511795
Care to elaborate? I'm not sure what you mean exactly.
Powered by blists - more mailing lists