Received: by 2002:a25:e7d8:0:0:0:0:0 with SMTP id e207csp2710117ybh; Mon, 16 Mar 2020 08:16:39 -0700 (PDT) X-Google-Smtp-Source: ADFU+vtE3bMXY9oCwKkT1vSwg6IHAOGW2MVgtHOLg8rn9ax8nq6hUjynLPipvAe2hUg3YNa0ENZ9 X-Received: by 2002:aca:37c3:: with SMTP id e186mr18182593oia.155.1584371799693; Mon, 16 Mar 2020 08:16:39 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1584371799; cv=none; d=google.com; s=arc-20160816; b=ZnRuxqtfUTbtxebhvy4fNRz/weQRN6Xa8CugEx9VF+3Hq4Q0e7kci6i647OTN5sgqQ PvrvVEa8tdBd4h15tY4aJ1Ulv2887nwOiWtrKXmqwH0IgH6RhEBQOLshx4Kfmxf0ES9v u61V/fv6rn1lnQc/t57ovgLFPr81BIpG2W14XqIIMTr+UboDNBJ9mUM7TVJOLXGg2w3q Wp3qLIAeGityGBpqDhW1XdXjVpyqrUkbGzwCB9Xjz3MDUqABA93RSqP+jaQgl2R3vBxN /hMZCU2m+0VZvfeQCPLfAnW8TS37jhXOomDL7LPZHpK2ncSJdLhdIoEDk619sfD9/K8g 76hw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:cc:to:subject :message-id:date:from:in-reply-to:references:mime-version :dkim-signature; bh=ixSqifDu9ZEefUiTiNVPd6ssEpIkNW/tDU5FVkyvqtI=; b=pDiRddDIFSV5YwDxZTFeKkhjwJ910aS4866qMV29pcIhYaeaj4Dxfe7ubSuDaJ/bWi SQ41XT+pPXzcS9PsASOss7uYOmAjRDK7ahB2WseoBeNsYcYHq90jRoTPBmyf+R+vUyM5 6iZ7MRINB4JOAV8u/0x68yJsExKcI/42HUIHzdPxHQIrTqB47CwbfB6w4cvVlaVU1Lmb 0tNFWirnEd1qv8J472LwiBugAv18mczcFf8A4ejreH+TASQlVqldXREdZ2Ix68krN7am CgtBOsIchwyUA9dlLDzpGT7ATxGSqlt+2cmAS2QrCYMTAN4mQyR0h1FxwiLiuKGtM+jV YODw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=jODSjjQ0; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id i15si142446oib.46.2020.03.16.08.16.24; Mon, 16 Mar 2020 08:16:39 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=jODSjjQ0; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1731806AbgCPPO0 (ORCPT + 99 others); Mon, 16 Mar 2020 11:14:26 -0400 Received: from mail-qt1-f195.google.com ([209.85.160.195]:38561 "EHLO mail-qt1-f195.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1731740AbgCPPOZ (ORCPT ); Mon, 16 Mar 2020 11:14:25 -0400 Received: by mail-qt1-f195.google.com with SMTP id e20so14472238qto.5; Mon, 16 Mar 2020 08:14:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=ixSqifDu9ZEefUiTiNVPd6ssEpIkNW/tDU5FVkyvqtI=; b=jODSjjQ0stgdcIWw5FmNkmjAJbTA++R+6bwpB71tEMevOeCcXd6xRVARjGV6eA0CIi ff/X0cqc3mG5P8xo3ALlOOD9yIN1eKOZnl+XS/gir3lTYF6EHyDVA05tqdoM6knnVx4v 4rqF4mQv2EsNdCTTlmer+lofMTczcxeWTk9EWJszdxQxitwWB+JzL1s/INbWDK+pVd9K O3//Ds8qzs5cZbx9oW6HTLeEP45LAAhcYTX2WDK1/mYZTi+h/Ck95PmuDg9/CEaZ3m2p BSKg7H8zJVrxufhYNbUJEFK+QPj5SmObaORY5xRgPytcv17CrRenHsis4z5cBxO8yxF4 5zCA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=ixSqifDu9ZEefUiTiNVPd6ssEpIkNW/tDU5FVkyvqtI=; b=o3Jjli9GSVx/tll2kaP4ErsfHyr42HWHh2L7q1EU+xwSRvdCgi3zRZ3QELCwM6dNY0 z2qv1xQQqhGBkJlbtPYrOR7P78WDcDWcAYu9tscvTBUcirqImigtZU0cyda1xrrTSAza MrVXg+2zHI2AhQlRVeG74fzcvaGLfCeI6WVCYxdjy3vewO4kV8pA7Be0ZJQVOuFENq9R ILzxYJAuBdFmoajw4RYLPSCOLqNT50vpCl+9Vvb7ydASkmbRrr0RAIPWi+sM5fd9RaJd IiGCdHVCJP2gssUJg5MKMvT4yMY2CvfWmMpzrPNLvgldxU9tX/zP4jxjOrWvdnj8VR7v L4YA== X-Gm-Message-State: ANhLgQ0SjnM9A+Vt5YSgDx+7bfqWWNWOAUTHkBszrH5hcUcc1/FpPeup ePkA5rlnA57jwiG+Fxn3S4MPlnQZs9QgKBzBoPE= X-Received: by 2002:ac8:683:: with SMTP id f3mr540411qth.356.1584371664321; Mon, 16 Mar 2020 08:14:24 -0700 (PDT) MIME-Version: 1.0 References: <20200316090021.52148-1-pmalani@chromium.org> <20200316090021.52148-2-pmalani@chromium.org> In-Reply-To: <20200316090021.52148-2-pmalani@chromium.org> From: Enric Balletbo Serra Date: Mon, 16 Mar 2020 16:14:13 +0100 Message-ID: Subject: Re: [PATCH v5 1/4] dt-bindings: Add cros-ec Type C port driver To: Prashant Malani Cc: linux-kernel , Benson Leung , "open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" , Enric Balletbo i Serra , Guenter Roeck , Mark Rutland , Rob Herring Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Prashant, Missatge de Prashant Malani del dia dl., 16 de mar=C3=A7 2020 a les 10:02: > > Some Chrome OS devices with Embedded Controllers (EC) can read and > modify Type C port state. > > Add an entry in the DT Bindings documentation that lists out the logical > device and describes the relevant port information, to be used by the > corresponding driver. > > Signed-off-by: Prashant Malani After Rob review, it can go together with the other patches through the chrome-platform tree. From my side: Reviewed-by: Enric Balletbo i Serra > --- > > Changes in v5: > - Updated License identifier. > - Updated DT example to be a full example. > > Changes in v4: > - Rebased on top of usb-connector.yaml, so the connector property now > directly references the usb-connector DT binding. > > .../bindings/chrome/google,cros-ec-typec.yaml | 54 +++++++++++++++++++ > 1 file changed, 54 insertions(+) > create mode 100644 Documentation/devicetree/bindings/chrome/google,cros-= ec-typec.yaml > > diff --git a/Documentation/devicetree/bindings/chrome/google,cros-ec-type= c.yaml b/Documentation/devicetree/bindings/chrome/google,cros-ec-typec.yaml > new file mode 100644 > index 0000000000000..6d7396ab8beec > --- /dev/null > +++ b/Documentation/devicetree/bindings/chrome/google,cros-ec-typec.yaml > @@ -0,0 +1,54 @@ > +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) > +%YAML 1.2 > +--- > +$id: http://devicetree.org/schemas/chrome/google,cros-ec-typec.yaml# > +$schema: http://devicetree.org/meta-schemas/core.yaml# > + > +title: Google Chrome OS EC(Embedded Controller) Type C port driver. > + > +maintainers: > + - Benson Leung > + - Prashant Malani > + > +description: > + Chrome OS devices have an Embedded Controller(EC) which has access to > + Type C port state. This node is intended to allow the host to read and > + control the Type C ports. The node for this device should be under a > + cros-ec node like google,cros-ec-spi. > + > +properties: > + compatible: > + const: google,cros-ec-typec > + > + connector: > + $ref: /schemas/connector/usb-connector.yaml# > + > +required: > + - compatible > + > +examples: > + - |+ > + spi0 { > + #address-cells =3D <1>; > + #size-cells =3D <0>; > + > + cros_ec: ec@0 { > + compatible =3D "google,cros-ec-spi"; > + reg =3D <0>; > + > + typec { > + compatible =3D "google,cros-ec-typec"; > + > + #address-cells =3D <1>; > + #size-cells =3D <0>; > + > + connector@0 { > + compatible =3D "usb-c-connector"; > + reg =3D <0>; > + power-role =3D "dual"; > + data-role =3D "dual"; > + try-power-role =3D "source"; > + }; > + }; > + }; > + }; > -- > 2.25.1.481.gfbce0eb801-goog >