From: Naveen Kumar <mnkumar@google.com>
To: Mathias Nyman <mathias.nyman@intel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
royluo@google.com, devicetree@vger.kernel.org,
Naveen Kumar M <mnkumar@google.com>
Subject: [PATCH RESEND 1/2] usb: host: xhci-plat: Add quirk-no-64-bit-support
Date: Wed, 1 Nov 2023 10:16:24 +0000 [thread overview]
Message-ID: <20231101101625.4151442-2-mnkumar@google.com> (raw)
In-Reply-To: <20231101101625.4151442-1-mnkumar@google.com>
From: Naveen Kumar M <mnkumar@google.com>
This patch exposes the existing quirk XHCI_NO_64BIT_SUPPORT so that dwc3
clients can also use this flag. Despite HCCPARAMS1 being set to 1 some
clients may not support 64 bit addressing.
Signed-off-by: Naveen Kumar M <mnkumar@google.com>
---
drivers/usb/host/xhci-plat.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/usb/host/xhci-plat.c b/drivers/usb/host/xhci-plat.c
index b93161374293..d5f37decb7da 100644
--- a/drivers/usb/host/xhci-plat.c
+++ b/drivers/usb/host/xhci-plat.c
@@ -249,6 +249,9 @@ int xhci_plat_probe(struct platform_device *pdev, struct device *sysdev, const s
if (device_property_read_bool(tmpdev, "quirk-broken-port-ped"))
xhci->quirks |= XHCI_BROKEN_PORT_PED;
+ if (device_property_read_bool(tmpdev, "quirk-no-64-bit-support"))
+ xhci->quirks |= XHCI_NO_64BIT_SUPPORT;
+
device_property_read_u32(tmpdev, "imod-interval-ns",
&xhci->imod_interval);
}
--
2.42.0.820.g83a721a137-goog
next prev parent reply other threads:[~2023-11-01 10:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-01 10:16 [PATCH RESEND 0/2] Add a quirk in xhci-plat for parent nodes to specify no 64 bit support Naveen Kumar
2023-11-01 10:16 ` Naveen Kumar [this message]
2023-11-01 10:16 ` [PATCH RESEND 2/2] dt-bindings: usb: add no-64-bit-support property Naveen Kumar
2023-11-01 10:38 ` Conor Dooley
2023-11-01 11:26 ` Krzysztof Kozlowski
2023-11-06 14:44 ` Rob Herring
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=20231101101625.4151442-2-mnkumar@google.com \
--to=mnkumar@google.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mathias.nyman@intel.com \
--cc=robh+dt@kernel.org \
--cc=royluo@google.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 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.