From: Fabio Estevam <festevam@gmail.com>
To: Anson Huang <Anson.Huang@nxp.com>
Cc: Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <kernel@pengutronix.de>,
Fabio Estevam <fabio.estevam@nxp.com>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>,
Michael Trimarchi <michael@amarulasolutions.com>,
Matteo Lisi <matteo.lisi@engicam.com>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
linux-clk <linux-clk@vger.kernel.org>,
NXP Linux Team <Linux-imx@nxp.com>,
"moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE"
<linux-arm-kernel@lists.infradead.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH V2 1/2] clk: imx6ul: add GPIO clock gates
Date: Sat, 2 Jun 2018 23:06:13 -0300 [thread overview]
Message-ID: <CAOMZO5D1f3=+u-51K5U0CVZdmrtZomRkHO1KR1k9N6K+ws0WLA@mail.gmail.com> (raw)
In-Reply-To: <1527990245-13619-1-git-send-email-Anson.Huang@nxp.com>
On Sat, Jun 2, 2018 at 10:44 PM, Anson Huang <Anson.Huang@nxp.com> wrote:
> i.MX6UL has GPIO clock gates in CCM CCGR,
> add them into clock tree for clock management.
>
> Signed-off-by: Anson Huang <Anson.Huang@nxp.com>
Reviewed-by: Fabio Estevam <fabio.estevam@nxp.com>
next prev parent reply other threads:[~2018-06-03 2:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-03 1:44 [PATCH V2 1/2] clk: imx6ul: add GPIO clock gates Anson Huang
2018-06-03 1:44 ` [PATCH V2 2/2] ARM: dts: imx6ul: add GPIO clocks Anson Huang
2018-06-03 2:06 ` Fabio Estevam
2018-06-03 20:57 ` Fabio Estevam
2018-06-25 3:14 ` Anson Huang
2018-06-28 0:52 ` Shawn Guo
2018-06-29 18:39 ` Stephen Boyd
2018-07-01 2:19 ` Shawn Guo
2018-07-06 17:15 ` Stephen Boyd
2018-07-11 8:28 ` Shawn Guo
2018-06-03 2:06 ` Fabio Estevam [this message]
2018-06-05 21:10 ` [PATCH V2 1/2] clk: imx6ul: add GPIO clock gates Rob Herring
2018-06-29 18:42 ` 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='CAOMZO5D1f3=+u-51K5U0CVZdmrtZomRkHO1KR1k9N6K+ws0WLA@mail.gmail.com' \
--to=festevam@gmail.com \
--cc=Anson.Huang@nxp.com \
--cc=Linux-imx@nxp.com \
--cc=devicetree@vger.kernel.org \
--cc=fabio.estevam@nxp.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=matteo.lisi@engicam.com \
--cc=michael@amarulasolutions.com \
--cc=mturquette@baylibre.com \
--cc=robh+dt@kernel.org \
--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).