From: Minas Harutyunyan <Minas.Harutyunyan@synopsys.com>
To: Fabrice Gasnier <fabrice.gasnier@foss.st.com>,
"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
"robh+dt@kernel.org" <robh+dt@kernel.org>,
"alexandre.torgue@foss.st.com" <alexandre.torgue@foss.st.com>
Cc: "balbi@kernel.org" <balbi@kernel.org>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-stm32@st-md-mailman.stormreply.com"
<linux-stm32@st-md-mailman.stormreply.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"amelie.delaunay@foss.st.com" <amelie.delaunay@foss.st.com>
Subject: Re: [PATCH 2/3] usb: dwc2: stm32mp15: set otg_rev
Date: Fri, 1 Oct 2021 11:10:37 +0000 [thread overview]
Message-ID: <92611706-3847-9ba1-8d2a-2e9eba654e1d@synopsys.com> (raw)
In-Reply-To: <1631692473-8732-3-git-send-email-fabrice.gasnier@foss.st.com>
On 9/15/2021 11:54 AM, Fabrice Gasnier wrote:
> STM32MP15 complies with the OTG 2.0. Set OTG revision accordingly. It is
> useful for the of_usb_update_otg_caps() routine to check and update
> otg_rev to the lower value between DT and provided params.
>
> Signed-off-by: Fabrice Gasnier <fabrice.gasnier@foss.st.com>
Acked-by: Minas Harutyunyan <Minas.Harutyunyan@synopsys.com>
next prev parent reply other threads:[~2021-10-01 11:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-15 7:54 [PATCH 0/3] usb: dwc2: fill in gadget caps, configure it for stm32mp15 Fabrice Gasnier
2021-09-15 7:54 ` [PATCH 1/3] usb: dwc2: add otg_rev and otg_caps information for gadget driver Fabrice Gasnier
2021-10-01 11:10 ` Minas Harutyunyan
2021-10-06 6:27 ` gregkh
2021-09-15 7:54 ` [PATCH 2/3] usb: dwc2: stm32mp15: set otg_rev Fabrice Gasnier
2021-10-01 11:10 ` Minas Harutyunyan [this message]
2021-09-15 7:54 ` [PATCH 3/3] ARM: dts: stm32: set otg-rev on stm32mp151 Fabrice Gasnier
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=92611706-3847-9ba1-8d2a-2e9eba654e1d@synopsys.com \
--to=minas.harutyunyan@synopsys.com \
--cc=alexandre.torgue@foss.st.com \
--cc=amelie.delaunay@foss.st.com \
--cc=balbi@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=fabrice.gasnier@foss.st.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=linux-usb@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®