public inbox for linux-usb@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Douglas Gilbert <dgilbert@interlog.com>
Cc: linux-usb@vger.kernel.org
Subject: Re: [Announce] lsucpd release 0.91 utility for USB Type-C
Date: Fri, 8 Dec 2023 08:16:35 +0100	[thread overview]
Message-ID: <2023120804-chowder-sampling-8ebb@gregkh> (raw)
In-Reply-To: <5f74a231-e0c2-4be6-ab90-6592f7cfa8df@interlog.com>

On Fri, Dec 08, 2023 at 01:36:02AM -0500, Douglas Gilbert wrote:
> lsucpd is a command line utility for listing USB Type-C ports, partners
> and any associated PD objects. It is essentially data-mining the
> /sys/class/typec and /sys/class/usb_power_delivery directories. So
> lsucpd performs no magic and root permissions are not required.
> 
> lsucpd was originally announced in this post on 28 August 2023:
>   https://marc.info/?l=linux-usb&m=169325926403279&w=2
> That code has been tagged as 'r0.89'. There is also a 'r0.90' tag
> but it was not announced. This release is tagged as 'r0.91'. The
> code is available at this git mirror at:
>     https://github.com/doug-gilbert/lsucpd
> 
> Changelog since 0.89 [20230827] [svn: r9]
>   - add the first stage of JSON support
>   - add --pdo-snk= and --pdo-src= options to decode PDOs
>   - add --rdo= option to decode RDOs
>   - make preparations for PD revision 3.2

Nice!  Any thoughts about adding this functionality to the usbutils
package to make it all in one place?

thanks,

greg k-h

  reply	other threads:[~2023-12-08  7:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-08  6:36 [Announce] lsucpd release 0.91 utility for USB Type-C Douglas Gilbert
2023-12-08  7:16 ` Greg KH [this message]
2023-12-08 21:14   ` Douglas Gilbert
2023-12-11 15:07 ` Alexander Stein
2023-12-12  5:44   ` Douglas Gilbert

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=2023120804-chowder-sampling-8ebb@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=dgilbert@interlog.com \
    --cc=linux-usb@vger.kernel.org \
    /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