From: shc_work@mail.ru (Alexander Shiyan)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: i.MX6Q clocks: Fix CKIH clock name
Date: Mon, 29 Jul 2013 19:42:07 +0400 [thread overview]
Message-ID: <20130729194207.bfb62131c3cfd29e5d5944ea@mail.ru> (raw)
In-Reply-To: <51F622D1.5030009@de.bosch.com>
On Mon, 29 Jul 2013 10:07:45 +0200
Dirk Behme <dirk.behme@de.bosch.com> wrote:
> On 27.07.2013 08:56, Alexander Shiyan wrote:
> > i.MX6Q have only one High-frequency reference clock (CKIH).
> > Patch removes index from CKIH and makes name according datasheet.
> >
> > Signed-off-by: Alexander Shiyan <shc_work@mail.ru>
> > ---
> > arch/arm/mach-imx/clk-imx6q.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/arch/arm/mach-imx/clk-imx6q.c b/arch/arm/mach-imx/clk-imx6q.c
> > index 9181a24..8f2a8b5 100644
> > --- a/arch/arm/mach-imx/clk-imx6q.c
> > +++ b/arch/arm/mach-imx/clk-imx6q.c
> > @@ -292,7 +292,7 @@ static void __init imx6q_clocks_init(struct device_node *ccm_node)
> >
> > clk[dummy] = imx_clk_fixed("dummy", 0);
> > clk[ckil] = imx_obtain_fixed_clock("ckil", 0);
> > - clk[ckih] = imx_obtain_fixed_clock("ckih1", 0);
> > + clk[ckih] = imx_obtain_fixed_clock("ckih", 0);
> > clk[osc] = imx_obtain_fixed_clock("osc", 0);
> >
> > np = of_find_compatible_node(NULL, NULL, "fsl,imx6q-anatop");
>
> Just for my understanding: This is a cosmetic change, only? And doesn't
> change any functionality? Correct?
Yes, but in any case this is an incomplete patch, because I forgot to change
the relevant DTS.
--
Alexander Shiyan <shc_work@mail.ru>
prev parent reply other threads:[~2013-07-29 15:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-27 6:56 [PATCH] ARM: i.MX6Q clocks: Fix CKIH clock name Alexander Shiyan
2013-07-29 8:07 ` Dirk Behme
2013-07-29 15:42 ` Alexander Shiyan [this message]
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=20130729194207.bfb62131c3cfd29e5d5944ea@mail.ru \
--to=shc_work@mail.ru \
--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).