From: Rob Herring <robh@kernel.org>
To: Peter Chen <peter.chen@nxp.com>
Cc: "linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
dl-linux-imx <linux-imx@nxp.com>,
"robh+dt@kernel.org" <robh+dt@kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"frieder.schrempf@exceet.de" <frieder.schrempf@exceet.de>,
"festevam@gmail.com" <festevam@gmail.com>
Subject: [v5,4/4] doc: usb: ci-hdrc-usb2: Add pinctrl properties for HSIC pin groups
Date: Mon, 17 Dec 2018 15:29:22 -0600 [thread overview]
Message-ID: <20181217212922.GA27338@bogus> (raw)
On Tue, 11 Dec 2018 02:09:04 +0000, Peter Chen wrote:
> For USB HSIC, the data and strobe pin needs to be pulled down
> at default, we consider it as "idle" state. When the USB host
> is ready to be used, the strobe pin needs to be pulled up,
> we consider it as "active" state.
>
> Signed-off-by: Peter Chen <peter.chen@nxp.com>
> ---
> .../devicetree/bindings/usb/ci-hdrc-usb2.txt | 31 +++++++++++++++++++++-
> 1 file changed, 30 insertions(+), 1 deletion(-)
>
Reviewed-by: Rob Herring <robh@kernel.org>
WARNING: multiple messages have this Message-ID (diff)
From: Rob Herring <robh@kernel.org>
To: Peter Chen <peter.chen@nxp.com>
Cc: "linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
dl-linux-imx <linux-imx@nxp.com>,
"robh+dt@kernel.org" <robh+dt@kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"frieder.schrempf@exceet.de" <frieder.schrempf@exceet.de>,
"festevam@gmail.com" <festevam@gmail.com>
Subject: Re: [PATCH v5 4/4] doc: usb: ci-hdrc-usb2: Add pinctrl properties for HSIC pin groups
Date: Mon, 17 Dec 2018 15:29:22 -0600 [thread overview]
Message-ID: <20181217212922.GA27338@bogus> (raw)
In-Reply-To: <20181211020624.9433-5-peter.chen@nxp.com>
On Tue, 11 Dec 2018 02:09:04 +0000, Peter Chen wrote:
> For USB HSIC, the data and strobe pin needs to be pulled down
> at default, we consider it as "idle" state. When the USB host
> is ready to be used, the strobe pin needs to be pulled up,
> we consider it as "active" state.
>
> Signed-off-by: Peter Chen <peter.chen@nxp.com>
> ---
> .../devicetree/bindings/usb/ci-hdrc-usb2.txt | 31 +++++++++++++++++++++-
> 1 file changed, 30 insertions(+), 1 deletion(-)
>
Reviewed-by: Rob Herring <robh@kernel.org>
next reply other threads:[~2018-12-17 21:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-17 21:29 Rob Herring [this message]
2018-12-17 21:29 ` [PATCH v5 4/4] doc: usb: ci-hdrc-usb2: Add pinctrl properties for HSIC pin groups Rob Herring
-- strict thread matches above, loose matches on Subject: below --
2018-12-11 2:09 [v5,4/4] " Peter Chen
2018-12-11 2:09 ` [PATCH v5 4/4] " Peter Chen
2018-12-11 2:09 [v5,3/4] usb: chipidea: host: override ehci->hub_control Peter Chen
2018-12-11 2:09 ` [PATCH v5 3/4] " Peter Chen
2018-12-11 2:08 [v5,2/4] usb: chipidea: imx: add HSIC support Peter Chen
2018-12-11 2:08 ` [PATCH v5 2/4] " Peter Chen
2019-09-13 9:47 ` [v5,2/4] " André Draszik
2019-09-16 2:31 ` Peter Chen
2018-12-11 2:08 [v5,1/4] usb: chipidea: add flag for imx hsic implementation Peter Chen
2018-12-11 2:08 ` [PATCH v5 1/4] " Peter Chen
2018-12-11 2:08 [PATCH v5 0/4] usb: chipidea: imx: add HSIC support 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=20181217212922.GA27338@bogus \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=frieder.schrempf@exceet.de \
--cc=linux-imx@nxp.com \
--cc=linux-usb@vger.kernel.org \
--cc=peter.chen@nxp.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.