All of lore.kernel.org
 help / color / mirror / Atom feed
From: chunfeng yun <chunfeng.yun@mediatek.com>
To: Mathias Nyman <mathias.nyman@intel.com>
Cc: Rob Herring <robh+dt@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Matthias Brugger <matthias.bgg@gmail.com>,
	Felipe Balbi <balbi@ti.com>,
	Sascha Hauer <s.hauer@pengutronix.de>,
	<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>,
	"Roger Quadros" <rogerq@ti.com>, <linux-usb@vger.kernel.org>,
	<linux-mediatek@lists.infradead.org>,
	John Crispin <blogic@openwrt.org>,
	Daniel Kurtz <djkurtz@chromium.org>
Subject: Re: [PATCH v3 0/5] Mediatek xHCI support
Date: Thu, 23 Jul 2015 09:18:35 +0800	[thread overview]
Message-ID: <1437614315.3040.3.camel@mhfsdcap03> (raw)
In-Reply-To: <1437573945-31586-1-git-send-email-chunfeng.yun@mediatek.com>

Sorry, add a title

On Wed, 2015-07-22 at 22:05 +0800, Chunfeng Yun wrote:
> From ac1e8724bfa47494223bad0af450c1a63cd2fe0c Mon Sep 17 00:00:00 2001
> From: Chunfeng Yun <chunfeng.yun@mediatek.com>
> Date: Wed, 22 Jul 2015 21:15:15 +0800
> Subject: [PATCH 0/5] *** SUBJECT HERE ***
> 
> The patch supports MediaTek's xHCI controller.
> 
> There are some differences from xHCI spec:
> 1. The interval is specified in 250 * 8ns increments for Interrupt Moderation
> Interval(IMODI) of the Interrupter Moderation(IMOD) register, it is 8 times as
> much as that defined in xHCI spec.
> 
> 2. For the value of TD Size in Normal TRB, MTK's xHCI controller defines a
> number of packets that remain to be transferred for a TD after processing all
> Max packets in all previous TRBs,that means don't include the current TRB's,
> but in xHCI spec it includes the current ones.
> 
> 3. To minimize the scheduling effort for synchronous endpoints in xHC, the MTK
> architecture defines some extra SW scheduling parameters for HW. According to
> these parameters provided by SW, the xHC can easily decide whether a
> synchronous endpoint should be scheduled in a specific uFrame. The extra SW
> scheduling parameters are put into reserved DWs in Slot and Endpoint Context.
> And a bandwidth scheduler algorithm is added to support such feature.
> 
> A usb3.0 phy driver is also added which used by mt65xx SoCs platform, it
> supports two usb2.0 ports and one usb3.0 port.
> 
> Change in v3:
> 1. implement generic phy
> 2. move opperations for IPPC and wakeup from phy driver to xHCI driver
> 3. seperate quirk functions into a single C file to fix up dependence issue
> 
> Chunfeng Yun (5):
>   dt-bindings: Add usb3.0 phy binding for MT65xx SoCs
>   dt-bindings: Add a binding for Mediatek xHCI host controller
>   usb: phy: add usb3.0 phy driver for mt65xx SoCs
>   xhci: mediatek: support MTK xHCI host controller
>   arm64: dts: mediatek: add xHCI & usb phy for mt8173
> 
>  .../devicetree/bindings/phy/phy-mt65xx-u3.txt      |  21 +
>  .../devicetree/bindings/usb/mt8173-xhci.txt        |  50 ++
>  arch/arm64/boot/dts/mediatek/mt8173-evb.dts        |  15 +
>  arch/arm64/boot/dts/mediatek/mt8173.dtsi           |  31 +
>  drivers/phy/Kconfig                                |   9 +
>  drivers/phy/Makefile                               |   1 +
>  drivers/phy/phy-mt65xx-usb3.c                      | 426 +++++++++++
>  drivers/usb/host/Kconfig                           |   9 +
>  drivers/usb/host/Makefile                          |   4 +
>  drivers/usb/host/xhci-mtk-sch.c                    | 436 +++++++++++
>  drivers/usb/host/xhci-mtk.c                        | 836 +++++++++++++++++++++
>  drivers/usb/host/xhci-mtk.h                        | 135 ++++
>  drivers/usb/host/xhci-ring.c                       |  35 +-
>  drivers/usb/host/xhci.c                            |  19 +-
>  drivers/usb/host/xhci.h                            |   1 +
>  15 files changed, 2021 insertions(+), 7 deletions(-)
>  create mode 100644 Documentation/devicetree/bindings/phy/phy-mt65xx-u3.txt
>  create mode 100644 Documentation/devicetree/bindings/usb/mt8173-xhci.txt
>  create mode 100644 drivers/phy/phy-mt65xx-usb3.c
>  create mode 100644 drivers/usb/host/xhci-mtk-sch.c
>  create mode 100644 drivers/usb/host/xhci-mtk.c
>  create mode 100644 drivers/usb/host/xhci-mtk.h
> 
> --
> 1.8.1.1.dirty
> 
> In-Reply-To: 
> 



