linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: <Mario.Limonciello@dell.com>
To: <pmenzel@molgen.mpg.de>, <mathias.nyman@linux.intel.com>,
	<mika.westerberg@linux.intel.com>
Cc: <andreas.noever@gmail.com>, <michael.jamet@intel.com>,
	<YehezkelShB@gmail.com>, <ck@xatom.net>,
	<linux-kernel@vger.kernel.org>, <anthony.wong@canonical.com>
Subject: RE: USB devices on Dell TB16 dock stop working after resuming
Date: Fri, 17 Jan 2020 18:33:12 +0000	[thread overview]
Message-ID: <789c7db3bafa4bf9a9348123492196b0@AUSX13MPC105.AMER.DELL.COM> (raw)
In-Reply-To: <44d8eb12-9af5-7b9a-fa24-be8e8ec3cd48@molgen.mpg.de>

> > I was able to reproduce the issue with an external HS hub as well, so  this issue
> > appears to be more related to ASMedia host than the built in HS hub in TB16
> 
> I contacted the (German) Dell support, and they asked me to update the laptop
> firmware to 1.9.1 claiming that these issues might be fixed there (despite the
> change-log not containing that). Anyway, after the update, the user is still
> able to reproduce the issue.
> 
> Mario, what can I do, so the issue is escalated to your team, so you can work
> with ASMedia to solve this?
> 
> 
> Kind regards,
> 
> Paul

From this thread it does sound to me like an ASMedia firmware problem,
not a Linux kernel problem.

I do know there is an updated ASMedia firmware binary available.  Right now
however there is unfortunately not a way to update ASMedia hub firmware using
free software.  If possible, I would recommend that you try to update the
firmware using a Windows machine and see if it helps the problem.

I'm sorry and I don't intend to "pass the buck" but if that doesn't help this needs
to be prioritized and escalated with Dell support.

They will then work with the appropriate engineering team who owns the relationship
to ASMedia to resolve it.

  reply	other threads:[~2020-01-17 18:33 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-04 13:13 USB devices on Dell TB16 dock stop working after resuming Paul Menzel
2019-11-04 14:24 ` Mika Westerberg
2019-11-04 14:44   ` Mika Westerberg
2019-11-04 15:44     ` Mika Westerberg
2019-11-04 15:49       ` Mario.Limonciello
2019-11-04 16:11         ` Paul Menzel
2019-11-04 16:17           ` Mario.Limonciello
2019-11-04 16:22             ` Paul Menzel
2019-11-04 16:21           ` Mika Westerberg
2019-11-19 16:55             ` Paul Menzel
2019-11-19 17:20               ` Paul Menzel
2019-11-20 10:50               ` Mika Westerberg
2019-11-20 14:15                 ` Mario.Limonciello
2019-11-20 15:23                   ` Mika Westerberg
2019-11-20 17:06                     ` Mario.Limonciello
2019-11-20 17:16                       ` Yehezkel Bernat
2019-11-20 17:41                         ` Mario.Limonciello
2019-11-20 17:43                         ` Mika Westerberg
2019-11-20 17:39                       ` Mika Westerberg
2019-11-22 10:50                 ` Mika Westerberg
2019-11-22 11:05                   ` Paul Menzel
2019-11-22 11:29                     ` Mika Westerberg
2019-11-22 11:33                       ` Paul Menzel
2019-11-22 11:41                         ` Mika Westerberg
2019-11-25  9:20                           ` Mathias Nyman
2019-11-26 11:33                             ` Paul Menzel
2019-11-26 12:44                               ` Mathias Nyman
2019-12-20 14:25                                 ` Paul Menzel
2019-12-23  9:39                                   ` Mathias Nyman
2020-01-17  9:56                                     ` Paul Menzel
2020-01-17 18:33                                       ` Mario.Limonciello [this message]
2020-01-18  9:15                                         ` Paul Menzel
2020-01-27 22:16                                           ` Paul Menzel
2020-02-05 13:10                                             ` Paul Menzel

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=789c7db3bafa4bf9a9348123492196b0@AUSX13MPC105.AMER.DELL.COM \
    --to=mario.limonciello@dell.com \
    --cc=YehezkelShB@gmail.com \
    --cc=andreas.noever@gmail.com \
    --cc=anthony.wong@canonical.com \
    --cc=ck@xatom.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mathias.nyman@linux.intel.com \
    --cc=michael.jamet@intel.com \
    --cc=mika.westerberg@linux.intel.com \
    --cc=pmenzel@molgen.mpg.de \
    /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;
as well as URLs for NNTP newsgroup(s).