From: Shawn Guo <shawnguo@kernel.org>
To: Michael Turquette <mturquette@baylibre.com>
Cc: mark.rutland@arm.com, devicetree@vger.kernel.org,
Shengjiu Wang <shengjiu.wang@freescale.com>,
linux@arm.linux.org.uk, pawel.moll@arm.com,
ijc+devicetree@hellion.org.uk, linux-kernel@vger.kernel.org,
robh+dt@kernel.org, kernel@pengutronix.de, galak@codeaurora.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH V3 1/2] clk: imx6: Add SPDIF_GCLK clock in clock tree
Date: Mon, 19 Oct 2015 23:36:18 +0800 [thread overview]
Message-ID: <20151019153618.GA14709@tiger> (raw)
In-Reply-To: <20151019152807.20687.15779@quantum>
Hi Mike,
On Mon, Oct 19, 2015 at 08:28:07AM -0700, Michael Turquette wrote:
> Quoting Shengjiu Wang (2015-10-10 03:15:06)
> > Correct SPDIF clock setting issue in clock tree, the SPDIF_GCLK is also
> > one clock of SPDIF, which is missed before.
> >
> > We found an issue that imx can't enter low power mode with spdif
> > if IMX6x_CLK_SPDIF is used as the core clock of spdif. Because
> > spdif driver will register IMX6x_CLK_SPDIF clock to regmap, regmap will do
> > clk_prepare in init function, then IMX6x_CLK_SPDIF clock is prepared in probe,
> > so its parent clock (PLL clock) is prepared, the prepare operation of
> > PLL clock is to enable the clock. But I.MX needs all PLL clock is disabled,
> > then it can enter low power mode.
> >
> > So we can't use IMX6x_CLK_SPDIF as the core clock of spdif, the correct spdif
> > core clock is SPDIF_GCLK, which share same gate bit with IMX6x_CLK_SPDIF clock.
> > SPDIF_GCLK's parent clock is ipg clock.
>
> I'm confused by this. Is there really a new clock signal to be added, or
> this just to workaround some reference counting problems with regmap?
I was confused by the previous version of the patch, and asked Shengjiu
to improve the commit log, which seems still not so good. In short, the
patch does add a missing clock, and the missing of the clock is
discovered by a low-power-mode issue when SPDIF driver is enabled.
>
> >
> > Signed-off-by: Shengjiu Wang <shengjiu.wang@freescale.com>
>
> Please Cc the linux-clk@vger.kernel.org mailing list for future clock
> driver patches.
Right, should have reminded him. I will keep my eyes more closely on
this.
Shawn
next prev parent reply other threads:[~2015-10-19 15:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-10 10:15 [PATCH V3 0/2] Add SPDIF_GCLK clock in clock tree for imx6 Shengjiu Wang
2015-10-10 10:15 ` [PATCH V3 1/2] clk: imx6: Add SPDIF_GCLK clock in clock tree Shengjiu Wang
[not found] ` <ee897786f33c9ba67b560964a76485891f2f63a8.1444471684.git.shengjiu.wang-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
2015-10-19 15:28 ` Michael Turquette
2015-10-19 15:36 ` Shawn Guo [this message]
2015-10-20 10:23 ` Michael Turquette
2015-10-10 10:15 ` [PATCH V3 2/2] ARM: dts: imx6: change the core clock of spdif Shengjiu Wang
2015-10-12 14:01 ` [PATCH V3 0/2] Add SPDIF_GCLK clock in clock tree for imx6 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=20151019153618.GA14709@tiger \
--to=shawnguo@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=mark.rutland@arm.com \
--cc=mturquette@baylibre.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=shengjiu.wang@freescale.com \
/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).