WARNING: multiple messages have this Message-ID (diff)
From: chunfeng yun <chunfeng.yun@mediatek.com>
To: Mathias Nyman <mathias.nyman@intel.com>
Cc: Rob Herring <robh+dt@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Matthias Brugger <matthias.bgg@gmail.com>,
	Felipe Balbi <balbi@ti.com>,
	Sascha Hauer <s.hauer@pengutronix.de>,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	Roger Quadros <rogerq@ti.com>,
	linux-usb@vger.kernel.org, linux-mediatek@lists.infradead.org,
	John Crispin <blogic@openwrt.org>,
	Daniel Kurtz <djkurtz@chromium.org>
Subject: Re: [PATCH v3 0/5] Mediatek xHCI support
Date: Thu, 23 Jul 2015 09:18:35 +0800	[thread overview]
Message-ID: <1437614315.3040.3.camel@mhfsdcap03> (raw)
In-Reply-To: <1437573945-31586-1-git-send-email-chunfeng.yun@mediatek.com>

Sorry, add a title

On Wed, 2015-07-22 at 22:05 +0800, Chunfeng Yun wrote:
> From ac1e8724bfa47494223bad0af450c1a63cd2fe0c Mon Sep 17 00:00:00 2001
> From: Chunfeng Yun <chunfeng.yun@mediatek.com>
> Date: Wed, 22 Jul 2015 21:15:15 +0800
> Subject: [PATCH 0/5] *** SUBJECT HERE ***
> 
> The patch supports MediaTek's xHCI controller.
> 
> There are some differences from xHCI spec:
> 1. The interval is specified in 250 * 8ns increments for Interrupt Moderation
> Interval(IMODI) of the Interrupter Moderation(IMOD) register, it is 8 times as
> much as that defined in xHCI spec.
> 
> 2. For the value of TD Size in Normal TRB, MTK's xHCI controller defines a
> number of packets that remain to be transferred for a TD after processing all
> Max packets in all previous TRBs,that means don't include the current TRB's,
> but in xHCI spec it includes the current ones.
> 
> 3. To minimize the scheduling effort for synchronous endpoints in xHC, the MTK
> architecture defines some extra SW scheduling parameters for HW. According to
> these parameters provided by SW, the xHC can easily decide whether a
> synchronous endpoint should be scheduled in a specific uFrame. The extra SW
> scheduling parameters are put into reserved DWs in Slot and Endpoint Context.
> And a bandwidth scheduler algorithm is added to support such feature.
> 
> A usb3.0 phy driver is also added which used by mt65xx SoCs platform, it
> supports two usb2.0 ports and one usb3.0 port.
> 
> Change in v3:
> 1. implement generic phy
> 2. move opperations for IPPC and wakeup from phy driver to xHCI driver
> 3. seperate quirk functions into a single C file to fix up dependence issue
> 
> Chunfeng Yun (5):
>   dt-bindings: Add usb3.0 phy binding for MT65xx SoCs
>   dt-bindings: Add a binding for Mediatek xHCI host controller
>   usb: phy: add usb3.0 phy driver for mt65xx SoCs
>   xhci: mediatek: support MTK xHCI host controller
>   arm64: dts: mediatek: add xHCI & usb phy for mt8173
> 
>  .../devicetree/bindings/phy/phy-mt65xx-u3.txt      |  21 +
>  .../devicetree/bindings/usb/mt8173-xhci.txt        |  50 ++
>  arch/arm64/boot/dts/mediatek/mt8173-evb.dts        |  15 +
>  arch/arm64/boot/dts/mediatek/mt8173.dtsi           |  31 +
>  drivers/phy/Kconfig                                |   9 +
>  drivers/phy/Makefile                               |   1 +
>  drivers/phy/phy-mt65xx-usb3.c                      | 426 +++++++++++
>  drivers/usb/host/Kconfig                           |   9 +
>  drivers/usb/host/Makefile                          |   4 +
>  drivers/usb/host/xhci-mtk-sch.c                    | 436 +++++++++++
>  drivers/usb/host/xhci-mtk.c                        | 836 +++++++++++++++++++++
>  drivers/usb/host/xhci-mtk.h                        | 135 ++++
>  drivers/usb/host/xhci-ring.c                       |  35 +-
>  drivers/usb/host/xhci.c                            |  19 +-
>  drivers/usb/host/xhci.h                            |   1 +
>  15 files changed, 2021 insertions(+), 7 deletions(-)
>  create mode 100644 Documentation/devicetree/bindings/phy/phy-mt65xx-u3.txt
>  create mode 100644 Documentation/devicetree/bindings/usb/mt8173-xhci.txt
>  create mode 100644 drivers/phy/phy-mt65xx-usb3.c
>  create mode 100644 drivers/usb/host/xhci-mtk-sch.c
>  create mode 100644 drivers/usb/host/xhci-mtk.c
>  create mode 100644 drivers/usb/host/xhci-mtk.h
> 
> --
> 1.8.1.1.dirty
> 
> In-Reply-To: 
> 

