linux-arm-msm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Boyd <sboyd@codeaurora.org>
To: Kumar Gala <galak@codeaurora.org>
Cc: Georgi Djakov <gdjakov@mm-sol.com>,
	mturquette@linaro.org, linux-kernel@vger.kernel.org,
	linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH v1] clk: qcom: Add support for regmap clock dividers
Date: Thu, 02 Oct 2014 14:26:13 -0700	[thread overview]
Message-ID: <542DC2F5.7080508@codeaurora.org> (raw)
In-Reply-To: <40F825DC-F79B-43F6-9E9B-5E3879669155@codeaurora.org>

On 10/02/14 12:51, Kumar Gala wrote:
> On Oct 2, 2014, at 1:11 PM, Stephen Boyd <sboyd@codeaurora.org> wrote:
>
>> On 09/30/14 10:20, Georgi Djakov wrote:
>>> This patch expands the regmap support to allow registration of clock
>>> dividers. It just prepares for the introduction of a clkdiv driver,
>>> that will be in a separate patch.
>>> Such dividers are found in the Qualcomm PMIC chips such as PM8941,
>>> PMA8084 and others.
>> We're going to need to rework the Makefile in clk/qcom so that we only
>> build certain pieces of the "library" when we need them. Right now the
>> directory is focused entirely on mmio clock controllers and if we put
>> the pmic clocks in there then we need to figure out a way to only build
>> the pmic pieces if only the pmic driver is selected and only build the
>> mmio pieces if the mmio drivers are selected.
> Would we ever not build the mmio drivers or do you mean something else?
>
>

Yes I mean we may not build the mmio drivers.

-- 
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by The Linux Foundation

  reply	other threads:[~2014-10-02 21:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-30 17:20 [PATCH v1] clk: qcom: Add support for regmap clock dividers Georgi Djakov
2014-10-02 18:11 ` Stephen Boyd
2014-10-02 19:51   ` Kumar Gala
2014-10-02 21:26     ` Stephen Boyd [this message]
2014-10-03 15:13   ` Georgi Djakov
2014-10-03 17:49     ` 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=542DC2F5.7080508@codeaurora.org \
    --to=sboyd@codeaurora.org \
    --cc=galak@codeaurora.org \
    --cc=gdjakov@mm-sol.com \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mturquette@linaro.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).