From: mathias.nyman@intel.com (Mathias Nyman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v7 4/5] xhci: mediatek: support MTK xHCI host controller
Date: Tue, 08 Sep 2015 13:45:07 +0300 [thread overview]
Message-ID: <55EEBC33.5030906@intel.com> (raw)
In-Reply-To: <1441693083-8440-5-git-send-email-chunfeng.yun@mediatek.com>
Hi
On 08.09.2015 09:18, Chunfeng Yun wrote:
> There some vendor quirks for MTK xhci host controller:
> 1. It defines some extra SW scheduling parameters for HW
> to minimize the scheduling effort for synchronous and
> interrupt endpoints. The parameters are put into reseved
> DWs of slot context and endpoint context.
> 2. Its IMODI unit for Interrupter Moderation register is
> 8 times as much as that defined in xHCI spec.
> 3. Its TDS in Normal TRB defines a number of packets that
> remains to be transferred for a TD after processing all
> Max packets in all previous TRBs.
>
I just rewrote and unified the the xhci TD remainder functions,
now we got only one xhci_td_remainder() function which should
be more suitable for quirks.
You can add the quirk directly to it, no need to duplicate the
whole function.
-Mathias
next prev parent reply other threads:[~2015-09-08 10:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-08 6:17 [PATCH v7 0/5] Mediatek xHCI support Chunfeng Yun
2015-09-08 6:17 ` [PATCH v7 1/5] dt-bindings: Add usb3.0 phy binding for MT65xx SoCs Chunfeng Yun
2015-09-09 0:16 ` Rob Herring
2015-09-11 3:34 ` chunfeng yun
2015-09-09 13:58 ` Rob Herring
2015-09-08 6:18 ` [PATCH v7 2/5] dt-bindings: Add a binding for Mediatek xHCI host controller Chunfeng Yun
2015-09-09 0:30 ` Rob Herring
2015-09-11 3:39 ` chunfeng yun
2015-09-08 6:18 ` [PATCH v7 3/5] usb: phy: add usb3.0 phy driver for mt65xx SoCs Chunfeng Yun
2015-09-08 6:18 ` [PATCH v7 4/5] xhci: mediatek: support MTK xHCI host controller Chunfeng Yun
2015-09-08 10:45 ` Mathias Nyman [this message]
2015-09-08 6:18 ` [PATCH v7 5/5] arm64: dts: mediatek: add xHCI & usb phy for mt8173 Chunfeng Yun
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=55EEBC33.5030906@intel.com \
--to=mathias.nyman@intel.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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).