From: Li Jun <jun.li@nxp.com>
To: robh+dt@kernel.org, shawnguo@kernel.org, balbi@kernel.org,
mathias.nyman@intel.com
Cc: gregkh@linuxfoundation.org, s.hauer@pengutronix.de,
kernel@pengutronix.de, festevam@gmail.com, linux-imx@nxp.com,
Anson.Huang@nxp.com, jun.li@nxp.com, aisheng.dong@nxp.com,
peng.fan@nxp.com, fugang.duan@nxp.com, qiangqing.zhang@nxp.com,
horia.geanta@nxp.com, linux-usb@vger.kernel.org,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 1/6] dt-bindings: usb: xhci: add property to disable xhci 64bit support
Date: Tue, 22 Sep 2020 18:46:47 +0800 [thread overview]
Message-ID: <1600771612-30727-2-git-send-email-jun.li@nxp.com> (raw)
In-Reply-To: <1600771612-30727-1-git-send-email-jun.li@nxp.com>
Add a property "xhci-64bit-support-disable" to disable xhci 64bit address
dma, some SoC integration may not support 64bit DMA but the AC64 bit
(bit 0) of HCCPARAMS1 is kept to be 1.
Signed-off-by: Li Jun <jun.li@nxp.com>
---
Documentation/devicetree/bindings/usb/usb-xhci.txt | 3 +++
1 file changed, 3 insertions(+)
diff --git a/Documentation/devicetree/bindings/usb/usb-xhci.txt b/Documentation/devicetree/bindings/usb/usb-xhci.txt
index 0c5cff8..26446fb 100644
--- a/Documentation/devicetree/bindings/usb/usb-xhci.txt
+++ b/Documentation/devicetree/bindings/usb/usb-xhci.txt
@@ -28,6 +28,9 @@ Optional properties:
- quirk-broken-port-ped: set if the controller has broken port disable mechanism
- imod-interval-ns: default interrupt moderation interval is 5000ns
- phys : see usb-hcd.yaml in the current directory
+ - xhci-64bit-support-disable: set if the AC64 bit (bit 0) of HCCPARAMS1 is
+ set to be 1, but the controller actually can't handle 64-bit address
+ due to SoC integration.
additionally the properties from usb-hcd.yaml (in the current directory) are
supported.
--
2.7.4
next prev parent reply other threads:[~2020-09-22 10:54 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-22 10:46 [PATCH v3 0/6] add NXP imx8mp usb support Li Jun
2020-09-22 10:46 ` Li Jun [this message]
2020-09-29 18:11 ` [PATCH v3 1/6] dt-bindings: usb: xhci: add property to disable xhci 64bit support Rob Herring
2020-10-02 16:39 ` Jun Li
2020-09-22 10:46 ` [PATCH v3 2/6] usb: host: xhci-plat: add support of XHCI_NO_64BIT_SUPPORT via property Li Jun
2020-09-22 10:46 ` [PATCH v3 3/6] dt-bindings: usb: dwc3-imx8mp: add imx8mp dwc3 glue bindings Li Jun
2020-09-22 14:32 ` Krzysztof Kozlowski
2020-09-22 16:45 ` Jun Li
2020-09-22 18:22 ` Krzysztof Kozlowski
2020-09-22 10:46 ` [PATCH v3 4/6] usb: dwc3: add imx8mp dwc3 glue layer driver Li Jun
2020-09-22 10:46 ` [PATCH v3 5/6] arm64: dtsi: imx8mp: add usb nodes Li Jun
2020-09-22 14:39 ` Krzysztof Kozlowski
2020-09-23 7:50 ` Sascha Hauer
2020-09-23 8:49 ` Jun Li
2020-09-22 10:46 ` [PATCH v3 6/6] arm64: dts: imx8mp-evk: enable usb1 as host mode Li Jun
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=1600771612-30727-2-git-send-email-jun.li@nxp.com \
--to=jun.li@nxp.com \
--cc=Anson.Huang@nxp.com \
--cc=aisheng.dong@nxp.com \
--cc=balbi@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=fugang.duan@nxp.com \
--cc=gregkh@linuxfoundation.org \
--cc=horia.geanta@nxp.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-usb@vger.kernel.org \
--cc=mathias.nyman@intel.com \
--cc=peng.fan@nxp.com \
--cc=qiangqing.zhang@nxp.com \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.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).