From: b32955@freescale.com (Huang Shijie)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] ARM: clk: imx: add a new helper which can re-parent the clock
Date: Mon, 26 May 2014 14:47:46 +0800 [thread overview]
Message-ID: <20140526064745.GA31472@shlinux1.ap.freescale.net> (raw)
In-Reply-To: <20140526080120.GE2650@dragon>
On Mon, May 26, 2014 at 04:01:21PM +0800, Shawn Guo wrote:
> On Mon, May 26, 2014 at 01:20:32PM +0800, Huang Shijie wrote:
> > The clocks for Quadspi controller may be different when different
> > NOR flashes are connected to the board.
> >
> > This patch adds a new helper to register the clock which needs the
> > re-parent capability.
> >
> > Signed-off-by: Huang Shijie <b32955@freescale.com>
>
> So what you need is to register a mux clock without
> CLK_SET_RATE_NO_REPARENT flag, right?
yes.
Without this fixed flag, I can pass the CLK_SET_RATE_PARENT in the "flags".
>
> I'm think about just dropping the flag from imx_clk_mux() and
> imx_clk_mux_flags(), since this is the default behavior of basic mux
> clock, and I doubt dropping the flag will cause problem for mux clocks
> on i.MX.
this is what i was worry about.
So i do not change the imx_clk_mux/imx_clk_mux_flags, and add new helper which
has the minimum impact to the current code.
thanks
Huang Shijie
next prev parent reply other threads:[~2014-05-26 6:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-26 5:20 [PATCH 1/2] ARM: clk: imx: add a new helper which can re-parent the clock Huang Shijie
2014-05-26 5:20 ` [PATCH 2/2] ARM: clk-imx6sx: register the qspi's clock with re-parent capability Huang Shijie
2014-05-26 6:54 ` [PATCH 1/2] ARM: clk: imx: add a new helper which can re-parent the clock Alexander Shiyan
2014-05-26 6:03 ` Huang Shijie
2014-05-26 7:42 ` Alexander Shiyan
2014-05-26 8:01 ` Shawn Guo
2014-05-26 6:47 ` Huang Shijie [this message]
2014-05-26 8:11 ` Shawn Guo
2014-05-26 6:58 ` Huang Shijie
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=20140526064745.GA31472@shlinux1.ap.freescale.net \
--to=b32955@freescale.com \
--cc=linux-arm-kernel@lists.infradead.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).