From: Greg KH <gregkh@linuxfoundation.org>
To: Venkat Jayaraman <venkat.jayaraman@intel.com>
Cc: linux-usb@vger.kernel.org, pse.type-c.linux@intel.com
Subject: Re: [PATCH v2] usb: typec: ucsi: Add support for READ_POWER_LEVEL command
Date: Mon, 21 Jul 2025 16:35:12 +0200 [thread overview]
Message-ID: <2025072133-mastiff-calorie-c02d@gregkh> (raw)
In-Reply-To: <20250703193259.760717-1-venkat.jayaraman@intel.com>
On Thu, Jul 03, 2025 at 12:32:59PM -0700, Venkat Jayaraman wrote:
> Add support for UCSI READ_POWER_LEVEL command as per
> UCSI specification v2.1 and above to debugfs.
>
> Following power related fields will be exposed as files in debugfs:-
> peak_current (Peak current),
> avg_current (Average current) and
> vbus_voltage (VBUS voltage)
>
> These files will be updated either when a READ_POWER_LEVEL
> command is sent from OS or when a device is connected.
>
> Signed-off-by: Venkat Jayaraman <venkat.jayaraman@intel.com>
> ---
> Changelog v2:
> - Removed extra space in declaration
> - Made the call to debugfs_create_file single line for clarity
>
> drivers/usb/typec/ucsi/debugfs.c | 31 +++++++++++++++++++++++++++++++
> drivers/usb/typec/ucsi/ucsi.c | 16 ++++++++++++++++
> drivers/usb/typec/ucsi/ucsi.h | 13 +++++++++++++
> 3 files changed, 60 insertions(+)
You somehow did not cc: the proper maintainers on this at all, have you
gone through the proper Intel kernel developer training that should
document all of this type of thing? If not, please do so.
thanks,
greg k-h
prev parent reply other threads:[~2025-07-21 14:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-03 19:32 [PATCH v2] usb: typec: ucsi: Add support for READ_POWER_LEVEL command Venkat Jayaraman
2025-07-21 14:35 ` Greg KH [this message]
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=2025072133-mastiff-calorie-c02d@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=linux-usb@vger.kernel.org \
--cc=pse.type-c.linux@intel.com \
--cc=venkat.jayaraman@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