From: Felipe Balbi <balbi@kernel.org>
To: Amelie Delaunay <amelie.delaunay@st.com>,
Minas Harutyunyan <hminas@synopsys.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>
Cc: linux-usb@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com,
Fabrice Gasnier <fabrice.gasnier@st.com>,
Benjamin Gaignard <benjamin.gaignard@st.com>,
Amelie Delaunay <amelie.delaunay@st.com>
Subject: Re: [PATCH v3 1/2] dt-bindings: usb: dwc2: add support for STM32MP15 SoCs USB OTG HS and FS
Date: Fri, 31 Jan 2020 15:36:17 +0200 [thread overview]
Message-ID: <87imkr7nou.fsf@kernel.org> (raw)
In-Reply-To: <20200124084131.23749-2-amelie.delaunay@st.com>
[-- Attachment #1: Type: text/plain, Size: 492 bytes --]
Hi,
Amelie Delaunay <amelie.delaunay@st.com> writes:
> Add the specific compatible string for the DWC2 IP found in the STM32MP15
> SoCs.
> STM32MP15 SoCs uses sensing comparators to detect Vbus valid levels and
> ID pin state. usb33d-supply described the regulator supplying Vbus and ID
> sensing comparators.
>
> Signed-off-by: Amelie Delaunay <amelie.delaunay@st.com>
This doesn't apply. dwc2 bindings is still in .txt format. I have taken
patch 2, though.
--
balbi
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2020-01-31 13:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-24 8:41 [PATCH v3 0/2] USB DWC2 support for STM32MP15 SoCs USB OTG Amelie Delaunay
2020-01-24 8:41 ` [PATCH v3 1/2] dt-bindings: usb: dwc2: add support for STM32MP15 SoCs USB OTG HS and FS Amelie Delaunay
2020-01-27 14:29 ` Rob Herring
2020-01-31 13:36 ` Felipe Balbi [this message]
2020-01-31 16:13 ` Amelie DELAUNAY
2020-01-31 20:06 ` Rob Herring
2020-01-24 8:41 ` [PATCH v3 2/2] " Amelie Delaunay
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=87imkr7nou.fsf@kernel.org \
--to=balbi@kernel.org \
--cc=amelie.delaunay@st.com \
--cc=benjamin.gaignard@st.com \
--cc=devicetree@vger.kernel.org \
--cc=fabrice.gasnier@st.com \
--cc=gregkh@linuxfoundation.org \
--cc=hminas@synopsys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=linux-usb@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@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 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.