From: Rob Herring <robh@kernel.org>
To: Stephen Boyd <swboyd@chromium.org>
Cc: Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Guenter Roeck <groeck@chromium.org>,
Alexandru M Stan <amstan@chromium.org>,
Matthias Kaehlcke <mka@chromium.org>,
chrome-platform@lists.linux.dev,
Benson Leung <bleung@chromium.org>,
Lee Jones <lee.jones@linaro.org>,
Craig Hesling <hesling@chromium.org>,
devicetree@vger.kernel.org, patches@lists.linux.dev,
Tom Hughes <tomhughes@chromium.org>,
Tzung-Bi Shih <tzungbi@kernel.org>,
linux-kernel@vger.kernel.org,
Douglas Anderson <dianders@chromium.org>
Subject: Re: [PATCH v6 1/2] dt-bindings: cros-ec: Reorganize property availability
Date: Mon, 27 Jun 2022 15:35:53 -0600 [thread overview]
Message-ID: <20220627213553.GA3004606-robh@kernel.org> (raw)
In-Reply-To: <20220614195144.2794796-2-swboyd@chromium.org>
On Tue, 14 Jun 2022 12:51:43 -0700, Stephen Boyd wrote:
> Various properties in the cros-ec binding only apply to different
> compatible strings. For example, the interrupts and reg property are
> required for all cros-ec devices except for the rpmsg version. Add some
> conditions to update the availability of properties so that they can't
> be used with compatibles that don't support them.
>
> Cc: Rob Herring <robh@kernel.org>
> Cc: Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>
> Cc: <devicetree@vger.kernel.org>
> Cc: <chrome-platform@lists.linux.dev>
> Cc: Guenter Roeck <groeck@chromium.org>
> Cc: Douglas Anderson <dianders@chromium.org>
> Cc: Craig Hesling <hesling@chromium.org>
> Cc: Tom Hughes <tomhughes@chromium.org>
> Cc: Alexandru M Stan <amstan@chromium.org>
> Cc: Tzung-Bi Shih <tzungbi@kernel.org>
> Cc: Matthias Kaehlcke <mka@chromium.org>
> Cc: Benson Leung <bleung@chromium.org>
> Cc: Lee Jones <lee.jones@linaro.org>
> Signed-off-by: Stephen Boyd <swboyd@chromium.org>
> ---
> .../bindings/chrome/google,cros-ec-typec.yaml | 1 +
> .../bindings/extcon/extcon-usbc-cros-ec.yaml | 1 +
> .../i2c/google,cros-ec-i2c-tunnel.yaml | 1 +
> .../bindings/mfd/google,cros-ec.yaml | 29 +++++++++++++------
> .../bindings/pwm/google,cros-ec-pwm.yaml | 1 +
> .../regulator/google,cros-ec-regulator.yaml | 1 +
> .../bindings/sound/google,cros-ec-codec.yaml | 1 +
> 7 files changed, 26 insertions(+), 9 deletions(-)
>
Reviewed-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2022-06-27 21:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-14 19:51 [PATCH v6 0/2] dt-bindings: cros-ec: Update for fingerprint devices Stephen Boyd
2022-06-14 19:51 ` [PATCH v6 1/2] dt-bindings: cros-ec: Reorganize property availability Stephen Boyd
2022-06-14 22:41 ` Doug Anderson
2022-06-16 0:39 ` Stephen Boyd
2022-06-27 21:35 ` Rob Herring [this message]
2022-06-14 19:51 ` [PATCH v6 2/2] dt-bindings: cros-ec: Add ChromeOS fingerprint binding Stephen Boyd
2022-06-14 22:41 ` Doug Anderson
2022-06-16 0:50 ` Stephen Boyd
2022-06-27 21:57 ` Rob Herring
2022-06-29 7:29 ` Stephen Boyd
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=20220627213553.GA3004606-robh@kernel.org \
--to=robh@kernel.org \
--cc=amstan@chromium.org \
--cc=bleung@chromium.org \
--cc=chrome-platform@lists.linux.dev \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=groeck@chromium.org \
--cc=hesling@chromium.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mka@chromium.org \
--cc=patches@lists.linux.dev \
--cc=swboyd@chromium.org \
--cc=tomhughes@chromium.org \
--cc=tzungbi@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).