WARNING: multiple messages have this Message-ID (diff)
From: chunfeng.yun@mediatek.com (chunfeng yun)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 0/5] Mediatek xHCI support
Date: Thu, 23 Jul 2015 09:18:35 +0800	[thread overview]
Message-ID: <1437614315.3040.3.camel@mhfsdcap03> (raw)
In-Reply-To: <1437573945-31586-1-git-send-email-chunfeng.yun@mediatek.com>

Sorry, add a title

On Wed, 2015-07-22 at 22:05 +0800, Chunfeng Yun wrote:
> From ac1e8724bfa47494223bad0af450c1a63cd2fe0c Mon Sep 17 00:00:00 2001
> From: Chunfeng Yun <chunfeng.yun@mediatek.com>
> Date: Wed, 22 Jul 2015 21:15:15 +0800
> Subject: [PATCH 0/5] *** SUBJECT HERE ***
> 
> The patch supports MediaTek's xHCI controller.
> 
> There are some differences from xHCI spec:
> 1. The interval is specified in 250 * 8ns increments for Interrupt Moderation
> Interval(IMODI) of the Interrupter Moderation(IMOD) register, it is 8 times as
> much as that defined in xHCI spec.
> 
> 2. For the value of TD Size in Normal TRB, MTK's xHCI controller defines a
> number of packets that remain to be transferred for a TD after processing all
> Max packets in all previous TRBs,that means don't include the current TRB's,
> but in xHCI spec it includes the current ones.
> 
> 3. To minimize the scheduling effort for synchronous endpoints in xHC, the MTK
> architecture defines some extra SW scheduling parameters for HW. According to
> these parameters provided by SW, the xHC can easily decide whether a
> synchronous endpoint should be scheduled in a specific uFrame. The extra SW
> scheduling parameters are put into reserved DWs in Slot and Endpoint Context.
> And a bandwidth scheduler algorithm is added to support such feature.
> 
> A usb3.0 phy driver is also added which used by mt65xx SoCs platform, it
> supports two usb2.0 ports and one usb3.0 port.
> 
> Change in v3:
> 1. implement generic phy
> 2. move opperations for IPPC and wakeup from phy driver to xHCI driver
> 3. seperate quirk functions into a single C file to fix up dependence issue
> 
> Chunfeng Yun (5):
>   dt-bindings: Add usb3.0 phy binding for MT65xx SoCs
>   dt-bindings: Add a binding for Mediatek xHCI host controller
>   usb: phy: add usb3.0 phy driver for mt65xx SoCs
>   xhci: mediatek: support MTK xHCI host controller
>   arm64: dts: mediatek: add xHCI & usb phy for mt8173
> 
>  .../devicetree/bindings/phy/phy-mt65xx-u3.txt      |  21 +
>  .../devicetree/bindings/usb/mt8173-xhci.txt        |  50 ++
>  arch/arm64/boot/dts/mediatek/mt8173-evb.dts        |  15 +
>  arch/arm64/boot/dts/mediatek/mt8173.dtsi           |  31 +
>  drivers/phy/Kconfig                                |   9 +
>  drivers/phy/Makefile                               |   1 +
>  drivers/phy/phy-mt65xx-usb3.c                      | 426 +++++++++++
>  drivers/usb/host/Kconfig                           |   9 +
>  drivers/usb/host/Makefile                          |   4 +
>  drivers/usb/host/xhci-mtk-sch.c                    | 436 +++++++++++
>  drivers/usb/host/xhci-mtk.c                        | 836 +++++++++++++++++++++
>  drivers/usb/host/xhci-mtk.h                        | 135 ++++
>  drivers/usb/host/xhci-ring.c                       |  35 +-
>  drivers/usb/host/xhci.c                            |  19 +-
>  drivers/usb/host/xhci.h                            |   1 +
>  15 files changed, 2021 insertions(+), 7 deletions(-)
>  create mode 100644 Documentation/devicetree/bindings/phy/phy-mt65xx-u3.txt
>  create mode 100644 Documentation/devicetree/bindings/usb/mt8173-xhci.txt
>  create mode 100644 drivers/phy/phy-mt65xx-usb3.c
>  create mode 100644 drivers/usb/host/xhci-mtk-sch.c
>  create mode 100644 drivers/usb/host/xhci-mtk.c
>  create mode 100644 drivers/usb/host/xhci-mtk.h
> 
> --
> 1.8.1.1.dirty
> 
> In-Reply-To: 
> 

  parent reply	other threads:[~2015-07-23  1:18 UTC|newest]

