[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZGzwCdTO2LptPeQs@surfacebook>
Date: Tue, 23 May 2023 19:55:37 +0300
From: andy.shevchenko@...il.com
To: Mario Limonciello <mario.limonciello@....com>
Cc: 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
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.
Regression 2: See https://stackoverflow.com/a/43957671/2511795
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists