From: Rob Herring <robh@kernel.org>
To: Anson.Huang@nxp.com
Cc: rui.zhang@intel.com, edubezval@gmail.com,
daniel.lezcano@linaro.org, robh+dt@kernel.org,
mark.rutland@arm.com, shawnguo@kernel.org,
s.hauer@pengutronix.de, kernel@pengutronix.de,
festevam@gmail.com, mturquette@baylibre.com, sboyd@kernel.org,
l.stach@pengutronix.de, abel.vesa@nxp.com,
andrew.smirnov@gmail.com, angus@akkea.ca, ccaione@baylibre.com,
agx@sigxcpu.org, leonard.crestez@nxp.com,
linux-pm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-clk@vger.kernel.org,
Linux-imx@nxp.com
Subject: Re: [PATCH 3/6] dt-bindings: thermal: qoriq: Add optional clocks property
Date: Mon, 22 Jul 2019 17:55:35 -0600 [thread overview]
Message-ID: <20190722235535.GA2063@bogus> (raw)
In-Reply-To: <20190705045612.27665-3-Anson.Huang@nxp.com>
On Fri, 5 Jul 2019 12:56:09 +0800, Anson.Huang@nxp.com wrote:
> From: Anson Huang <Anson.Huang@nxp.com>
>
> Some platforms have clock control for TMU, add optional
> clocks property to the binding doc.
>
> Signed-off-by: Anson Huang <Anson.Huang@nxp.com>
> ---
> Documentation/devicetree/bindings/thermal/qoriq-thermal.txt | 1 +
> 1 file changed, 1 insertion(+)
>
Reviewed-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2019-07-22 23:55 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-05 4:56 [PATCH 1/6] thermal: qoriq: Use devm_platform_ioremap_resource() instead of of_iomap() Anson.Huang
2019-07-05 4:56 ` [PATCH 2/6] thermal: qoriq: Use __maybe_unused instead of #if CONFIG_PM_SLEEP Anson.Huang
2019-07-05 4:56 ` [PATCH 3/6] dt-bindings: thermal: qoriq: Add optional clocks property Anson.Huang
2019-07-22 23:55 ` Rob Herring [this message]
2019-07-05 4:56 ` [PATCH 4/6] thermal: qoriq: Add clock operations Anson.Huang
2019-07-29 8:12 ` Guido Günther
2019-07-29 8:40 ` Anson Huang
2019-07-05 4:56 ` [PATCH 5/6] clk: imx8mq: Remove CLK_IS_CRITICAL flag for IMX8MQ_CLK_TMU_ROOT Anson.Huang
2019-07-05 7:01 ` Abel Vesa
2019-07-22 21:31 ` Stephen Boyd
2019-07-23 2:50 ` Shawn Guo
2019-07-26 22:26 ` Daniel Baluta
2019-07-27 6:19 ` Anson Huang
2019-07-27 6:33 ` Daniel Baluta
2019-07-27 16:17 ` Abel Vesa
2019-07-29 1:29 ` Anson Huang
2019-07-29 6:51 ` Daniel Baluta
2019-07-29 7:14 ` Anson Huang
2019-07-29 7:20 ` Daniel Baluta
2019-07-29 7:21 ` Daniel Baluta
2019-07-29 7:49 ` Anson Huang
2019-07-29 8:13 ` Daniel Baluta
2019-07-27 18:26 ` Guido Günther
2019-07-27 20:17 ` Fabio Estevam
2019-07-28 7:58 ` Guido Günther
2019-07-28 15:24 ` Fabio Estevam
2019-07-05 4:56 ` [PATCH 6/6] arm64: dts: imx8mq: Add clock for TMU node Anson.Huang
2019-07-23 2:51 ` Shawn Guo
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=20190722235535.GA2063@bogus \
--to=robh@kernel.org \
--cc=Anson.Huang@nxp.com \
--cc=Linux-imx@nxp.com \
--cc=abel.vesa@nxp.com \
--cc=agx@sigxcpu.org \
--cc=andrew.smirnov@gmail.com \
--cc=angus@akkea.ca \
--cc=ccaione@baylibre.com \
--cc=daniel.lezcano@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=edubezval@gmail.com \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=l.stach@pengutronix.de \
--cc=leonard.crestez@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mturquette@baylibre.com \
--cc=robh+dt@kernel.org \
--cc=rui.zhang@intel.com \
--cc=s.hauer@pengutronix.de \
--cc=sboyd@kernel.org \
--cc=shawnguo@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).