From: Rob Herring <robh@kernel.org>
To: Fabio Baltieri <fabiobaltieri@chromium.org>
Cc: chrome-platform@lists.linux.dev,
"Guenter Roeck" <groeck@chromium.org>,
"Thierry Reding" <thierry.reding@gmail.com>,
"Lee Jones" <lee.jones@linaro.org>,
"Rob Herring" <robh+dt@kernel.org>,
"Benson Leung" <bleung@chromium.org>,
linux-pwm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Subject: Re: [PATCH v4 1/4] dt-bindings: add mfd/cros_ec definitions
Date: Tue, 19 Apr 2022 12:35:23 -0500 [thread overview]
Message-ID: <Yl7y29jgoB7GWWLf@robh.at.kernel.org> (raw)
In-Reply-To: <20220414092831.3717684-2-fabiobaltieri@chromium.org>
On Thu, 14 Apr 2022 09:28:28 +0000, Fabio Baltieri wrote:
> Add a dt-bindings include file for cros_ec devicetree definition, define
> a pair of special purpose PWM channels in it.
>
> Signed-off-by: Fabio Baltieri <fabiobaltieri@chromium.org>
> ---
> include/dt-bindings/mfd/cros_ec.h | 18 ++++++++++++++++++
> 1 file changed, 18 insertions(+)
> create mode 100644 include/dt-bindings/mfd/cros_ec.h
>
Acked-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2022-04-19 17:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-14 9:28 [PATCH v4 0/4] Add channel type support to pwm-cros-ec Fabio Baltieri
2022-04-14 9:28 ` [PATCH v4 1/4] dt-bindings: add mfd/cros_ec definitions Fabio Baltieri
2022-04-19 17:35 ` Rob Herring [this message]
2022-04-14 9:28 ` [PATCH v4 2/4] pwm: pwm-cros-ec: add channel type support Fabio Baltieri
2022-04-14 9:43 ` Tzung-Bi Shih
2022-04-14 9:28 ` [PATCH v4 3/4] dt-bindings: update google,cros-ec-pwm documentation Fabio Baltieri
2022-04-14 12:20 ` Rob Herring
2022-04-14 19:24 ` Fabio Baltieri
2022-04-14 9:28 ` [PATCH v4 4/4] arm64: dts: address cros-ec-pwm channels by type Fabio Baltieri
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=Yl7y29jgoB7GWWLf@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=bleung@chromium.org \
--cc=chrome-platform@lists.linux.dev \
--cc=devicetree@vger.kernel.org \
--cc=fabiobaltieri@chromium.org \
--cc=groeck@chromium.org \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=thierry.reding@gmail.com \
--cc=u.kleine-koenig@pengutronix.de \
/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).