From: Linus Walleij <linus.walleij@linaro.org>
To: Stephen Boyd <sboyd@codeaurora.org>
Cc: Michael Turquette <mturquette@baylibre.com>,
Peter De Schrijver <pdeschrijver@nvidia.com>,
linux-clk <linux-clk@vger.kernel.org>,
"linux-arm-msm@vger.kernel.org" <linux-arm-msm@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Arnd Bergmann <arnd@arndb.de>, Olof Johansson <olof@lixom.net>
Subject: Re: [PATCH 1/5 v2] clk: qcom: Update DT bindings for the MSM8660/APQ8060 RPMCC
Date: Fri, 9 Jun 2017 10:48:57 +0200 [thread overview]
Message-ID: <CACRpkdbW24L2kLL9buPRAawXOuQ1ypCLf58gCq5=BWP5ex4zuA@mail.gmail.com> (raw)
In-Reply-To: <20170601073858.GU20170@codeaurora.org>
On Thu, Jun 1, 2017 at 9:38 AM, Stephen Boyd <sboyd@codeaurora.org> wrote:
> On 05/24, Linus Walleij wrote:
>> I am sorry if you guys are swamped, I just don't know what to do,
>> clock drivers are starting to become the bottleneck for everything
>> I do. I bet the ARM SoC maintainers must be noticing it too.
(...)
> Meh. Life happens and msm8660 is about a decade old now and not
> something that I can easily review without digging through old
> websites to find documentation on the code I worked on 7 years
> ago. So sorry, but these sorts of patches are basically
> approaching priority none for me and I have to steal time to
> review them.
Sorry the reference above was mainly to the Gemini SoC clock driver
which was blocking ARM consolidation, the fact that this MSM8660
thing was stalled too just got me to think it was related.
I understand the MSM8660 is low prio, but the first DragonBoard
was pushed to developers en masse in 2012 (yours truly included),
which was just half a decade ago, and started
the community boards effort from Qualcomm, and yeah, community
moves slower than markets usually, the board is still supported by
the BSquare company that managed the board release for Qualcomm,
I can still login and check schematics and support forums,
cool isn't it :D
Yours,
Linus Walleij
next prev parent reply other threads:[~2017-06-09 8:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-19 9:13 [PATCH 1/5 v2] clk: qcom: Update DT bindings for the MSM8660/APQ8060 RPMCC Linus Walleij
2017-04-19 9:13 ` [PATCH 2/5 v2] clk: qcom: Elaborate on "active" clocks in the RPM clock bindings Linus Walleij
[not found] ` <20170419091326.11226-2-linus.walleij-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2017-04-28 13:35 ` Rob Herring
2017-06-01 7:39 ` Stephen Boyd
2017-04-19 9:13 ` [PATCH 4/5 v2] clk: qcom: Update DT bindings for MSM8660 LCC Linus Walleij
2017-05-17 7:23 ` [PATCH 1/5 v2] clk: qcom: Update DT bindings for the MSM8660/APQ8060 RPMCC Linus Walleij
[not found] ` <CACRpkdbXEFeVkD8rETyrnuoAxUvnFt2BL07UsXuXfSnq3Qdyfw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-05-24 9:16 ` Linus Walleij
[not found] ` <CACRpkdYvwwJcxKPtKUyZBLWsmjXji7pHDKNz9NRTETqj2P3drQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-05-26 11:57 ` Peter De Schrijver
2017-06-01 7:38 ` Stephen Boyd
2017-06-09 8:48 ` Linus Walleij [this message]
[not found] ` <20170419091326.11226-1-linus.walleij-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2017-06-01 7:48 ` Stephen Boyd
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='CACRpkdbW24L2kLL9buPRAawXOuQ1ypCLf58gCq5=BWP5ex4zuA@mail.gmail.com' \
--to=linus.walleij@linaro.org \
--cc=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=olof@lixom.net \
--cc=pdeschrijver@nvidia.com \
--cc=sboyd@codeaurora.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).