From: Rob Herring <robh@kernel.org>
To: Jun Li <lijun.kernel@gmail.com>
Cc: Amelie DELAUNAY <amelie.delaunay@st.com>,
Heikki Krogerus <heikki.krogerus@linux.intel.com>,
Badhri Jagan Sridharan <badhri@google.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Alexandre Torgue <alexandre.torgue@st.com>,
Russell King <linux@armlinux.org.uk>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Linux USB List <linux-usb@vger.kernel.org>,
"moderated list:ARM/STM32 ARCHITECTURE"
<linux-stm32@st-md-mailman.stormreply.com>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
Fabrice Gasnier <fabrice.gasnier@st.com>
Subject: Re: [RESEND PATCH v3 1/4] dt-bindings: connector: add power-opmode optional property to usb-connector
Date: Thu, 5 Nov 2020 09:55:17 -0600 [thread overview]
Message-ID: <CAL_JsqJUVRRD=j6FTFUgUuhfLkGe5WRex+gj7N6wvu-DbwL+bA@mail.gmail.com> (raw)
In-Reply-To: <CAKgpwJU_yTTYabeMYFBqNs_6=N7gaTAc1v-+fU-dshFUrL1qVA@mail.gmail.com>
On Thu, Nov 5, 2020 at 6:24 AM Jun Li <lijun.kernel@gmail.com> wrote:
>
> Amelie DELAUNAY <amelie.delaunay@st.com> 于2020年11月5日周四 下午7:36写道:
> >
> > On 11/4/20 10:08 PM, Rob Herring wrote:
> > > On Fri, Oct 30, 2020 at 04:27:14PM +0100, Amelie DELAUNAY wrote:
> > >>
> > >>
> > >> On 10/30/20 3:29 PM, Rob Herring wrote:
> > >>> On Thu, Oct 29, 2020 at 11:49 AM Amelie DELAUNAY <amelie.delaunay@st.com> wrote:
> > >>>>
> > >>>>
> > >>>>
> > >>>> On 10/29/20 4:40 PM, Rob Herring wrote:
> > >>>>> On Thu, Oct 29, 2020 at 10:58:03AM +0100, Amelie Delaunay wrote:
> > >>>>>> Power operation mode may depends on hardware design, so, add the optional
> > >>>>>> property power-opmode for usb-c connector to select the power operation
> > >>>>>> mode capability.
> > >>>>>>
> > >>>>>> Signed-off-by: Amelie Delaunay <amelie.delaunay@st.com>
> > >>>>>> ---
> > >>>>>> .../bindings/connector/usb-connector.yaml | 18 ++++++++++++++++++
> > >>>>>> 1 file changed, 18 insertions(+)
> > >>>>>>
> > >>>>>> diff --git a/Documentation/devicetree/bindings/connector/usb-connector.yaml b/Documentation/devicetree/bindings/connector/usb-connector.yaml
> > >>>>>> index 728f82db073d..200d19c60fd5 100644
> > >>>>>> --- a/Documentation/devicetree/bindings/connector/usb-connector.yaml
> > >>>>>> +++ b/Documentation/devicetree/bindings/connector/usb-connector.yaml
> > >>>>>> @@ -93,6 +93,24 @@ properties:
> > >>>>>> - device
> > >>>>>> - dual
> > >>>>>>
> > >>>>>> + power-opmode:
> > >>>>>
> > >>>>> I've acked this version:
> > >>>>>
> > >>>>> https://lore.kernel.org/r/20201020093627.256885-2-badhri@google.com
> > >>>>>
> > >>>>
> > >>>> frs is used for Fast Role Swap defined in USB PD spec.
> > >>>> I understand it allows to get the same information but I'm wondering why
> > >>>> the property name is limited to -frs- in this case. What about a
> > >>>> non-power delivery USB-C connector ?
> > >>>
> > >>> I've got no idea. The folks that know USB-C and PD details need to get
> > >>> together and work all this out. To me, it looks like the same thing...
> > >>>
> > >>
> > >> It looks but...
> > >>
> > >> The purpose of power-opmode property is to configure the USB-C controllers,
> > >> especially the non-PD USB-C controllers to determine the power operation
> > >> mode that the Type C connector will support and will advertise through CC
> > >> pins when it has no power delivery support, whatever the power role: Sink,
> > >> Source or Dual
> > >> The management of the property is the same that data-role and power-role
> > >> properties, and done by USB Type-C Connector Class.
> > >>
> > >> new-source-frs-typec-current specifies initial current capability of the new
> > >> source when vSafe5V is applied during PD3.0 Fast Role Swap. So here, this
> > >> property is not applied at usb-c controller configuration level, but during
> > >> PD Fast Role Swap, so when the Sink become the Source.
> > >> Moreover, the related driver code says FRS can only be supported by DRP
> > >> ports. So new-source-frs-typec-current property, in addition to being
> > >> specific to PD, is also dedicated to DRP usb-c controller.
> > >> The property is managed by Type-C Port Controller Manager for PD.
> > >
> > > But it's the same set of possible values, right? So we can align the
> > > values at least.
> > >
> >
> > USB Power Delivery FRS values are defined in
> > include/dt-bindings/usb/pd.h
>
> I think this can be changed if both can be aligned.
>
> >to fit with drivers/usb/typec/tcpm/tcpm.c
> > frs_typec_current enum.
> >
> > USB-C power operation mode values are defined in
> > include/linux/usb/typec.h with typec_pwr_opmode enum and matching with
> > string values of typec_pwr_opmodes tab.
> >
> > USB PD requires USB-C.
> > USB-C doesn't requires USB PD.
> >
> > drivers/usb/typec/tcpm/tcpm.c already used typec_pwr_opmode values.
> >
> > USB PD specification Table 6-14 Fixed Supply PDO says:
> > Fast Role Swap required USB Type-C Current (see also [USB Type-C 2.0]):
> > Value | Description
> > 00b | Fast Swap not supported (default)
> > 01b | Default USB Power
> > 10b | 1.5A @ 5V
> > 11b | 3.0A @ 5V
>
> This is the value in PDO of sink, the FRS property value(or after translated)
> actually is used to compare with above value.
>
> So I think both properties can share the same "value", maybe string
> like below
>
> 10 static const char * const typec_pwr_opmodes[] = {
> 11 [TYPEC_PWR_MODE_USB] = "default",
> 12 [TYPEC_PWR_MODE_1_5A] = "1.5A",
> 13 [TYPEC_PWR_MODE_3_0A] = "3.0A",
>
> >
> > Note the *see also USB Type-C 2.0*.
> >
> > USB Type-C specification 4.6.2.1 USB Type-C Current says:
> > The USB Type-C connector uses CC pins for configuration including an
> > ability for a Source to advertise to its port partner (Sink) the amount
> > of current it shall supply:
> > • Default is the as-configured for high-power operation current value as
> > defined by the USB Specification (500 mA for USB 2.0 ports; 900 mA or
> > 1,500 mA for USB 3.2 ports in single-lane or dual-lane operation,
> > respectively)
> > • 1.5 A
> > • 3.0 A
> >
> > > Can we align the names in some way? power-opmode and frs-source-opmode
> > > or ??
>
> how about typec-power-opmode and frs-new-source-opmode
Sure.
>
> > >
> >
> > I let USB PD specialists answer.
> >
> > *frs* property fits with USB PD specification, so with USB PD protocol.
> > *power-opmode fits with USB Type-C specification, so with USB-C hardware
> > support.
> >
> > > Are these 2 properties mutually exclusive?
>
> I think yes.
This should work to express that:
allOf:
- not:
required:
- typec-power-opmode
- frs-new-source-opmode
Rob
next prev parent reply other threads:[~2020-11-05 15:55 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-29 9:58 [RESEND PATCH v3 0/4] STUSB1600 support on STM32MP15xx-DKx Amelie Delaunay
2020-10-29 9:58 ` [RESEND PATCH v3 1/4] dt-bindings: connector: add power-opmode optional property to usb-connector Amelie Delaunay
2020-10-29 15:40 ` Rob Herring
2020-10-29 16:49 ` Amelie DELAUNAY
2020-10-30 1:54 ` Jun Li
2020-10-30 14:32 ` Rob Herring
2020-10-30 14:29 ` Rob Herring
2020-10-30 15:27 ` Amelie DELAUNAY
2020-11-04 21:08 ` Rob Herring
2020-11-05 11:36 ` Amelie DELAUNAY
2020-11-05 12:23 ` Jun Li
2020-11-05 15:17 ` Amelie DELAUNAY
2020-11-05 15:55 ` Rob Herring [this message]
2020-11-06 3:10 ` Badhri Jagan Sridharan
2020-11-06 8:03 ` Amelie DELAUNAY
2020-10-29 9:58 ` [RESEND PATCH v3 2/4] dt-bindings: usb: Add DT bindings for STUSB160x Type-C controller Amelie Delaunay
2020-10-29 9:58 ` [RESEND PATCH v3 3/4] ARM: dts: stm32: add STUSB1600 Type-C using I2C4 on stm32mp15xx-dkx Amelie Delaunay
2020-10-29 9:58 ` [RESEND PATCH v3 4/4] ARM: multi_v7_defconfig: enable STUSB160X Type-C port controller support 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='CAL_JsqJUVRRD=j6FTFUgUuhfLkGe5WRex+gj7N6wvu-DbwL+bA@mail.gmail.com' \
--to=robh@kernel.org \
--cc=alexandre.torgue@st.com \
--cc=amelie.delaunay@st.com \
--cc=badhri@google.com \
--cc=devicetree@vger.kernel.org \
--cc=fabrice.gasnier@st.com \
--cc=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=lijun.kernel@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=linux-usb@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mcoquelin.stm32@gmail.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;
as well as URLs for NNTP newsgroup(s).