Quoting Stephen Boyd (2020-09-09 17:48:53) > This binding only describes the USB phy inside the USB3 + DP "combo" > phy. Add information for the DP phy and describe the sub-nodes that > represent the DP and USB3 phys that exist inside the combo wrapper. > Remove reg-names from required properties because it isn't required nor > used by the kernel driver. > > Cc: Jeykumar Sankaran <jsa...@codeaurora.org> > Cc: Chandan Uddaraju <chand...@codeaurora.org> > Cc: Vara Reddy <va...@codeaurora.org> > Cc: Tanmay Shah <tan...@codeaurora.org> > Cc: Bjorn Andersson <bjorn.anders...@linaro.org> > Cc: Manu Gautam <mgau...@codeaurora.org> > Cc: Sandeep Maheswaram <s...@codeaurora.org> > Cc: Douglas Anderson <diand...@chromium.org> > Cc: Sean Paul <seanp...@chromium.org> > Cc: Jonathan Marek <jonat...@marek.ca> > Cc: Dmitry Baryshkov <dmitry.barysh...@linaro.org> > Cc: <devicet...@vger.kernel.org> > Cc: Rob Herring <robh...@kernel.org> > Cc: Rob Clark <robdcl...@chromium.org> > Signed-off-by: Stephen Boyd <swb...@chromium.org> > --- > .../bindings/phy/qcom,qmp-usb3-dp-phy.yaml | 91 +++++++++++++++++-- > 1 file changed, 81 insertions(+), 10 deletions(-)
I noticed that I didn't document the new compatible string I'm using, qcom,sc7180-qmp-usb3-dp-phy, ugh. Should I copy the whole file over and make a new document for the new compatible string? That feels like the better solution vs. making this binding have min/max stuff where it fails to enforce the DP part of the phy. We can delete this binding once the kernel tree isn't using it, right? Rob H? > > diff --git a/Documentation/devicetree/bindings/phy/qcom,qmp-usb3-dp-phy.yaml > b/Documentation/devicetree/bindings/phy/qcom,qmp-usb3-dp-phy.yaml > index ef8ae9f73092..4154f5748d39 100644 > --- a/Documentation/devicetree/bindings/phy/qcom,qmp-usb3-dp-phy.yaml > +++ b/Documentation/devicetree/bindings/phy/qcom,qmp-usb3-dp-phy.yaml > @@ -17,13 +17,15 @@ properties: > - qcom,sdm845-qmp-usb3-phy > reg:
