From: Prashant Malani <pmalani@chromium.org>
To: linux-kernel@vger.kernel.org, robh+dt@kernel.org
Cc: heikki.krogerus@linux.intel.com,
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>
Subject: Re: [PATCH v3 1/2] dt-bindings: chrome: Add cros-ec-typec mux props
Date: Fri, 12 Jun 2020 10:16:09 -0700 [thread overview]
Message-ID: <20200612171609.GA255826@google.com> (raw)
In-Reply-To: <20200519214604.180036-1-pmalani@chromium.org>
Hi,
From the discussion in [1], it looks like reconciling ACPI and DT
bindings for these properties to be identical is challenging.
Let's drop this patch, and move forward with the Patch 2/2 in this
series [2] alone.
We'll continue the discussion about how we can add these properties to
devicetree bindings in a conformant way.
Thanks everyone,
-Prashant,
[1]:
https://lore.kernel.org/lkml/CAL_Jsq+ORkzHchpD0qsH97zDJzXGj3jWy8=orXSVhNQd4kr9Kg@mail.gmail.com/T/#t
[2]: https://lkml.org/lkml/2020/5/19/1219
(Trimming text);
On Tue, May 19, 2020 at 02:46:02PM -0700, Prashant Malani wrote:
> Add properties for mode, orientation and USB data role switches for
> Type C connectors. When available, these will allow the Type C connector
> class port driver to configure the various switches according to USB PD
> information (like orientation, alt mode etc.) provided by the Chrome OS
> EC controller.
>
> Signed-off-by: Prashant Malani <pmalani@chromium.org>
> Acked-by: Benson Leung <bleung@chromium.org>
> ---
>
> Changes in v3:
> - Fixed Acked-by tag typo.
>
> Changes in v2:
> - Added more text to the switch descriptions, explaining their purpose,
> and relation to the Type C connector class framework.
>
> .../bindings/chrome/google,cros-ec-typec.yaml | 40 ++++++++++++++++++-
> 1 file changed, 39 insertions(+), 1 deletion(-)
>
prev parent reply other threads:[~2020-06-12 17:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-19 21:46 [PATCH v3 1/2] dt-bindings: chrome: Add cros-ec-typec mux props Prashant Malani
2020-05-19 21:46 ` [PATCH v3 2/2] platform/chrome: typec: Register Type C switches Prashant Malani
2020-06-25 11:59 ` Enric Balletbo i Serra
2020-05-29 19:28 ` [PATCH v3 1/2] dt-bindings: chrome: Add cros-ec-typec mux props Prashant Malani
2020-06-12 17:16 ` Prashant Malani [this message]
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=20200612171609.GA255826@google.com \
--to=pmalani@chromium.org \
--cc=bleung@chromium.org \
--cc=devicetree@vger.kernel.org \
--cc=enric.balletbo@collabora.com \
--cc=groeck@chromium.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--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 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).