From: Rob Herring <robh@kernel.org>
To: Roger Quadros <rogerq@ti.com>
Cc: kishon@ti.com, aniljoy@cadence.com, adouglas@cadence.com,
nsekhar@ti.com, jsarha@ti.com, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH v3 2/3] dt-bindings: phy: ti,phy-j721e-wiz: Add Type-C dir GPIO
Date: Fri, 25 Oct 2019 15:06:04 -0500 [thread overview]
Message-ID: <20191025200603.GA10839@bogus> (raw)
In-Reply-To: <20191024114042.30237-3-rogerq@ti.com>
On Thu, Oct 24, 2019 at 02:40:41PM +0300, Roger Quadros wrote:
> This is an optional GPIO, if specified will be used to
> swap lane 0 and lane 1 based on GPIO status. This is required
> to achieve plug flip support for USB Type-C.
>
> Type-C companions typically need some time after the cable is
> plugged before and before they reflect the correct status of
> Type-C plug orientation on the DIR line.
>
> Type-C Spec specifies CC attachment debounce time (tCCDebounce)
> of 100 ms (min) to 200 ms (max).
>
> Allow the DT node to specify the time (in ms) that we need
> to wait before sampling the DIR line.
>
> Signed-off-by: Roger Quadros <rogerq@ti.com>
> Cc: Rob Herring <robh@kernel.org>
> ---
> .../devicetree/bindings/phy/ti,phy-j721e-wiz.yaml | 15 +++++++++++++++
> 1 file changed, 15 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/phy/ti,phy-j721e-wiz.yaml b/Documentation/devicetree/bindings/phy/ti,phy-j721e-wiz.yaml
> index 8a1eccee6c1d..5dab0010bcdf 100644
> --- a/Documentation/devicetree/bindings/phy/ti,phy-j721e-wiz.yaml
> +++ b/Documentation/devicetree/bindings/phy/ti,phy-j721e-wiz.yaml
> @@ -53,6 +53,21 @@ properties:
> assigned-clock-parents:
> maxItems: 2
>
> + typec-dir-gpios:
TI specific or could be generic?
> + maxItems: 1
> + description:
> + GPIO to signal Type-C cable orientation for lane swap.
> + If GPIO is active, lane 0 and lane 1 of SERDES will be swapped to
> + achieve the funtionality of an exernal type-C plug flip mux.
s/exernal/external/
> +
> + typec-dir-debounce:
Needs '-ms' suffix.
> + $ref: '/schemas/types.yaml#/definitions/uint32'
then you can drop this because standard units have type already.
> + description:
> + Number of milliseconds to wait before sampling
> + typec-dir-gpio. If not specified, the GPIO will be sampled ASAP.
> + Type-C spec states minimum CC pin debounce of 100 ms and maximum
> + of 200 ms.
Express this as constraints:
minimum: 100
maximum: 200
default: ???
If the spec minimum is 100ms, then doesn't sampling ASAP violate the
spec?
> +
> patternProperties:
> "^pll[0|1]_refclk$":
> type: object
> --
> Texas Instruments Finland Oy, Porkkalankatu 22, 00180 Helsinki.
> Y-tunnus/Business ID: 0615521-4. Kotipaikka/Domicile: Helsinki
>
next prev parent reply other threads:[~2019-10-25 20:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-24 11:40 [PATCH v3 0/3] phy: cadence: j721e-wiz: Add Type-C plug flip support Roger Quadros
2019-10-24 11:40 ` [PATCH v3 1/3] phy: cadence: Sierra: add phy_reset hook Roger Quadros
2019-10-24 11:40 ` [PATCH v3 2/3] dt-bindings: phy: ti,phy-j721e-wiz: Add Type-C dir GPIO Roger Quadros
2019-10-25 20:06 ` Rob Herring [this message]
2019-10-28 8:32 ` Roger Quadros
2019-10-24 11:40 ` [PATCH v3 3/3] phy: ti: j721e-wiz: Manage typec-gpio-dir Roger Quadros
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=20191025200603.GA10839@bogus \
--to=robh@kernel.org \
--cc=adouglas@cadence.com \
--cc=aniljoy@cadence.com \
--cc=devicetree@vger.kernel.org \
--cc=jsarha@ti.com \
--cc=kishon@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nsekhar@ti.com \
--cc=rogerq@ti.com \
/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