From: Alexandre Torgue <alexandre.torgue@st.com>
To: Stephen Boyd <sboyd@codeaurora.org>
Cc: Gabriel FERNANDEZ <gabriel.fernandez@st.com>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Russell King <linux@armlinux.org.uk>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Michael Turquette <mturquette@baylibre.com>,
Nicolas Pitre <nico@linaro.org>, Arnd Bergmann <arnd@arndb.de>,
"daniel.thompson@linaro.org" <daniel.thompson@linaro.org>,
"andrea.merello@gmail.com" <andrea.merello@gmail.com>,
"radoslaw.pietrzyk@gmail.com" <radoslaw.pietrzyk@gmail.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-clk@vger.kernel.org" <linux-clk@vger.kernel.org>,
"kernel@stlinux.com" <kernel@stlinux.com>,
Ludovic BARRE <ludovic.barre@st.com>,
Olivier BIDEAU <olivier.bideau@st.com>,
Amelie DELAUNAY <amelie.delaunay@st.com>
Subject: Re: [PATCH v4 1/9] clk: stm32f4: Update DT bindings documentation
Date: Tue, 10 Jan 2017 11:08:55 +0100 [thread overview]
Message-ID: <0031c2ec-5fc8-4abf-29ef-5039b0508931@st.com> (raw)
In-Reply-To: <20170109193312.GN17126@codeaurora.org>
On 01/09/2017 08:33 PM, Stephen Boyd wrote:
> On 01/09, Alexandre Torgue wrote:
>> Hi Stephen,
>>
>> On 12/22/2016 01:10 AM, Stephen Boyd wrote:
>>> On 12/13, gabriel.fernandez@st.com wrote:
>>>> From: Gabriel Fernandez <gabriel.fernandez@st.com>
>>>>
>>>> Creation of dt include file for specific stm32f4 clocks.
>>>> These specific clocks are not derived from system clock (SYSCLOCK)
>>>> We should use index 1 to use these clocks in DT.
>>>> e.g. <&rcc 1 CLK_LSI>
>>>>
>>>> Signed-off-by: Gabriel Fernandez <gabriel.fernandez@st.com>
>>>> Acked-by: Rob Herring <robh@kernel.org>
>>>> ---
>>>
>>> Applied to clk-stm32f4 and merged into clk-next.
>>>
>>
>> I'm preparing pull request branch for STM32 DT part. This patch is
>> also requested to build correctly DT patches. Do you know how could
>> we synchronize our pull request ?
>>
>
> clk-stm32f4 is stable and not going to be rebased, so you're good
> to base patches on it and send it off to arm-soc if the arm-soc
> maintainers agree to it. You can also base off an earlier part of
> the branch if you only need this first patch for example.
>
I will base my DT branch from 4.10-rc1 + this commit (seen with Arnd)
Thanks
next prev parent reply other threads:[~2017-01-10 10:09 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-13 14:20 [PATCH v4 0/9] STM32F4 missing clocks gabriel.fernandez
2016-12-13 14:20 ` [PATCH v4 1/9] clk: stm32f4: Update DT bindings documentation gabriel.fernandez
2016-12-22 0:10 ` Stephen Boyd
2017-01-09 16:28 ` Alexandre Torgue
2017-01-09 19:33 ` Stephen Boyd
2017-01-10 10:08 ` Alexandre Torgue [this message]
2016-12-13 14:20 ` [PATCH v4 2/9] clk: stm32f4: Add PLL_I2S & PLL_SAI for STM32F429/469 boards gabriel.fernandez
2016-12-22 0:10 ` Stephen Boyd
2016-12-13 14:20 ` [PATCH v4 3/9] clk: stm32f4: Add post divisor for I2S & SAI PLLs gabriel.fernandez
2016-12-22 0:11 ` Stephen Boyd
2016-12-13 14:20 ` [PATCH v4 4/9] clk: stm32f4: Add lcd-tft clock gabriel.fernandez
2016-12-22 0:11 ` Stephen Boyd
2016-12-13 14:20 ` [PATCH v4 5/9] clk: stm32f4: Add I2S clock gabriel.fernandez
2016-12-22 0:11 ` Stephen Boyd
2016-12-13 14:20 ` [PATCH v4 6/9] clk: stm32f4: Add SAI clocks gabriel.fernandez
2016-12-22 0:11 ` Stephen Boyd
2016-12-13 14:20 ` [PATCH v4 7/9] clk: stm32f4: SDIO & 48Mhz clock management for STM32F469 board gabriel.fernandez
2016-12-22 0:11 ` Stephen Boyd
2016-12-13 14:20 ` [PATCH v4 8/9] ARM: dts: stm32f4: Add external I2S clock gabriel.fernandez
2017-01-10 10:59 ` Alexandre Torgue
2016-12-13 14:20 ` [PATCH v4 9/9] ARM: dts: stm32f4: Include auxiliary stm32fx clock definition gabriel.fernandez
2017-01-10 10:59 ` Alexandre Torgue
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=0031c2ec-5fc8-4abf-29ef-5039b0508931@st.com \
--to=alexandre.torgue@st.com \
--cc=amelie.delaunay@st.com \
--cc=andrea.merello@gmail.com \
--cc=arnd@arndb.de \
--cc=daniel.thompson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=gabriel.fernandez@st.com \
--cc=kernel@stlinux.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=ludovic.barre@st.com \
--cc=mark.rutland@arm.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=mturquette@baylibre.com \
--cc=nico@linaro.org \
--cc=olivier.bideau@st.com \
--cc=radoslaw.pietrzyk@gmail.com \
--cc=robh+dt@kernel.org \
--cc=sboyd@codeaurora.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).