From: Alexandre Torgue <alexandre.torgue@st.com>
To: <patrice.chotard@st.com>, <robh+dt@kernel.org>,
<mark.rutland@arm.com>, <linux@armlinux.org.uk>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <devicetree@vger.kernel.org>,
<lee.jones@linaro.org>
Cc: <mcoquelin.stm32@gmail.com>, <linux-stm32@st-md-mailman.stormreply.com>
Subject: Re: [PATCH 1/3] ARM: dts: stm32: Fix DT dtc warnings for stm32h7
Date: Tue, 7 Aug 2018 13:56:20 +0200 [thread overview]
Message-ID: <f5933d5c-8da3-5112-351c-6b1ba669a9b6@st.com> (raw)
In-Reply-To: <8bd7a402-fc88-f4d9-451f-9533f2898ce0@st.com>
Hi Patrice
On 08/07/2018 01:38 PM, Alexandre Torgue wrote:
>> + #address-cells = <1>;
>> + #size-cells = <1>;
>> +
>> clocks {
>> clk_hse: clk-hse {
>> #clock-cells = <0>;
>> @@ -60,7 +62,7 @@
>> clock-frequency = <32768>;
>> };
>> - clk_i2s: i2s_ckin {
>> + clk_i2s: i2s-ckin {
>
> clock driver deals with "i2s_ckin" for clock source selection. I need
> to check deeper if this change could cause an issue.
Sorry I didn't check in the well driver. As far I can see it's ok for
this part of patch.
cheers
Alex
>
> thx
> Alex
next prev parent reply other threads:[~2018-08-07 11:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-07 11:06 [PATCH 0/3] ARM: dts: stm32: Fix DT dtc warnings for STM32 MCU's patrice.chotard
2018-08-07 11:06 ` [PATCH 1/3] ARM: dts: stm32: Fix DT dtc warnings for stm32h7 patrice.chotard
2018-08-07 11:38 ` Alexandre Torgue
2018-08-07 11:56 ` Alexandre Torgue [this message]
2018-08-07 12:01 ` Patrice CHOTARD
2018-08-07 11:06 ` [PATCH 2/3] ARM: dts: stm32: Fix DT dtc warnings for stm32f7 patrice.chotard
2018-08-07 11:44 ` Alexandre Torgue
2018-08-07 11:06 ` [PATCH 3/3] ARM: dts: stm32: Fix DT dtc warnings for stm32f4 patrice.chotard
2018-08-07 11:44 ` 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=f5933d5c-8da3-5112-351c-6b1ba669a9b6@st.com \
--to=alexandre.torgue@st.com \
--cc=devicetree@vger.kernel.org \
--cc=lee.jones@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=linux@armlinux.org.uk \
--cc=mark.rutland@arm.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=patrice.chotard@st.com \
--cc=robh+dt@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
all inboxes | Powered by JetHome®