From: Rob Herring <robh@kernel.org>
To: Enric Balletbo Serra <eballetbo@gmail.com>
Cc: Prashant Malani <pmalani@chromium.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Benson Leung <bleung@chromium.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
Enric Balletbo i Serra <enric.balletbo@collabora.com>,
Guenter Roeck <groeck@chromium.org>,
Mark Rutland <mark.rutland@arm.com>
Subject: Re: [PATCH v5 1/4] dt-bindings: Add cros-ec Type C port driver
Date: Fri, 20 Mar 2020 16:34:58 -0600 [thread overview]
Message-ID: <20200320223458.GA15213@bogus> (raw)
In-Reply-To: <CAFqH_50eGjYu7dHFW82CY4-EyDtq+AF+6tHCAjKbaAjW5_7WYA@mail.gmail.com>
On Mon, Mar 16, 2020 at 04:14:13PM +0100, Enric Balletbo Serra wrote:
> Hi Prashant,
>
> Missatge de Prashant Malani <pmalani@chromium.org> del dia dl., 16 de
> març 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 <pmalani@chromium.org>
>
> After Rob review, it can go together with the other patches through
> the chrome-platform tree. From my side:
LGTM, but it is dependent on usb-connector.yaml which I picked up.
Either I can take this patch or you pull my dt/next branch in.
Rob
next prev parent reply other threads:[~2020-03-20 22:35 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-16 9:00 [PATCH v5 0/4] platform/chrome: Add Type C connector class driver Prashant Malani
2020-03-16 9:00 ` [PATCH v5 1/4] dt-bindings: Add cros-ec Type C port driver Prashant Malani
2020-03-16 15:14 ` Enric Balletbo Serra
2020-03-20 22:34 ` Rob Herring [this message]
2020-03-20 22:48 ` Enric Balletbo Serra
2020-03-26 0:10 ` Benson Leung
2020-03-30 20:17 ` Rob Herring
2020-03-16 9:00 ` [PATCH v5 2/4] platform/chrome: Add Type C connector class driver Prashant Malani
2020-03-18 17:43 ` Benson Leung
2020-03-23 14:00 ` Enric Balletbo i Serra
2020-03-16 9:00 ` [PATCH v5 3/4] platform/chrome: typec: Get PD_CONTROL cmd version Prashant Malani
2020-03-16 20:08 ` Prashant Malani
2020-03-17 11:09 ` Heikki Krogerus
2020-03-16 9:00 ` [PATCH v5 4/4] platform/chrome: typec: Update port info from EC Prashant Malani
2020-03-16 20:08 ` Prashant Malani
2020-03-17 11:10 ` Heikki Krogerus
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=20200320223458.GA15213@bogus \
--to=robh@kernel.org \
--cc=bleung@chromium.org \
--cc=devicetree@vger.kernel.org \
--cc=eballetbo@gmail.com \
--cc=enric.balletbo@collabora.com \
--cc=groeck@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pmalani@chromium.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