From: Lee Jones <lee@kernel.org>
To: Maria Lisina <sekoohaka.sarisan@gmail.com>
Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
mfd@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5] mfd: intel-lpss: Clean up and modernize DebugFS usage
Date: Wed, 16 Sep 2026 11:27:32 +0100 [thread overview]
Message-ID: <20260916102732.GJ11487@google.com> (raw)
In-Reply-To: <20260916-intel-lpss-debugfs-v5-1-99295f534067@gmail.com>
On Wed, 16 Sep 2026, Maria Lisina wrote:
> The DebugFS API is designed to handle errors gracefully.
> Any explicit checking on return values is considered an anti-pattern.
>
> This patch removes unnecessary error checking and converts
> intel_lpss_debugfs_add() into a void function.
>
> While at it, this patch also clean ups legacy and deprecated usage
> of S_IRUGO macro and debugfs_remove_recursive() function.
>
> Signed-off-by: Maria Lisina <sekoohaka.sarisan@gmail.com>
> ---
> Changes in v5:
> - Changed the goal of the patch to DebugFS modernization.
> - Refactored intel_lpss_debugfs_add() into a void function.
> - Removed deprecated macros and functions.
> - Removed dmesg message completely.
> - Link to v4: https://lore.kernel.org/r/20260914-intel-lpss-debugfs-v4-1-0eb82ea7c1e3@gmail.com
>
> Changes in v4:
> - Keep the dmesg messages, instead check whether DebugFS is initialized
> - Link to v3: https://lore.kernel.org/r/20260913-intel-lpss-debugfs-v3-1-1b8e2b1f0992@gmail.com
>
> Changes in v3:
> - Fixed commit name and description.
> - Link to v2: https://lore.kernel.org/r/20260913-intel-lpss-debugfs-v2-1-a1a4faf5cc63@gmail.com
>
> Changes in v2:
> - Fixed function name in comment section.
> - Link to v1: https://lore.kernel.org/r/20260913-intel-lpss-debugfs-v1-1-833cbb6fffc9@gmail.com
> ---
> drivers/mfd/intel-lpss.c | 28 +++++++++++-----------------
> 1 file changed, 11 insertions(+), 17 deletions(-)
>
> diff --git a/drivers/mfd/intel-lpss.c b/drivers/mfd/intel-lpss.c
> index 63d6694f71457b2e09d238af0a9bfb897a169a64..1a61ef1a62b3e8a2777f357d5c4605d5d57d9532 100644
> --- a/drivers/mfd/intel-lpss.c
> +++ b/drivers/mfd/intel-lpss.c
> @@ -142,28 +142,25 @@ static void intel_lpss_cache_ltr(struct intel_lpss *lpss)
> lpss->idle_ltr = readl(lpss->priv + LPSS_PRIV_IDLELTR);
> }
>
> -static int intel_lpss_debugfs_add(struct intel_lpss *lpss)
> +static void intel_lpss_debugfs_add(struct intel_lpss *lpss)
> {
> - struct dentry *dir;
> -
> - dir = debugfs_create_dir(dev_name(lpss->dev), intel_lpss_debugfs);
> - if (IS_ERR(dir))
> - return PTR_ERR(dir);
> + lpss->debugfs =
> + debugfs_create_dir(dev_name(lpss->dev), intel_lpss_debugfs);
No need to line-wrap for this. Use up to 100-chars to prevent this craziness.
Why continue if this returns an error?
>
> /* Cache the values into lpss structure */
> intel_lpss_cache_ltr(lpss);
>
> - debugfs_create_x32("capabilities", S_IRUGO, dir, &lpss->caps);
> - debugfs_create_x32("active_ltr", S_IRUGO, dir, &lpss->active_ltr);
> - debugfs_create_x32("idle_ltr", S_IRUGO, dir, &lpss->idle_ltr);
> -
> - lpss->debugfs = dir;
> - return 0;
> + debugfs_create_x32("capabilities", 0444, lpss->debugfs,
Does this accept a NULL pointer or an error in parameter 3?
> + &lpss->caps);
You should always align to the '(' but in this case, don't wrap at all.
> + debugfs_create_x32("active_ltr", 0444, lpss->debugfs,
> + &lpss->active_ltr);
> + debugfs_create_x32("idle_ltr", 0444, lpss->debugfs,
> + &lpss->idle_ltr);
> }
>
> static void intel_lpss_debugfs_remove(struct intel_lpss *lpss)
> {
> - debugfs_remove_recursive(lpss->debugfs);
> + debugfs_remove(lpss->debugfs);
Please explain why this is required?
> }
>
> static void intel_lpss_ltr_set(struct device *dev, s32 val)
> @@ -432,10 +429,7 @@ int intel_lpss_probe(struct device *dev,
> goto err_clk_register;
>
> intel_lpss_ltr_expose(lpss);
> -
> - ret = intel_lpss_debugfs_add(lpss);
> - if (ret)
> - dev_warn(dev, "Failed to create debugfs entries\n");
> + intel_lpss_debugfs_add(lpss);
>
> if (intel_lpss_has_idma(lpss)) {
> ret = mfd_add_devices(dev, lpss->devid, &intel_lpss_idma64_cell,
>
> ---
> base-commit: 2f0c1cf72f4682178506f513bbf015e591b1aa4a
> change-id: 20260913-intel-lpss-debugfs-eff3580d1295
>
> Best regards,
> --
> Maria Lisina <sekoohaka.sarisan@gmail.com>
>
--
Lee Jones
next prev parent reply other threads:[~2026-09-16 10:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-15 22:13 Maria Lisina
2026-09-16 7:23 ` Andy Shevchenko
2026-09-16 7:25 ` Andy Shevchenko
2026-09-16 10:27 ` Lee Jones [this message]
2026-09-16 11:01 ` Andy Shevchenko
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260916102732.GJ11487@google.com \
--to=lee@kernel.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mfd@lists.linux.dev \
--cc=sekoohaka.sarisan@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®