From: Forest Crossman <cyrozap@gmail.com>
To: linux-usb@vger.kernel.org
Cc: Forest Crossman <cyrozap@gmail.com>,
mathias.nyman@intel.com, gregkh@linuxfoundation.org,
linux-kernel@vger.kernel.org
Subject: [PATCH 0/2] Small fixes for ASMedia host controllers
Date: Mon, 27 Jul 2020 04:06:27 -0500 [thread overview]
Message-ID: <20200727090629.169701-1-cyrozap@gmail.com> (raw)
The first patch just defines some host controller device IDs to make the
code a bit easier to read (since the controller part number is not
always the same as the DID) and to prepare for the next patch.
The second patch defines a new device ID for the ASM1142 and enables the
XHCI_NO_64BIT_SUPPORT quirk for that device, since it has the same
problem with truncating the higher bits as the ASM2142/ASM3142.
Forest Crossman (2):
usb: xhci: define IDs for various ASMedia host controllers
usb: xhci: Fix ASMedia ASM1142 DMA addressing
drivers/usb/host/xhci-pci.c | 10 +++++++---
1 file changed, 7 insertions(+), 3 deletions(-)
--
2.20.1
next reply other threads:[~2020-07-27 9:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-27 9:06 Forest Crossman [this message]
2020-07-27 9:06 ` [PATCH 1/2] usb: xhci: define IDs for various ASMedia host controllers Forest Crossman
2020-07-27 9:26 ` Greg KH
2020-07-27 10:03 ` Forest Crossman
2020-07-27 10:12 ` Greg KH
2020-07-27 9:06 ` [PATCH 2/2] usb: xhci: Fix ASMedia ASM1142 DMA addressing Forest Crossman
2020-07-28 4:24 ` [PATCH v2 0/2] Small fixes for ASMedia host controllers Forest Crossman
2020-07-28 4:24 ` [PATCH v2 1/2] usb: xhci: define IDs for various " Forest Crossman
2020-07-29 18:08 ` Sergei Shtylyov
2020-07-28 4:24 ` [PATCH v2 2/2] usb: xhci: Fix ASMedia ASM1142 DMA addressing Forest Crossman
2020-07-28 11:16 ` [PATCH v2 0/2] Small fixes for ASMedia host controllers Greg KH
2020-07-28 12:40 ` Mathias Nyman
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=20200727090629.169701-1-cyrozap@gmail.com \
--to=cyrozap@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mathias.nyman@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;
as well as URLs for NNTP newsgroup(s).