Linux clock framework development
 help / color / mirror / Atom feed
From: Alexandre Torgue <alexandre.torgue@st.com>
To: Stephen Boyd <sboyd@kernel.org>,
	Michael Turquette <mturquette@baylibre.com>,
	<gabriel.fernandez@st.com>
Cc: <linux-clk@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	benjamin GAIGNARD <benjamin.gaignard@st.com>,
	Loic PALLARDY <loic.pallardy@st.com>
Subject: Re: [RESEND PATCH] clk: stm32: fix: stm32 clock drivers are not compiled by default
Date: Wed, 16 May 2018 10:01:56 +0200	[thread overview]
Message-ID: <503ec7d8-e493-3458-e974-5fab5649aaf8@st.com> (raw)
In-Reply-To: <152645747055.210890.12866212092853247736@swboyd.mtv.corp.google.com>



On 05/16/2018 09:57 AM, Stephen Boyd wrote:
> Quoting Alexandre Torgue (2018-05-16 00:34:21)
>>>>
>>>> Sorry I don't understand. Clock driver is mandatory to boot each
>>>> platform and depends on machine type. Do you see a use case where we
>>>> could need to disable the clock driver? (it would impose to change
>>>> devicetree to use fixed clocks and to have a booloader which configures
>>>> all PLL and clocks).
>>>
>>> No. My understanding of the patch that introduced the options was to
>>> allow the user to disable these drivers if they wanted to. I'm just
>>> reiterating the spirit of that patch. That must be wrong?
>>>
>> Actually initial patch is a mistake. You can't boot STM32 platform
>> without clock driver. This patch fixes that, and offers the possibility
>> to not build the clock driver of the machine which are not used
>> (currently all machine are selected but to reduce memory footprint you
>> could disable not used machine in defconfig).
> 
> Ok I stuck the patch into clk-fixes. Will send off to Linus tomorrow or the
> next day.
> 
Thanks Stephen

  reply	other threads:[~2018-05-16  8:01 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-03  6:40 [RESEND PATCH] clk: stm32: fix: stm32 clock drivers are not compiled by default gabriel.fernandez
2018-05-04  7:54 ` Alexandre Torgue
2018-05-05  2:45   ` Stephen Boyd
2018-05-14 12:45     ` Alexandre Torgue
2018-05-15 21:48       ` Stephen Boyd
2018-05-16  7:34         ` Alexandre Torgue
2018-05-16  7:57           ` Stephen Boyd
2018-05-16  8:01             ` Alexandre Torgue [this message]
2018-05-16  7:58 ` 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=503ec7d8-e493-3458-e974-5fab5649aaf8@st.com \
    --to=alexandre.torgue@st.com \
    --cc=benjamin.gaignard@st.com \
    --cc=gabriel.fernandez@st.com \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=loic.pallardy@st.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox