From: Stephen Boyd <sboyd@codeaurora.org>
To: Jongsung Kim <neidhard.kim@lge.com>
Cc: Michael Turquette <mturquette@baylibre.com>,
Rob Herring <robh@kernel.org>,
Maxime Ripard <maxime.ripard@free-electrons.com>,
linux-clk@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, Chanho Min <chanho.min@lge.com>
Subject: Re: [PATCH v2] clk: fixed-factor: add optional dt-binding clock-flags
Date: Wed, 24 Aug 2016 17:52:21 -0700 [thread overview]
Message-ID: <20160825005221.GK19826@codeaurora.org> (raw)
In-Reply-To: <5779C056.3020209@lge.com>
On 07/04, Jongsung Kim wrote:
> On 2016년 07월 02일 09:20, Stephen Boyd wrote:
> > Do you actually have an IC on the board that is doing some fixed
> > factor calculation? Or is this a clk driver design where we are
> > listing out each piece of an SoC's clk controller in DT?
> >
> The SoC has several PLLs of identical design, and one of them is divided
> to half and used for CPUs. The fixed-factor-clock represents the divider.
>
Ok, so it sounds like we can have the driver that registers the
CPU PLL also register the fixed factor clk? I fail to see why we
need this from DT in that case.
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2016-08-25 0:52 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-13 9:08 [RESEND][PATCH] clk: fixed-factor: set CLK_SET_RATE_PARENT Jongsung Kim
2016-06-21 0:59 ` Stephen Boyd
2016-06-24 3:49 ` [PATCH] clk: fixed-factor: add optional dt-binding clock-flags Jongsung Kim
2016-06-24 3:49 ` Jongsung Kim
2016-06-24 5:11 ` kbuild test robot
2016-06-24 5:11 ` kbuild test robot
2016-06-24 5:57 ` kbuild test robot
2016-06-24 5:57 ` kbuild test robot
2016-06-24 4:12 ` [PATCH v2] " Jongsung Kim
2016-06-24 4:12 ` Jongsung Kim
2016-06-28 20:55 ` Rob Herring
2016-06-28 21:18 ` Michael Turquette
2016-06-28 21:18 ` Michael Turquette
2016-06-29 7:06 ` Jongsung Kim
2016-07-02 0:20 ` Stephen Boyd
2016-07-04 1:48 ` Jongsung Kim
2016-08-25 0:52 ` Stephen Boyd [this message]
2016-06-29 5:04 ` Jongsung Kim
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=20160825005221.GK19826@codeaurora.org \
--to=sboyd@codeaurora.org \
--cc=chanho.min@lge.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maxime.ripard@free-electrons.com \
--cc=mturquette@baylibre.com \
--cc=neidhard.kim@lge.com \
--cc=robh@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.