public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Anson Huang <Anson.Huang@nxp.com>
Cc: shawnguo@kernel.org, s.hauer@pengutronix.de,
	kernel@pengutronix.de, fabio.estevam@nxp.com,
	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 1/2] clk: imx6sll: add GPIO LPCGs
Date: Tue, 3 Jul 2018 13:31:46 -0600	[thread overview]
Message-ID: <20180703193146.GA29496@rob-hp-laptop> (raw)
In-Reply-To: <1529649154-5724-1-git-send-email-Anson.Huang@nxp.com>

On Fri, Jun 22, 2018 at 02:32:33PM +0800, Anson Huang wrote:
> According to Reference Manual Rev.0, 06/2017,
> there are GPIO LPCGs defined in CCM CCGRs,
> add them into clock tree.
> 
> Signed-off-by: Anson Huang <Anson.Huang@nxp.com>
> ---
>  drivers/clk/imx/clk-imx6sll.c             | 6 ++++++

>  include/dt-bindings/clock/imx6sll-clock.h | 9 ++++++++-

Acked-by: Rob Herring <robh@kernel.org>

>  2 files changed, 14 insertions(+), 1 deletion(-)

  parent reply	other threads:[~2018-07-03 19:31 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
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 [this message]
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=20180703193146.GA29496@rob-hp-laptop \
    --to=robh@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=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