From: Stephen Boyd <sboyd@codeaurora.org>
To: Gabriel Fernandez <gabriel.fernandez@st.com>
Cc: Rob Herring <robh+dt@kernel.org>,
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, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-clk@vger.kernel.org,
ludovic.barre@st.com, olivier.bideau@st.com,
amelie.delaunay@st.com
Subject: Re: [PATCH v2 0/6] STM32F4 Add RTC & QSPI clocks
Date: Wed, 19 Oct 2016 13:29:04 -0700 [thread overview]
Message-ID: <20161019202904.GB8871@codeaurora.org> (raw)
In-Reply-To: <d878b846-556d-180b-8ebf-2d06646efb58@st.com>
On 10/19, Gabriel Fernandez wrote:
> Hi Stephen,
>
>
> On 10/19/2016 01:51 AM, Stephen Boyd wrote:
> >On 10/14, gabriel.fernandez@st.com wrote:
> >>Gabriel Fernandez (6):
> >> clk: stm32f4: Add LSI & LSE clocks
> >> ARM: dts: stm32f429: add LSI and LSE clocks
> >> arm: stmf32: Enable SYSCON
> >> clk: stm32f4: Add RTC clock
> >> clk: stm32f469: Add QSPI clock
> >> ARM: dts: stm32f429: Add QSPI clock
> >Can the clk patches be picked without causing problems for
> >existing dt changes? Do you want an ack from clk maintainers
> >instead of us picking the clk patches up? The series has
> >intermingled clk and dts changes so I'm confused.
> >
>
> Thanks for reviewing.
>
> Normally DT patches will be taken by STM32 maintainer, but yes there
> is a dependency between patch 1 & 2, so if you push the patch 1 into
> clk-next tree you have to take also patch 2.
Let's break the dependency by making the required property
optional or key off a different compatible string. As it stands
right now applying patch 1 will cause things to break until the
second patch lands which is not great.
>
> You have to be synchronized with Alexandre Torgue.
>
>
I'd prefer zero synchronization. Please just send the clk patches
the next time and leave the stuff for arm-soc out of the patch
series. Thanks.
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
WARNING: multiple messages have this Message-ID (diff)
From: sboyd@codeaurora.org (Stephen Boyd)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/6] STM32F4 Add RTC & QSPI clocks
Date: Wed, 19 Oct 2016 13:29:04 -0700 [thread overview]
Message-ID: <20161019202904.GB8871@codeaurora.org> (raw)
In-Reply-To: <d878b846-556d-180b-8ebf-2d06646efb58@st.com>
On 10/19, Gabriel Fernandez wrote:
> Hi Stephen,
>
>
> On 10/19/2016 01:51 AM, Stephen Boyd wrote:
> >On 10/14, gabriel.fernandez at st.com wrote:
> >>Gabriel Fernandez (6):
> >> clk: stm32f4: Add LSI & LSE clocks
> >> ARM: dts: stm32f429: add LSI and LSE clocks
> >> arm: stmf32: Enable SYSCON
> >> clk: stm32f4: Add RTC clock
> >> clk: stm32f469: Add QSPI clock
> >> ARM: dts: stm32f429: Add QSPI clock
> >Can the clk patches be picked without causing problems for
> >existing dt changes? Do you want an ack from clk maintainers
> >instead of us picking the clk patches up? The series has
> >intermingled clk and dts changes so I'm confused.
> >
>
> Thanks for reviewing.
>
> Normally DT patches will be taken by STM32 maintainer, but yes there
> is a dependency between patch 1 & 2, so if you push the patch 1 into
> clk-next tree you have to take also patch 2.
Let's break the dependency by making the required property
optional or key off a different compatible string. As it stands
right now applying patch 1 will cause things to break until the
second patch lands which is not great.
>
> You have to be synchronized with Alexandre Torgue.
>
>
I'd prefer zero synchronization. Please just send the clk patches
the next time and leave the stuff for arm-soc out of the patch
series. Thanks.
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
WARNING: multiple messages have this Message-ID (diff)
From: Stephen Boyd <sboyd-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
To: Gabriel Fernandez <gabriel.fernandez-qxv4g6HH51o@public.gmane.org>
Cc: Rob Herring <robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
Mark Rutland <mark.rutland-5wv7dgnIgG8@public.gmane.org>,
Russell King <linux-I+IVW8TIWO2tmTQ+vhA3Yw@public.gmane.org>,
Maxime Coquelin
<mcoquelin.stm32-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
Alexandre Torgue <alexandre.torgue-qxv4g6HH51o@public.gmane.org>,
Michael Turquette
<mturquette-rdvid1DuHRBWk0Htik3J/w@public.gmane.org>,
Nicolas Pitre <nico-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>,
Arnd Bergmann <arnd-r2nGTMty4D4@public.gmane.org>,
daniel.thompson-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-clk-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
ludovic.barre-qxv4g6HH51o@public.gmane.org,
olivier.bideau-qxv4g6HH51o@public.gmane.org,
amelie.delaunay-qxv4g6HH51o@public.gmane.org
Subject: Re: [PATCH v2 0/6] STM32F4 Add RTC & QSPI clocks
Date: Wed, 19 Oct 2016 13:29:04 -0700 [thread overview]
Message-ID: <20161019202904.GB8871@codeaurora.org> (raw)
In-Reply-To: <d878b846-556d-180b-8ebf-2d06646efb58-qxv4g6HH51o@public.gmane.org>
On 10/19, Gabriel Fernandez wrote:
> Hi Stephen,
>
>
> On 10/19/2016 01:51 AM, Stephen Boyd wrote:
> >On 10/14, gabriel.fernandez-qxv4g6HH51o@public.gmane.org wrote:
> >>Gabriel Fernandez (6):
> >> clk: stm32f4: Add LSI & LSE clocks
> >> ARM: dts: stm32f429: add LSI and LSE clocks
> >> arm: stmf32: Enable SYSCON
> >> clk: stm32f4: Add RTC clock
> >> clk: stm32f469: Add QSPI clock
> >> ARM: dts: stm32f429: Add QSPI clock
> >Can the clk patches be picked without causing problems for
> >existing dt changes? Do you want an ack from clk maintainers
> >instead of us picking the clk patches up? The series has
> >intermingled clk and dts changes so I'm confused.
> >
>
> Thanks for reviewing.
>
> Normally DT patches will be taken by STM32 maintainer, but yes there
> is a dependency between patch 1 & 2, so if you push the patch 1 into
> clk-next tree you have to take also patch 2.
Let's break the dependency by making the required property
optional or key off a different compatible string. As it stands
right now applying patch 1 will cause things to break until the
second patch lands which is not great.
>
> You have to be synchronized with Alexandre Torgue.
>
>
I'd prefer zero synchronization. Please just send the clk patches
the next time and leave the stuff for arm-soc out of the patch
series. Thanks.
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2016-10-19 20:29 UTC|newest]
Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-14 9:18 [PATCH v2 0/6] STM32F4 Add RTC & QSPI clocks gabriel.fernandez
2016-10-14 9:18 ` gabriel.fernandez
2016-10-14 9:18 ` gabriel.fernandez at st.com
2016-10-14 9:18 ` [PATCH v2 1/6] clk: stm32f4: Add LSI & LSE clocks gabriel.fernandez
2016-10-14 9:18 ` gabriel.fernandez-qxv4g6HH51o
2016-10-14 9:18 ` gabriel.fernandez at st.com
2016-10-19 20:24 ` Stephen Boyd
2016-10-19 20:24 ` Stephen Boyd
2016-10-19 20:24 ` Stephen Boyd
2016-10-20 7:47 ` Gabriel Fernandez
2016-10-20 7:47 ` Gabriel Fernandez
2016-10-20 7:47 ` Gabriel Fernandez
2016-10-20 16:05 ` Gabriel Fernandez
2016-10-20 16:05 ` Gabriel Fernandez
2016-10-20 16:05 ` Gabriel Fernandez
2016-10-14 9:18 ` [PATCH v2 2/6] ARM: dts: stm32f429: add LSI and " gabriel.fernandez
2016-10-14 9:18 ` gabriel.fernandez
2016-10-14 9:18 ` gabriel.fernandez at st.com
2016-10-14 9:18 ` [PATCH v2 3/6] arm: stmf32: Enable SYSCON gabriel.fernandez
2016-10-14 9:18 ` gabriel.fernandez-qxv4g6HH51o
2016-10-14 9:18 ` gabriel.fernandez at st.com
2016-10-14 9:18 ` [PATCH v2 4/6] clk: stm32f4: Add RTC clock gabriel.fernandez
2016-10-14 9:18 ` gabriel.fernandez-qxv4g6HH51o
2016-10-14 9:18 ` gabriel.fernandez at st.com
2016-10-19 20:45 ` Stephen Boyd
2016-10-19 20:45 ` Stephen Boyd
2016-10-20 7:50 ` Gabriel Fernandez
2016-10-20 7:50 ` Gabriel Fernandez
2016-10-20 7:50 ` Gabriel Fernandez
2016-10-20 7:55 ` Gabriel Fernandez
2016-10-20 7:55 ` Gabriel Fernandez
2016-10-20 7:55 ` Gabriel Fernandez
2016-10-14 9:18 ` [PATCH v2 5/6] clk: stm32f469: Add QSPI clock gabriel.fernandez
2016-10-14 9:18 ` gabriel.fernandez
2016-10-14 9:18 ` gabriel.fernandez at st.com
2016-10-18 14:17 ` Rob Herring
2016-10-18 14:17 ` Rob Herring
2016-10-19 20:32 ` Stephen Boyd
2016-10-19 20:32 ` Stephen Boyd
2016-10-20 15:44 ` Gabriel Fernandez
2016-10-20 15:44 ` Gabriel Fernandez
2016-10-20 15:44 ` Gabriel Fernandez
2016-10-14 9:18 ` [PATCH v2 6/6] ARM: dts: stm32f429: " gabriel.fernandez
2016-10-14 9:18 ` gabriel.fernandez
2016-10-14 9:18 ` gabriel.fernandez at st.com
2016-11-03 16:45 ` Alexandre Torgue
2016-11-03 16:45 ` Alexandre Torgue
2016-11-03 16:45 ` Alexandre Torgue
2016-10-18 23:51 ` [PATCH v2 0/6] STM32F4 Add RTC & QSPI clocks Stephen Boyd
2016-10-18 23:51 ` Stephen Boyd
2016-10-19 8:34 ` Gabriel Fernandez
2016-10-19 8:34 ` Gabriel Fernandez
2016-10-19 8:34 ` Gabriel Fernandez
2016-10-19 20:29 ` Stephen Boyd [this message]
2016-10-19 20:29 ` Stephen Boyd
2016-10-19 20:29 ` Stephen Boyd
2016-10-20 7:52 ` Gabriel Fernandez
2016-10-20 7:52 ` Gabriel Fernandez
2016-10-20 7:52 ` Gabriel Fernandez
2016-11-03 8:52 ` Alexandre Torgue
2016-11-03 8:52 ` Alexandre Torgue
2016-11-03 8:52 ` Alexandre Torgue
2016-11-03 8:57 ` Gabriel Fernandez
2016-11-03 8:57 ` Gabriel Fernandez
2016-11-03 8:57 ` 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=20161019202904.GB8871@codeaurora.org \
--to=sboyd@codeaurora.org \
--cc=alexandre.torgue@st.com \
--cc=amelie.delaunay@st.com \
--cc=arnd@arndb.de \
--cc=daniel.thompson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=gabriel.fernandez@st.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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.