Hi,
Li Jun [off-list ref] writes:
quoted hunk ↗ jump to hunk
In case dwc3 has SoC specific customizations, dwc3 glue driver can base on
compatible string and pass it via platform data to dwc3 core driver; and
pass xhci private data further to xhci-plat like quirks.
Signed-off-by: Li Jun <redacted>
---
drivers/usb/dwc3/core.h | 5 +++++
drivers/usb/dwc3/host.c | 9 +++++++++
2 files changed, 14 insertions(+)
diff --git a/drivers/usb/dwc3/core.h b/drivers/usb/dwc3/core.h
index 0b8ea8c..3146697 100644
--- a/drivers/usb/dwc3/core.h
+++ b/drivers/usb/dwc3/core.h
@@ -29,6 +29,7 @@
#include <linux/ulpi/interface.h>
#include <linux/phy/phy.h>
+#include "../host/xhci-plat.h"
#define DWC3_MSG_MAX 500
@@ -924,6 +925,10 @@ struct dwc3_scratchpad_array {
__le64 dma_adr[DWC3_MAX_HIBER_SCRATCHBUFS];
};
+struct dwc3_platform_data {
+ struct xhci_plat_priv *xhci_priv;
+};
why? We should rely on properties, no?
--
balbi