All of lore.kernel.org
 help / color / mirror / Atom feed
From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: Common clock API for i.MX
Date: Wed, 25 Jan 2012 08:45:33 +0000	[thread overview]
Message-ID: <20120125084533.GD1068@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <CAKGA1bkHgnJQs3_n6QtQjf-8xaPn0YnxMmE2Q=+opWcsp10zQA@mail.gmail.com>

On Tue, Jan 24, 2012 at 07:54:08PM -0600, Matt Sealey wrote:
> Hi Arnd/RMK/Sascha,
> 
> We're trying to bring up a good batch of drivers here for MX51 and
> EfikaMX systems and noticed that the released 3.2 kernel doesn't
> include the common clock stuff that all the other platforms seem to be
> using.

As far as I know, it still isn't ready (if it was, surely it would've
been merged?)

Grepping for clk_prepare() it looks like very few people have converted
over to this - it's just the AMBA stuff, a few bits of OMAP and MXS.
So even if the common clock stuff comes in, almost nothing will be able
to use it:

arch/arm/common/sa1111.c
arch/arm/common/timer-sp.c
arch/arm/mach-omap2/clock2xxx.c
arch/arm/mach-omap2/clock.h
arch/arm/mach-omap2/prcm.c
arch/arm/mach-omap2/clock2430_data.c
arch/arm/mach-omap2/clock2xxx.h
arch/arm/mach-omap2/clock2420_data.c
arch/arm/mach-mxs/clock-mx23.c
arch/arm/mach-mxs/clock.c
arch/arm/mach-mxs/timer.c
arch/arm/mach-mxs/system.c
arch/arm/mach-mxs/clock-mx28.c
arch/arm/mach-mxs/mach-mx28evk.c
arch/arm/kernel/smp_twd.c
drivers/gpio/gpio-pxa.c
drivers/tty/serial/amba-pl011.c
drivers/tty/serial/mxs-auart.c
drivers/tty/serial/amba-pl010.c
drivers/amba/bus.c
drivers/net/ethernet/freescale/fec.c
drivers/net/can/flexcan.c
drivers/video/omap2/dss/dsi.c
drivers/video/amba-clcd.c
drivers/video/mxsfb.c
drivers/staging/tidspbridge/include/dspbridge/clk.h
drivers/staging/tidspbridge/core/dsp-clock.c
drivers/spi/spi-pl022.c
drivers/mmc/host/mmci.c
drivers/mmc/host/mxs-mmc.c
drivers/dma/mxs-dma.c
drivers/mtd/nand/gpmi-nand/gpmi-lib.c

My conclusion, therefore, is that there's very little actual interest
amongst the ARM community to move towards a common clk API.

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.

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.

As a result of the lack of motivation by others over this, I've lost
interest in it.  Sorry.

  reply	other threads:[~2012-01-25  8:45 UTC|newest]

Thread overview: 13+ 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 [this message]
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 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
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=20120125084533.GD1068@n2100.arm.linux.org.uk \
    --to=linux@arm.linux.org.uk \
    --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 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.