All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marc Gonzalez <marc.w.gonzalez@free.fr>
To: Stephen Boyd <sboyd@kernel.org>,
	Bjorn Andersson <bjorn.andersson@linaro.org>
Cc: Michael Turquette <mturquette@baylibre.com>,
	linux-clk <linux-clk@vger.kernel.org>,
	MSM <linux-arm-msm@vger.kernel.org>,
	Georgi Djakov <georgi.djakov@linaro.org>,
	Amit Kucheria <amit.kucheria@linaro.org>
Subject: Re: [PATCH v1] clk: qcom: msm8916: Don't build support by default
Date: Wed, 12 Jun 2019 22:03:22 +0200	[thread overview]
Message-ID: <dc11a192-f8c6-f90f-8214-303291b03258@free.fr> (raw)
In-Reply-To: <20190612194915.8F5DD20866@mail.kernel.org>

On 12/06/2019 21:49, Stephen Boyd wrote:

> Quoting Bjorn Andersson (2019-06-12 12:13:47)
>
>> On Wed 12 Jun 08:52 PDT 2019, Marc Gonzalez wrote:
>>
>>> Build QCOM_A53PLL and QCOM_CLK_APCS_MSM8916 by default only when
>>> we're building MSM_GCC_8916.
>>>
>>> Signed-off-by: Marc Gonzalez <marc.w.gonzalez@free.fr>
>>
>> Not sure why these are default at all.
>>
>> But both drivers are used on platforms other than 8916 as well, so if
>> anything a fix would be to rename the APCS_MSM8916 to something more
>> generic (such as QCOM_CLK_APCS_GLOBAL) - but then the content should be
>> updated and the APCS mailbox driver as well...
> 
> I don't see any use in being this specific. I'd prefer we just leave
> this at the ARCH_FOO config level and not try anything more fancy.

As Bjorn pointed out, why do these default "on" at all?

https://elixir.bootlin.com/linux/latest/source/drivers/clk/qcom/Kconfig

There are dozens of config knobs in drivers/clk/qcom/Kconfig
and only these two force the default.

Let's remove the default altogether.

Regards.

  reply	other threads:[~2019-06-12 20:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-12 15:52 [PATCH v1] clk: qcom: msm8916: Don't build support by default Marc Gonzalez
2019-06-12 19:13 ` Bjorn Andersson
2019-06-12 19:49   ` Stephen Boyd
2019-06-12 20:03     ` Marc Gonzalez [this message]
2019-06-12 22:42       ` Stephen Boyd
2019-06-13 15:05   ` Marc Gonzalez

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=dc11a192-f8c6-f90f-8214-303291b03258@free.fr \
    --to=marc.w.gonzalez@free.fr \
    --cc=amit.kucheria@linaro.org \
    --cc=bjorn.andersson@linaro.org \
    --cc=georgi.djakov@linaro.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=mturquette@baylibre.com \
    --cc=sboyd@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.