From: Kevin Hilman <khilman@baylibre.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: arm-soc <arm@kernel.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
linux-amlogic@lists.infradead.org, linux-clk@vger.kernel.org
Subject: Re: [GIT PULL] Amlogic 64-bit DT updates for v4.12
Date: Fri, 31 Mar 2017 09:01:31 -0700 [thread overview]
Message-ID: <m2fuht4eqs.fsf@baylibre.com> (raw)
In-Reply-To: <CAK8P3a02e3DxjuW9pA66NSCc9vw_h1Xuk6TdEbRnEQ4v4W7NHA@mail.gmail.com> (Arnd Bergmann's message of "Fri, 31 Mar 2017 16:02:41 +0200")
Arnd Bergmann <arnd@arndb.de> writes:
> On Wed, Mar 29, 2017 at 11:45 PM, Kevin Hilman <khilman@baylibre.com> wrote:
>> Olof, Arnd,
>>
>> Below are some 64-bit DT changes for Amlogic platforms for v4.12. Note
>> that this branch includes a merge of an immutable branch from the clk
>> tree (clk-meson) due to dependencies on new clocks added to the meson
>> clock driver and used in these DT updates.
>
> I did not pull this one because of the silly dependency. The device tree
> files should be completely independent of the driver changes.
Aaargh, this is getting very frustrating.
[...]
> Which add random macros in the middle of the number space.
>
> Since the header changes are in an immutable branch, it's probably
> too late to fix this for 4.12, but maybe we can get the header into a
> form that allows us to do future DT changes without having to
> wait an extra release. The clock driver apparently already defines
> some of the numbers above, so you can fill all of those in already.
We could, but this is in direct conflict with the recommendations of the
clk maintainers to not expose clock IDs to the DT until we know they are
used because, well, things change.
Can we *please* get some clarity on on this between arm-soc and the clk
maintainers? I've been asking for a couple merge windows now.
Irritated,
Kevin
WARNING: multiple messages have this Message-ID (diff)
From: khilman@baylibre.com (Kevin Hilman)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] Amlogic 64-bit DT updates for v4.12
Date: Fri, 31 Mar 2017 09:01:31 -0700 [thread overview]
Message-ID: <m2fuht4eqs.fsf@baylibre.com> (raw)
In-Reply-To: <CAK8P3a02e3DxjuW9pA66NSCc9vw_h1Xuk6TdEbRnEQ4v4W7NHA@mail.gmail.com> (Arnd Bergmann's message of "Fri, 31 Mar 2017 16:02:41 +0200")
Arnd Bergmann <arnd@arndb.de> writes:
> On Wed, Mar 29, 2017 at 11:45 PM, Kevin Hilman <khilman@baylibre.com> wrote:
>> Olof, Arnd,
>>
>> Below are some 64-bit DT changes for Amlogic platforms for v4.12. Note
>> that this branch includes a merge of an immutable branch from the clk
>> tree (clk-meson) due to dependencies on new clocks added to the meson
>> clock driver and used in these DT updates.
>
> I did not pull this one because of the silly dependency. The device tree
> files should be completely independent of the driver changes.
Aaargh, this is getting very frustrating.
[...]
> Which add random macros in the middle of the number space.
>
> Since the header changes are in an immutable branch, it's probably
> too late to fix this for 4.12, but maybe we can get the header into a
> form that allows us to do future DT changes without having to
> wait an extra release. The clock driver apparently already defines
> some of the numbers above, so you can fill all of those in already.
We could, but this is in direct conflict with the recommendations of the
clk maintainers to not expose clock IDs to the DT until we know they are
used because, well, things change.
Can we *please* get some clarity on on this between arm-soc and the clk
maintainers? I've been asking for a couple merge windows now.
Irritated,
Kevin
WARNING: multiple messages have this Message-ID (diff)
From: khilman@baylibre.com (Kevin Hilman)
To: linus-amlogic@lists.infradead.org
Subject: [GIT PULL] Amlogic 64-bit DT updates for v4.12
Date: Fri, 31 Mar 2017 09:01:31 -0700 [thread overview]
Message-ID: <m2fuht4eqs.fsf@baylibre.com> (raw)
In-Reply-To: <CAK8P3a02e3DxjuW9pA66NSCc9vw_h1Xuk6TdEbRnEQ4v4W7NHA@mail.gmail.com> (Arnd Bergmann's message of "Fri, 31 Mar 2017 16:02:41 +0200")
Arnd Bergmann <arnd@arndb.de> writes:
> On Wed, Mar 29, 2017 at 11:45 PM, Kevin Hilman <khilman@baylibre.com> wrote:
>> Olof, Arnd,
>>
>> Below are some 64-bit DT changes for Amlogic platforms for v4.12. Note
>> that this branch includes a merge of an immutable branch from the clk
>> tree (clk-meson) due to dependencies on new clocks added to the meson
>> clock driver and used in these DT updates.
>
> I did not pull this one because of the silly dependency. The device tree
> files should be completely independent of the driver changes.
Aaargh, this is getting very frustrating.
[...]
> Which add random macros in the middle of the number space.
>
> Since the header changes are in an immutable branch, it's probably
> too late to fix this for 4.12, but maybe we can get the header into a
> form that allows us to do future DT changes without having to
> wait an extra release. The clock driver apparently already defines
> some of the numbers above, so you can fill all of those in already.
We could, but this is in direct conflict with the recommendations of the
clk maintainers to not expose clock IDs to the DT until we know they are
used because, well, things change.
Can we *please* get some clarity on on this between arm-soc and the clk
maintainers? I've been asking for a couple merge windows now.
Irritated,
Kevin
next prev parent reply other threads:[~2017-03-31 16:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-29 21:45 [GIT PULL] Amlogic 64-bit DT updates for v4.12 Kevin Hilman
2017-03-29 21:45 ` Kevin Hilman
2017-03-29 21:45 ` Kevin Hilman
2017-03-31 14:02 ` Arnd Bergmann
2017-03-31 14:02 ` Arnd Bergmann
2017-03-31 14:02 ` Arnd Bergmann
2017-03-31 16:01 ` Kevin Hilman [this message]
2017-03-31 16:01 ` Kevin Hilman
2017-03-31 16:01 ` Kevin Hilman
2017-03-31 16:11 ` Ben Dooks
2017-03-31 16:11 ` Ben Dooks
2017-03-31 16:11 ` Ben Dooks
2017-03-31 17:07 ` Michael Turquette
2017-03-31 17:07 ` Michael Turquette
2017-03-31 17:07 ` Michael Turquette
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=m2fuht4eqs.fsf@baylibre.com \
--to=khilman@baylibre.com \
--cc=arm@kernel.org \
--cc=arnd@arndb.de \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.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.