From: Rob Herring <robh@kernel.org>
To: Neil Armstrong <neil.armstrong@linaro.org>
Cc: linux-usb@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Konrad Dybcio <konrad.dybcio@linaro.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
linux-kernel@vger.kernel.org, Will Deacon <will@kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Heikki Krogerus <heikki.krogerus@linux.intel.com>,
Catalin Marinas <catalin.marinas@arm.com>,
linux-arm-msm@vger.kernel.org, Andy Gross <agross@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Bjorn Andersson <andersson@kernel.org>
Subject: Re: [PATCH v3 05/12] dt-bindings: usb: snps,dwc3: document HS & SS OF graph ports
Date: Thu, 16 Mar 2023 18:03:40 -0500 [thread overview]
Message-ID: <167900782010.4050347.7367290857102133764.robh@kernel.org> (raw)
In-Reply-To: <20230130-topic-sm8450-upstream-pmic-glink-v3-5-4c860d265d28@linaro.org>
On Thu, 09 Mar 2023 14:27:56 +0100, Neil Armstrong wrote:
> Document the optional ports subnode to describe the High-Speed
> and Super-Speed connections as separate OF graph links.
>
> The ports property is an alternative to the already documented
> single port subnode property.
>
> Signed-off-by: Neil Armstrong <neil.armstrong@linaro.org>
> ---
> Documentation/devicetree/bindings/usb/snps,dwc3.yaml | 16 ++++++++++++++++
> 1 file changed, 16 insertions(+)
>
Reviewed-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2023-03-16 23:03 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-09 13:27 [PATCH v3 00/12] soc: qcom: add UCSI function to PMIC GLINK Neil Armstrong
2023-03-09 13:27 ` [PATCH v3 01/12] usb: typec: ucsi: add PMIC Glink UCSI driver Neil Armstrong
2023-03-13 9:43 ` Heikki Krogerus
2023-03-14 8:54 ` Neil Armstrong
2023-03-09 13:27 ` [PATCH v3 02/12] dt-bindings: soc: qcom: qcom,pmic-glink: document SM8450 compatible Neil Armstrong
2023-03-09 13:27 ` [PATCH v3 03/12] dt-bindings: soc: qcom: qcom,pmic-glink: document SM8550 compatible Neil Armstrong
2023-03-09 13:27 ` [PATCH v3 04/12] soc: qcom: pmic_glink: register ucsi aux device Neil Armstrong
2023-03-10 20:56 ` Dmitry Baryshkov
2023-03-09 13:27 ` [PATCH v3 05/12] dt-bindings: usb: snps,dwc3: document HS & SS OF graph ports Neil Armstrong
2023-03-16 23:03 ` Rob Herring [this message]
2023-03-09 13:27 ` [PATCH v3 06/12] arm64: dts: qcom: sm8350: add port subnodes in dwc3 node Neil Armstrong
2023-03-09 13:27 ` [PATCH v3 07/12] arm64: dts: qcom: sm8450: " Neil Armstrong
2023-03-09 13:27 ` [PATCH v3 08/12] arm64: dts: qcom: sm8550: " Neil Armstrong
2023-03-09 13:28 ` [PATCH v3 09/12] arm64: dts: qcom: sm8350-hdk: add pmic glink node Neil Armstrong
2023-03-09 13:28 ` [PATCH v3 10/12] arm64: dts: qcom: sm8450-hdk: " Neil Armstrong
2023-03-09 13:28 ` [PATCH v3 11/12] arm64: dts: qcom: sm8550-mtp: " Neil Armstrong
2023-03-09 13:28 ` [PATCH v3 12/12] arm64: defconfig: add PMIC GLINK modules Neil Armstrong
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=167900782010.4050347.7367290857102133764.robh@kernel.org \
--to=robh@kernel.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=robh+dt@kernel.org \
--cc=will@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