From: daniel.thompson@linaro.org (Daniel Thompson)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 2/4] dt-bindings: Document the STM32F4 clock bindings
Date: Mon, 01 Jun 2015 08:46:59 +0100 [thread overview]
Message-ID: <556C0DF3.7050603@linaro.org> (raw)
In-Reply-To: <55698104.2070205@gmail.com>
On 30/05/15 10:21, Maxime Coquelin wrote:
> HI Daniel,
>
> On 05/30/2015 09:54 AM, Daniel Thompson wrote:
>> This adds documentation of device tree bindings for the clock related
>> portions of the STM32 RCC block.
>>
>> Signed-off-by: Daniel Thompson <daniel.thompson@linaro.org>
>> ---
>> .../devicetree/bindings/clock/st,stm32-rcc.txt | 65
>> ++++++++++++++++++++++
>> 1 file changed, 65 insertions(+)
>> <snip>
>> +Example:
>> +
>> + /* Gated clock, AHB1 bit 0 (GPIOA) */
>> + ... {
>> + clocks = <&rcc 0 0>
>> + };
>> +
>> + /* Gated clock, AHB2 bit 4 (GPIOA) */
> s/GPIOA/CRYP/
Oops! Will fix.
>> + ... {
>> + clocks = <&rcc 0 36>
>> + };
>> +
>> +Specifying other clocks
>> +=======================
>> +
>> +The primary index must be set to 1.
>> +
>> +The secondary index is bound with the following magic numbers:
>> +
>> + 0 SYSTICK
>> + 1 FCLK
> How do you plan to handle the SAI & I2S clocks?
> By adding index 3?
Pretty much. Tentatively I'm thinking of:
2 I2S clocks
3 SAI1_A clock
4 SAI1_B clock
5 LCD-TFT clock
Note: Sort order is based on the vertical ordering in the clock tree
diagram in the data sheet.
Only reason not to include these in the bindings immediately is that I
wanted to check how/if these clocks are gated. The clock tree diagram
shows them having individual clock gates so before proposing them using
magic numbers I wanted to double check if these values can be identified
at gates clocks.
Daniel.
next prev parent reply other threads:[~2015-06-01 7:46 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-22 20:41 [RFC PATCH 0/3] clk: stm32: Add clock driver for STM32F4[23]xxx devices Daniel Thompson
2015-05-22 20:41 ` [RFC PATCH 1/3] dt-bindings: Document the STM32F4 clock bindings Daniel Thompson
2015-05-22 20:41 ` [RFC PATCH 2/3] clk: stm32: Add clock driver for STM32F4[23]xxx devices Daniel Thompson
2015-06-04 22:07 ` Stephen Boyd
2015-06-05 9:36 ` Daniel Thompson
2015-06-06 0:10 ` Stephen Boyd
2015-05-22 20:41 ` [RFC PATCH 3/3] ARM: dts: stm32f429: Adopt STM32F4 clock driver Daniel Thompson
2015-05-26 16:41 ` [RFC PATCH 0/3] clk: stm32: Add clock driver for STM32F4[23]xxx devices Maxime Coquelin
2015-05-27 8:36 ` Daniel Thompson
2015-05-30 7:54 ` [PATCH v2 0/4] " Daniel Thompson
2015-05-30 7:54 ` [PATCH v2 1/4] ARM: stm32: Enable clock source Daniel Thompson
2015-05-30 7:54 ` [PATCH v2 2/4] dt-bindings: Document the STM32F4 clock bindings Daniel Thompson
2015-05-30 9:21 ` Maxime Coquelin
2015-06-01 7:46 ` Daniel Thompson [this message]
2015-05-30 7:54 ` [PATCH v2 3/4] clk: stm32: Add clock driver for STM32F4[23]xxx devices Daniel Thompson
2015-05-30 9:15 ` Maxime Coquelin
2015-06-01 7:18 ` Daniel Thompson
2015-05-30 7:54 ` [PATCH v2 4/4] ARM: dts: stm32f429: Adopt STM32F4 clock driver Daniel Thompson
2015-05-30 9:38 ` Maxime Coquelin
2015-05-30 8:40 ` [PATCH v2 0/4] clk: stm32: Add clock driver for STM32F4[23]xxx devices Maxime Coquelin
2015-06-10 20:09 ` [PATCH v3 0/3] " Daniel Thompson
2015-06-10 20:09 ` [PATCH v3 1/3] dt-bindings: Document the STM32F4 clock bindings Daniel Thompson
2015-06-12 7:25 ` Maxime Coquelin
2015-06-22 22:47 ` Stephen Boyd
2015-06-10 20:09 ` [PATCH v3 2/3] clk: stm32: Add clock driver for STM32F4[23]xxx devices Daniel Thompson
2015-06-22 22:48 ` Stephen Boyd
2015-06-22 23:21 ` Stephen Boyd
2015-06-23 8:25 ` Daniel Thompson
2015-06-10 20:09 ` [PATCH v3 3/3] ARM: dts: stm32f429: Adopt STM32F4 clock driver Daniel Thompson
2015-07-07 9:38 ` Maxime Coquelin
2015-06-22 22:48 ` [PATCH v3 0/3] clk: stm32: Add clock driver for STM32F4[23]xxx devices Stephen Boyd
2015-06-23 8:22 ` Daniel Thompson
2015-06-23 9:24 ` Maxime Coquelin
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=556C0DF3.7050603@linaro.org \
--to=daniel.thompson@linaro.org \
--cc=linux-arm-kernel@lists.infradead.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).