From: Greg KH <gregkh@linuxfoundation.org>
To: Rajat Khandelwal <rajat.khandelwal@linux.intel.com>
Cc: heikki.krogerus@linux.intel.com, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] usb: typec: intel_pmc_mux: Expose IOM port status to debugfs
Date: Thu, 30 Mar 2023 13:01:51 +0200 [thread overview]
Message-ID: <ZCVsH2KkfcMA86hJ@kroah.com> (raw)
In-Reply-To: <20230330104821.773053-1-rajat.khandelwal@linux.intel.com>
On Thu, Mar 30, 2023 at 04:18:21PM +0530, Rajat Khandelwal wrote:
> IOM status has a crucial role during debugging to check the
> current state of the type-C port.
> There are ways to fetch the status, but all those require the
> IOM port status offset, which could change with platform.
>
> Make a debugfs directory for intel_pmc_mux and expose the status
> under it per port basis.
>
> Signed-off-by: Rajat Khandelwal <rajat.khandelwal@linux.intel.com>
> Reviewed-by: Heikki Krogerus <heikki.krogerus@linux.intel.com>
> ---
> drivers/usb/typec/mux/intel_pmc_mux.c | 44 +++++++++++++++++++++++++++
> 1 file changed, 44 insertions(+)
>
> diff --git a/drivers/usb/typec/mux/intel_pmc_mux.c b/drivers/usb/typec/mux/intel_pmc_mux.c
> index 34e4188a40ff..c99d20888f5d 100644
> --- a/drivers/usb/typec/mux/intel_pmc_mux.c
> +++ b/drivers/usb/typec/mux/intel_pmc_mux.c
> @@ -15,6 +15,7 @@
> #include <linux/usb/typec_mux.h>
> #include <linux/usb/typec_dp.h>
> #include <linux/usb/typec_tbt.h>
> +#include <linux/debugfs.h>
>
> #include <asm/intel_scu_ipc.h>
>
> @@ -145,6 +146,8 @@ struct pmc_usb {
> u32 iom_port_status_offset;
> };
>
> +static struct dentry *pmc_mux_debugfs_root;
Why not just look up the dentry and delete it when you want it with a
call to debugfs_lookup_and_remove() instead? That way you don't have to
keep it around (hint, pass it back from your call to
pmc_mux_debugfs_init() or better yet, don't even have a
pmc_mux_debugfs_init() function as it only contains one line and is
only called in one place.
This will save you the storage space of this variable if debugfs is not
enabled in your kernel. A small amount, yes, but it's nicer, right?
thanks,
greg k-h
next prev parent reply other threads:[~2023-03-30 11:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-30 10:48 [PATCH] usb: typec: intel_pmc_mux: Expose IOM port status to debugfs Rajat Khandelwal
2023-03-30 11:01 ` Greg KH [this message]
2023-04-04 17:18 ` Rajat Khandelwal
2023-04-04 18:25 ` Greg KH
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=ZCVsH2KkfcMA86hJ@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=rajat.khandelwal@linux.intel.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;
as well as URLs for NNTP newsgroup(s).