Linux USB
 help / color / mirror / Atom feed
From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Yehezkel Bernat <YehezkelShB@gmail.com>,
	Michael Jamet <michael.jamet@intel.com>,
	Lukas Wunner <lukas@wunner.de>,
	Andreas Noever <andreas.noever@gmail.com>
Cc: linux-usb@vger.kernel.org,
	Aapo Vienamo <aapo.vienamo@linux.intel.com>,
	Rene Sapiens <rene.sapiens@intel.com>,
	R Kannappan <r.kannappan@intel.com>,
	Mika Westerberg <mika.westerberg@linux.intel.com>
Subject: [PATCH 0/4] thunderbolt: Improve software receiver lane margining
Date: Tue, 13 Aug 2024 14:01:31 +0300	[thread overview]
Message-ID: <20240813110135.2178900-1-mika.westerberg@linux.intel.com> (raw)

Hi all,

This series improves the software receiver lane margining support in
debugfs so that it should be more usable now.

Aapo Vienamo (1):
  thunderbolt: Add missing usb4_port_sb_read() to usb4_port_sw_margin()

R Kannappan (1):
  thunderbolt: Improve software receiver lane margining

Rene Sapiens (2):
  thunderbolt: Consolidate margining parameters into a structure
  thunderbolt: Add optional voltage offset range for receiver lane margining

 drivers/thunderbolt/debugfs.c | 381 ++++++++++++++++++++++++++++++++--
 drivers/thunderbolt/sb_regs.h |  18 +-
 drivers/thunderbolt/tb.h      |  42 +++-
 drivers/thunderbolt/usb4.c    |  62 +++---
 4 files changed, 451 insertions(+), 52 deletions(-)

-- 
2.43.0


             reply	other threads:[~2024-08-13 11:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-13 11:01 Mika Westerberg [this message]
2024-08-13 11:01 ` [PATCH 1/4] thunderbolt: Add missing usb4_port_sb_read() to usb4_port_sw_margin() Mika Westerberg
2024-08-13 11:01 ` [PATCH 2/4] thunderbolt: Consolidate margining parameters into a structure Mika Westerberg
2024-08-13 11:01 ` [PATCH 3/4] thunderbolt: Add optional voltage offset range for receiver lane margining Mika Westerberg
2024-08-13 11:01 ` [PATCH 4/4] thunderbolt: Improve software " Mika Westerberg
2024-08-16  9:38   ` Dan Carpenter

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=20240813110135.2178900-1-mika.westerberg@linux.intel.com \
    --to=mika.westerberg@linux.intel.com \
    --cc=YehezkelShB@gmail.com \
    --cc=aapo.vienamo@linux.intel.com \
    --cc=andreas.noever@gmail.com \
    --cc=linux-usb@vger.kernel.org \
    --cc=lukas@wunner.de \
    --cc=michael.jamet@intel.com \
    --cc=r.kannappan@intel.com \
    --cc=rene.sapiens@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