From: Shawn Guo <shawnguo@kernel.org>
To: Anson Huang <Anson.Huang@nxp.com>
Cc: s.hauer@pengutronix.de, kernel@pengutronix.de,
fabio.estevam@nxp.com, robh+dt@kernel.org, mark.rutland@arm.com,
mturquette@baylibre.com, sboyd@kernel.org, aisheng.dong@nxp.com,
ping.bai@nxp.com, Linux-imx@nxp.com,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-clk@vger.kernel.org
Subject: Re: [PATCH 2/2] ARM: dts: imx6sll: add gpio clocks
Date: Thu, 12 Jul 2018 10:52:04 +0800 [thread overview]
Message-ID: <20180712025203.GQ6959@dragon> (raw)
In-Reply-To: <1529649154-5724-2-git-send-email-Anson.Huang@nxp.com>
On Fri, Jun 22, 2018 at 02:32:34PM +0800, Anson Huang wrote:
> i.MX6SLL has GPIO clock gates in CCM CCGR, add
> clock property for GPIO driver to make sure all
> GPIO banks work as expected.
>
> Signed-off-by: Anson Huang <Anson.Huang@nxp.com>
I tried to create a topic branch for this patch with dependent clk
branch merged in. But it turns out to be difficult and not worth the
effort, because too many imx6sll patches need to be moved out from
imx/dt branch, and some imx6sll changes are mixed with other SoCs.
Let's apply this in next cycle. Ping me when 4.19-rc1 is available.
Shawn
next prev parent reply other threads:[~2018-07-12 2:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-22 6:32 [PATCH 1/2] clk: imx6sll: add GPIO LPCGs Anson Huang
2018-06-22 6:32 ` [PATCH 2/2] ARM: dts: imx6sll: add gpio clocks Anson Huang
2018-06-23 15:49 ` Fabio Estevam
2018-07-12 2:52 ` Shawn Guo [this message]
2018-08-29 1:12 ` Anson Huang
2018-08-29 14:30 ` Shawn Guo
2018-06-23 15:48 ` [PATCH 1/2] clk: imx6sll: add GPIO LPCGs Fabio Estevam
2018-07-03 19:31 ` Rob Herring
2018-07-06 20:58 ` Stephen Boyd
2018-07-11 8:43 ` Shawn Guo
2018-07-11 16:33 ` Stephen Boyd
2018-07-12 2:25 ` 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=20180712025203.GQ6959@dragon \
--to=shawnguo@kernel.org \
--cc=Anson.Huang@nxp.com \
--cc=Linux-imx@nxp.com \
--cc=aisheng.dong@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=mturquette@baylibre.com \
--cc=ping.bai@nxp.com \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=sboyd@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).