From: Rob Herring <robh@kernel.org>
To: Johan Jonker <jbx6244@gmail.com>
Cc: daniel.lezcano@linaro.org, devicetree@vger.kernel.org,
p.zabel@pengutronix.de, amitk@kernel.org, robh+dt@kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, rui.zhang@intel.com,
heiko@sntech.de, linux-pm@vger.kernel.org,
linux-rockchip@lists.infradead.org
Subject: Re: [PATCH v2 1/4] dt-bindings: thermal: allow more resets for tsadc node in rockchip-thermal.yaml
Date: Wed, 6 Oct 2021 16:13:54 -0500 [thread overview]
Message-ID: <YV4RkjIEMUKlWK4z@robh.at.kernel.org> (raw)
In-Reply-To: <20210930110517.14323-1-jbx6244@gmail.com>
On Thu, 30 Sep 2021 13:05:14 +0200, Johan Jonker wrote:
> The tsadc node in rk356x.dtsi has more resets defined then currently
> allowed by rockchip-thermal.yaml, so fix that in the documentation.
> The driver now uses the devm_reset_control_array_get() function,
> so reset-names is no longer required, but keep it for legacy reasons.
>
> Signed-off-by: Johan Jonker <jbx6244@gmail.com>
> ---
>
> Changed V2:
> Remove deprecated
> ---
> .../devicetree/bindings/thermal/rockchip-thermal.yaml | 7 +++++--
> 1 file changed, 5 insertions(+), 2 deletions(-)
>
Reviewed-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2021-10-06 21:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-30 11:05 [PATCH v2 1/4] dt-bindings: thermal: allow more resets for tsadc node in rockchip-thermal.yaml Johan Jonker
2021-09-30 11:05 ` [PATCH v2 2/4] dt-bindings: thermal: remove redundant comments from rockchip-thermal.yaml Johan Jonker
2021-09-30 11:05 ` [PATCH v2 3/4] thermal: rockchip_thermal: allow more resets for tsadc node Johan Jonker
2021-09-30 11:05 ` [PATCH v2 4/4] arm64: dts: fix resets in tsadc node for rk356x.dtsi Johan Jonker
2021-10-06 21:13 ` Rob Herring [this message]
2021-10-18 18:20 ` (subset) [PATCH v2 1/4] dt-bindings: thermal: allow more resets for tsadc node in rockchip-thermal.yaml Heiko Stuebner
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=YV4RkjIEMUKlWK4z@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=amitk@kernel.org \
--cc=daniel.lezcano@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=jbx6244@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=p.zabel@pengutronix.de \
--cc=robh+dt@kernel.org \
--cc=rui.zhang@intel.com \
/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