devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Shawn Guo <shawnguo@kernel.org>
To: Stefan Agner <stefan@agner.ch>
Cc: kernel@pengutronix.de, sboyd@codeaurora.org,
	aisheng.dong@nxp.com, fabio.estevam@nxp.com, robh+dt@kernel.org,
	mark.rutland@arm.com, linux-arm-kernel@lists.infradead.org,
	devicetree@vger.kernel.org, linux-clk@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/2] ARM: dts: imx7: add USDHC NAND and IPG clock to SDHC instances
Date: Mon, 15 May 2017 09:53:35 +0800	[thread overview]
Message-ID: <20170515015334.GH8471@dragon> (raw)
In-Reply-To: <20170410210015.1620-2-stefan@agner.ch>

On Mon, Apr 10, 2017 at 02:00:15PM -0700, Stefan Agner wrote:
> The USDHC instances need the USDHC NAND and IPG clock in order to
> operate. Reference them properly by replacing the dummy clocks with
> the actual clocks.
> 
> Note that both clocks are currently implicitly enabled since they
> are part of the i.MX 7 clock drivers init_on list. This might
> change in the future.
> 
> Signed-off-by: Stefan Agner <stefan@agner.ch>

Applied, thanks.

  parent reply	other threads:[~2017-05-15  1:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-10 21:00 [PATCH v2 1/2] clk: imx7d: fix USDHC NAND clock Stefan Agner
2017-04-10 21:00 ` [PATCH v2 2/2] ARM: dts: imx7: add USDHC NAND and IPG clock to SDHC instances Stefan Agner
2017-04-11 20:00   ` Dong Aisheng
2017-05-15  1:53   ` Shawn Guo [this message]
     [not found] ` <20170410210015.1620-1-stefan-XLVq0VzYD2Y@public.gmane.org>
2017-04-11 19:59   ` [PATCH v2 1/2] clk: imx7d: fix USDHC NAND clock Dong Aisheng
2017-04-19 16:14   ` Stephen Boyd
2017-04-19 16:23     ` Stefan Agner
     [not found]       ` <9f0b9e83bc2a46bacb323d3ff2cfcf64-XLVq0VzYD2Y@public.gmane.org>
2017-04-19 16:44         ` 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=20170515015334.GH8471@dragon \
    --to=shawnguo@kernel.org \
    --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=robh+dt@kernel.org \
    --cc=sboyd@codeaurora.org \
    --cc=stefan@agner.ch \
    /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).