Thread overview: 62+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-22 14:05 Chunfeng Yun
2015-07-22 14:05 ` No subject Chunfeng Yun
2015-07-22 14:05 ` (unknown), Chunfeng Yun
2015-07-22 14:05 ` [PATCH v3 1/5] dt-bindings: Add usb3.0 phy binding for MT65xx SoCs Chunfeng Yun
2015-07-22 14:05   ` Chunfeng Yun
2015-07-22 14:05   ` Chunfeng Yun
2015-07-22 14:05 ` [PATCH v3 2/5] dt-bindings: Add a binding for Mediatek xHCI host controller Chunfeng Yun
2015-07-22 14:05   ` Chunfeng Yun
2015-07-22 14:05   ` Chunfeng Yun
2015-07-22 14:22   ` Mark Rutland
2015-07-22 14:22     ` Mark Rutland
2015-07-22 14:22     ` Mark Rutland
2015-07-26  3:45     ` chunfeng yun
2015-07-26  3:45       ` chunfeng yun
2015-07-26  3:45       ` chunfeng yun
2015-07-31 13:37       ` Mark Rutland
2015-07-31 13:37         ` Mark Rutland
2015-07-31 13:37         ` Mark Rutland
2015-08-01  3:42         ` chunfeng yun
2015-08-01  3:42           ` chunfeng yun
2015-08-01  3:42           ` chunfeng yun
2015-07-22 14:05 ` [PATCH v3 3/5] usb: phy: add usb3.0 phy driver for mt65xx SoCs Chunfeng Yun
2015-07-22 14:05   ` Chunfeng Yun
2015-07-22 14:05   ` Chunfeng Yun
2015-07-22 14:21   ` Felipe Balbi
2015-07-22 14:21     ` Felipe Balbi
2015-07-22 14:21     ` Felipe Balbi
2015-07-26  2:51     ` chunfeng yun
2015-07-26  2:51       ` chunfeng yun
2015-07-26  2:51       ` chunfeng yun
2015-07-28  5:47       ` Kishon Vijay Abraham I
2015-07-28  5:47         ` Kishon Vijay Abraham I
2015-07-28  5:47         ` Kishon Vijay Abraham I
2015-07-31 12:25         ` chunfeng yun
2015-07-31 12:25           ` chunfeng yun
2015-07-31 12:25           ` chunfeng yun
2015-07-31 14:18           ` Kishon Vijay Abraham I
2015-07-31 14:18             ` Kishon Vijay Abraham I
2015-07-31 14:18             ` Kishon Vijay Abraham I
2015-08-01  2:42             ` chunfeng yun
2015-08-01  2:42               ` chunfeng yun
2015-08-01  2:42               ` chunfeng yun
2015-07-27 13:58   ` Ricky Liang
2015-07-27 13:58     ` Ricky Liang
2015-07-27 13:58     ` Ricky Liang
2015-07-31 12:32     ` chunfeng yun
2015-07-31 12:32       ` chunfeng yun
2015-07-31 12:32       ` chunfeng yun
2015-07-22 14:05 ` [PATCH v3 4/5] xhci: mediatek: support MTK xHCI host controller Chunfeng Yun
2015-07-22 14:05   ` Chunfeng Yun
2015-07-22 14:05   ` Chunfeng Yun
2015-07-22 14:05 ` [PATCH v3 5/5] arm64: dts: mediatek: add xHCI & usb phy for mt8173 Chunfeng Yun
2015-07-22 14:05   ` Chunfeng Yun
2015-07-22 14:05   ` Chunfeng Yun
2015-07-22 18:11   ` Sergei Shtylyov
2015-07-22 18:11     ` Sergei Shtylyov
2015-07-26  2:41     ` chunfeng yun
2015-07-26  2:41       ` chunfeng yun
2015-07-26  2:41       ` chunfeng yun
2015-07-23  1:18 ` chunfeng yun [this message]
2015-07-23  1:18   ` [PATCH v3 0/5] Mediatek xHCI support chunfeng yun
2015-07-23  1:18   ` 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=1437614315.3040.3.camel@mhfsdcap03 \
    --to=chunfeng.yun@mediatek.com \
    --cc=balbi@ti.com \
    --cc=blogic@openwrt.org \
    --cc=devicetree@vger.kernel.org \
    --cc=djkurtz@chromium.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mathias.nyman@intel.com \
    --cc=matthias.bgg@gmail.com \
    --cc=robh+dt@kernel.org \
    --cc=rogerq@ti.com \
    --cc=s.hauer@pengutronix.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.