From: Rob Herring <robh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
To: Li Jun <jun.li-3arQi8VN3Tc@public.gmane.org>
Cc: peter.chen-3arQi8VN3Tc@public.gmane.org,
shawnguo-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org,
linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH v2 2/3] doc: usb: ci-hdrc-usb2: add property over-current-active-high
Date: Wed, 20 Jul 2016 14:10:08 -0500 [thread overview]
Message-ID: <20160720191007.GA12271@rob-hp-laptop> (raw)
In-Reply-To: <1469001762-15015-2-git-send-email-jun.li-3arQi8VN3Tc@public.gmane.org>
On Wed, Jul 20, 2016 at 04:02:41PM +0800, Li Jun wrote:
> Adding over-current-active-high to indicate the over current flag
> is high active as typically we use active low for over current
> polarity.
>
> Signed-off-by: Li Jun <jun.li-3arQi8VN3Tc@public.gmane.org>
> ---
> Documentation/devicetree/bindings/usb/ci-hdrc-usb2.txt | 2 ++
> 1 file changed, 2 insertions(+)
Acked-by: Rob Herring <robh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2016-07-20 19:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-20 8:02 [PATCH v2 1/3] doc: usb: usbmisc-imx: add imx7d compatible string Li Jun
[not found] ` <1469001762-15015-1-git-send-email-jun.li-3arQi8VN3Tc@public.gmane.org>
2016-07-20 8:02 ` [PATCH v2 2/3] doc: usb: ci-hdrc-usb2: add property over-current-active-high Li Jun
[not found] ` <1469001762-15015-2-git-send-email-jun.li-3arQi8VN3Tc@public.gmane.org>
2016-07-20 19:10 ` Rob Herring [this message]
2016-07-20 8:02 ` [PATCH v2 3/3] usb: chipidea: imx: set over current polarity per dts setting Li Jun
[not found] ` <1469001762-15015-3-git-send-email-jun.li-3arQi8VN3Tc@public.gmane.org>
2016-07-21 8:16 ` Peter Chen
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=20160720191007.GA12271@rob-hp-laptop \
--to=robh-dgejt+ai2ygdnm+yrofe0a@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=jun.li-3arQi8VN3Tc@public.gmane.org \
--cc=linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=peter.chen-3arQi8VN3Tc@public.gmane.org \
--cc=shawnguo-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.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;
as well as URLs for NNTP newsgroup(s).