From: Vladimir Zapolskiy <vz@mleia.com>
To: Gabriel FERNANDEZ <gabriel.fernandez@st.com>,
Rob Herring <robh+dt@kernel.org>,
Stephen Boyd <sboyd@codeaurora.org>
Cc: Mark Rutland <mark.rutland@arm.com>,
Russell King <linux@armlinux.org.uk>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Alexandre TORGUE <alexandre.torgue@st.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>,
Lee Jones <lee.jones@linaro.org>,
Sylvain Lemieux <slemieux.tyco@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.kerne>
Subject: Re: [PATCH v7 3/3] clk: stm32h7: Add stm32h743 clock driver
Date: Thu, 20 Jul 2017 14:51:06 +0300 [thread overview]
Message-ID: <c5264416-754b-6ec8-f9fb-3b0ac2ba3a58@mleia.com> (raw)
In-Reply-To: <11c37627-a39b-7f2d-d0d4-af312eac8668@st.com>
Hi Gabriel,
On 07/20/2017 11:31 AM, Gabriel FERNANDEZ wrote:
> Hi Vladimir,
>
>
> On 07/19/2017 11:20 PM, Vladimir Zapolskiy wrote:
>> Hello Gabriel,
>>
>> On 07/19/2017 05:25 PM, gabriel.fernandez@st.com wrote:
>>> From: Gabriel Fernandez <gabriel.fernandez@st.com>
>>>
>>> This patch enables clocks for STM32H743 boards.
>>>
>>> Signed-off-by: Gabriel Fernandez <gabriel.fernandez@st.com>
>>>
>>> for MFD changes:
>>> Acked-by: Lee Jones <lee.jones@linaro.org>
>>>
>>> for DT-Bindings
>>> Acked-by: Rob Herring <robh@kernel.org>
>>> ---
>>> .../devicetree/bindings/clock/st,stm32h7-rcc.txt | 82 ++
>> I'll provide some review comments about device tree bindings only.
>>
>>> drivers/clk/Makefile | 1 +
>>> drivers/clk/clk-stm32h7.c | 1409 ++++++++++++++++++++
>>> include/dt-bindings/clock/stm32h7-clks.h | 165 +++
>>> include/dt-bindings/mfd/stm32h7-rcc.h | 136 ++
>>> 5 files changed, 1793 insertions(+)
>>> create mode 100644 Documentation/devicetree/bindings/clock/st,stm32h7-rcc.txt
>>> create mode 100644 drivers/clk/clk-stm32h7.c
>>> create mode 100644 include/dt-bindings/clock/stm32h7-clks.h
>>> create mode 100644 include/dt-bindings/mfd/stm32h7-rcc.h
>>>
>>> diff --git a/Documentation/devicetree/bindings/clock/st,stm32h7-rcc.txt b/Documentation/devicetree/bindings/clock/st,stm32h7-rcc.txt
>>> new file mode 100644
>>> index 0000000..442c50c
>>> --- /dev/null
>>> +++ b/Documentation/devicetree/bindings/clock/st,stm32h7-rcc.txt
>>> @@ -0,0 +1,82 @@
>>> +STMicroelectronics STM32H7 Reset and Clock Controller
>>> +=====================================================
>>> +
>>> +The RCC IP is both a reset and a clock controller.
>>> +
>>> +Please refer to clock-bindings.txt for common clock controller binding usage.
>>> +Please also refer to reset.txt for common reset controller binding usage.
>>> +
>>> +Required properties:
>>> +- compatible: Should be:
>>> + "st,stm32h743-rcc"
>>> +
>>> +- reg: should be register base and length as documented in the
>>> + datasheet
>>> +
>>> +- #reset-cells: 1, see below
>>> +
>>> +- #clock-cells : from common clock binding; shall be set to 1
>>> +
>>> +- clocks: External oscillator clock phandle
>>> + - high speed external clock signal (HSE)
>>> + - low speed external clock signal (LSE)
>>> + - external I2S clock (I2S_CKIN)
>>> +
>>> +Optional properties:
>>> +- st,syscfg: phandle for pwrcfg, mandatory to disable/enable backup domain
>>> + write protection (RTC clock).
>>> +
>>> +Example:
>>> +
>>> + rcc: rcc@58024400 {
>> 'rcc' as a generic device node name is awkward.
>>
>> I believe the main function of the device is clock controller (unlikely
>> a generic reset controller can be converted into a clock controller),
>> the locations of the document and device driver also indicate that
>> primarily it is a clock controller, so I suggest to replace device node
>> name with 'clock-controller' like below:
> I prefer to keep rcc node name, to be coherent with the other ST
> platforms (STM32F4/F7)
the thing is, a device node name is expected to comply with ePAPR or
the devicetree specification, which says
The name of a node should be somewhat generic, reflecting
the function of the device and not its precise programming model.
If devicetree and CCF maintainers are fine with 'rcc', I won't object,
my role is just to emphasize the found issue and recommend to use another
and more common name 'clock-controller', it is a simple and fortunately
backward compatible change to other ST platforms as well.
>> rcc: clock-controller@58024400 {
>>
>>> + #reset-cells = <1>;
>>> + #clock-cells = <2>
>> Missing trailing semicolon ^^^
> ok
--
With best wishes,
Vladimir
next prev parent reply other threads:[~2017-07-20 11:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-19 14:25 [PATCH v7 0/3] clk: stm32h7: Add stm32h743 clock driver gabriel.fernandez
2017-07-19 14:25 ` [PATCH v7 1/3] clk: nxp: clk-lpc32xx: rename clk_gate_is_enabled() gabriel.fernandez
[not found] ` <1500474344-9832-2-git-send-email-gabriel.fernandez-qxv4g6HH51o@public.gmane.org>
2017-07-19 21:00 ` Vladimir Zapolskiy
2017-07-19 14:25 ` [PATCH v7 2/3] clk: gate: expose clk_gate_ops::is_enabled gabriel.fernandez
2017-07-19 21:02 ` Vladimir Zapolskiy
2017-07-19 14:25 ` [PATCH v7 3/3] clk: stm32h7: Add stm32h743 clock driver gabriel.fernandez
2017-07-19 21:20 ` Vladimir Zapolskiy
2017-07-20 8:31 ` Gabriel FERNANDEZ
2017-07-20 11:51 ` Vladimir Zapolskiy [this message]
[not found] ` <c5264416-754b-6ec8-f9fb-3b0ac2ba3a58-ChpfBGZJDbMAvxtiuMwx3w@public.gmane.org>
2017-07-21 20:37 ` Stephen Boyd
[not found] ` <20170721203712.GH19878-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2017-07-22 11:56 ` Gabriel FERNANDEZ
[not found] ` <d999fc79-7b14-da8e-965f-371cf4352dd1-ChpfBGZJDbMAvxtiuMwx3w@public.gmane.org>
2017-07-22 11:58 ` Gabriel FERNANDEZ
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=c5264416-754b-6ec8-f9fb-3b0ac2ba3a58@mleia.com \
--to=vz@mleia.com \
--cc=alexandre.torgue@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=lee.jones@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kerne \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mark.rutland@arm.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=mturquette@baylibre.com \
--cc=nico@linaro.org \
--cc=radoslaw.pietrzyk@gmail.com \
--cc=robh+dt@kernel.org \
--cc=sboyd@codeaurora.org \
--cc=slemieux.tyco@gmail.com \
/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).