From: skannan@codeaurora.org (Saravana Kannan)
To: linux-arm-kernel@lists.infradead.org
Subject: Common clock API for i.MX
Date: Mon, 06 Feb 2012 16:20:56 -0800 [thread overview]
Message-ID: <4F306E68.1090507@codeaurora.org> (raw)
In-Reply-To: <20120125084533.GD1068@n2100.arm.linux.org.uk>
On 01/25/2012 12:45 AM, Russell King - ARM Linux wrote:
>
> My conclusion, therefore, is that there's very little actual interest
> amongst the ARM community to move towards a common clk API.
MSM is most certainly interested.
> I'm rather disappointed by that, and have been wondering for some time
> why I wasted my time over the clk_prepare() stuff, and wondering why the
> hell I bothered putting it in mainline. I must have been under the
> mistaken impression that this is something people wanted. Obviously not.
The time you spent on this certainly wasn't a waste. Once it got into
the mainline, we already back ported the stubs into our kernel tree. I
have already laid out a plan to migrate of all MSM drivers to the new
APIs and it's work in progress. Some drivers devs are already working on it.
Unfortunately, the fact that not all the MSM drivers are already merged
onto the mailine is a separate issue that I don't have much control
over. So, the interest for these APIs aren't easily visible to you.
> There's a good saying here: actions speak louder than words. The action
> here is the lack of patches from platform maintainers. That definitely
> shouts.
You are welcome to look at our kernel tree for proof of interest. I know
internal trees aren't of much relevance to you, but you can take that as
a precursor of what to expect when changes get pushed upstream.
> As a result of the lack of motivation by others over this, I've lost
> interest in it. Sorry.
Hopefully, this email is of some help in restoring your interest.
Thanks,
Saravana
--
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.
next prev parent reply other threads:[~2012-02-07 0:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-25 1:54 Common clock API for i.MX Matt Sealey
2012-01-25 8:45 ` Russell King - ARM Linux
2012-01-25 13:45 ` Matt Sealey
2012-01-25 14:44 ` Russell King - ARM Linux
2012-01-25 20:33 ` Sylwester Nawrocki
2012-01-25 14:53 ` Mark Brown
2012-01-25 15:42 ` Nicolas Pitre
2012-01-25 15:52 ` Mark Brown
2012-01-26 6:20 ` Shawn Guo
2012-01-26 19:02 ` Sascha Hauer
2012-02-07 0:20 ` Saravana Kannan [this message]
2012-01-26 6:10 ` Shawn Guo
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=4F306E68.1090507@codeaurora.org \
--to=skannan@codeaurora.org \
--cc=linux-arm-kernel@lists.infradead.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).