From: Andreas Noever <andreas.noever@gmail.com>
To: linux-kernel@vger.kernel.org, Greg KH <greg@kroah.com>
Cc: Matthew Garrett <matthew.garrett@nebula.com>,
Andreas Noever <andreas.noever@gmail.com>
Subject: [PATCH 0/2] thunderbolt: Fix issues with more complex endpoints.
Date: Thu, 12 Jun 2014 23:11:45 +0200 [thread overview]
Message-ID: <1402607507-14858-1-git-send-email-andreas.noever@gmail.com> (raw)
Hi,
I have got my hand on a slightly more complex Thunderbolt device (a Startech
docking station). This series fixes the following issues that I have observed
with this device:
- Some ports on this device are disabled. Accessing them results in an error.
- This device uses both Thunderbolt links which are represented as two ports on
the switch. We have to ensure that we only scan one of these ports.
Part 1 of the series reads the switch configuration (disabled ports and which
port pairs are "dual link ports") from eeprom. Part 2 uses this information to
avoid scanning these ports.
Andreas Noever (2):
thunderbolt: Read port configuration from eeprom.
thunderbolt: Fix nontrivial endpoint devices.
drivers/thunderbolt/ctl.c | 2 +-
drivers/thunderbolt/eeprom.c | 266 ++++++++++++++++++++++++++++++++++++++++++-
drivers/thunderbolt/switch.c | 44 ++++---
drivers/thunderbolt/tb.c | 5 +
drivers/thunderbolt/tb.h | 7 +-
5 files changed, 300 insertions(+), 24 deletions(-)
--
2.0.0
next reply other threads:[~2014-06-12 21:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-12 21:11 Andreas Noever [this message]
2014-06-12 21:11 ` [PATCH 1/2] thunderbolt: Read port configuration from eeprom Andreas Noever
2014-06-12 21:11 ` [PATCH 2/2] thunderbolt: Fix nontrivial endpoint devices Andreas Noever
2014-06-12 22:06 ` [PATCH 0/2] thunderbolt: Fix issues with more complex endpoints Greg KH
2014-06-19 21:15 ` 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=1402607507-14858-1-git-send-email-andreas.noever@gmail.com \
--to=andreas.noever@gmail.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew.garrett@nebula.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