All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rajaram Regupathy <rajaram.regupathy@gmail.com>
To: linux-usb@vger.kernel.org
Cc: heikki.krogerus@linux.intel.com, Benson Leung <bleung@google.com>,
	Prashant Malani <pmalani@chromium.org>,
	jthies@google.com, saranya.gopal@intel.com
Subject: [ANNOUNCE] libtypec_0.1/lstypec_0.1 is released
Date: Sun, 16 Jan 2022 20:49:47 +0530	[thread overview]
Message-ID: <CAD039W71Hf06Bw4H_qjm7bRg__BjHfG=p-E7HXL62g0Yc7txBA@mail.gmail.com> (raw)

HI

libtypec
++++++

USB-Type C and USB Power Delivery systems are with multiple
specification versions, platform designs and microcontroller vendors
for managing  data, power and display.

libtypec is aimed to provide a generic way for userspace System
Software on Linux, Android, Chrome OS or Other OSes to build developer
tools or
other management applications for USB-Type C and USB Power Delivery
class devices.

Features
======
- libtypec - get method for port and port-partner capabilities
-  utils/lstypec -  displaying information about USB typec class
devices in the system and the devices connected to them

Release:
=======

Binary : https://github.com/Rajaram-Regupathy/libtypec/releases/download/libtypec_v0.1/libtypec_0.1.tar.xz
Source : https://github.com/Rajaram-Regupathy/libtypec/archive/refs/tags/libtypec_v0.1.tar.gz

             reply	other threads:[~2022-01-16 15:20 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-16 15:19 Rajaram Regupathy [this message]
2022-01-16 15:37 ` [ANNOUNCE] libtypec_0.1/lstypec_0.1 is released Stephan Brunner
2022-01-17  7:18 ` Greg KH
2022-01-17 14:37   ` Rajaram Regupathy
2022-01-17 15:38     ` Greg KH
2022-01-18 16:31       ` Rajaram Regupathy
2022-01-18 18:33         ` Greg KH
2022-01-18 19:16           ` Benson Leung
2022-01-19  8:28             ` Greg KH
2022-01-20  9:59               ` Rajaram Regupathy
2022-01-20 11:50                 ` Greg KH
2022-01-26 16:09                   ` Rajaram Regupathy
2022-01-26 16:39                     ` 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='CAD039W71Hf06Bw4H_qjm7bRg__BjHfG=p-E7HXL62g0Yc7txBA@mail.gmail.com' \
    --to=rajaram.regupathy@gmail.com \
    --cc=bleung@google.com \
    --cc=heikki.krogerus@linux.intel.com \
    --cc=jthies@google.com \
    --cc=linux-usb@vger.kernel.org \
    --cc=pmalani@chromium.org \
    --cc=saranya.gopal@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.