public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ian Molton <ian@mnementh.co.uk>
To: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Cc: linux-kernel@vger.kernel.org, Magnus Damm <damm@opensource.se>,
	akpm@linux-foundation.org, Matt Fleming <matt@console-pimps.org>,
	Philip Langdale <philipl@overt.org>
Subject: Re: [PATCH] tmio_mmc: Optionally support using platform clock
Date: Tue, 28 Jul 2009 14:39:59 +0100	[thread overview]
Message-ID: <4A6EFFAF.10603@mnementh.co.uk> (raw)
In-Reply-To: <Pine.LNX.4.64.0907280937000.4943@axis700.grange>

Guennadi Liakhovetski wrote:
> If the platform device has a clock associated with the tmio-mmc device, 
> use it.

As RMK has stated manny times before now, you cannot pass struct clks to 
devices like this, they should be claimed using the clk api.

The problem for tmio-mmc is that the struct clk is tied to the 
architecture code, so at present we cant create new clk providers. What 
we need is for the clk api to be divorced from the arch code so that the 
TMIO MFD driver can create its own clocks that can be claimed by its 
children.

  parent reply	other threads:[~2009-07-28 13:40 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-28  7:51 [PATCH] tmio_mmc: Optionally support using platform clock Guennadi Liakhovetski
2009-07-28 11:48 ` Matt Fleming
2009-07-28 13:39 ` Ian Molton [this message]
2009-07-28 13:46 ` Ian Molton
2009-07-28 15:45   ` Guennadi Liakhovetski
2009-07-28 17:09     ` Ian Molton
2009-08-01 14:10       ` Dmitry Eremin-Solenikov
2009-08-03 17:30         ` Ian Molton
2009-08-03 21:57           ` Dmitry Eremin-Solenikov
2009-07-29 15:20 ` pHilipp Zabel
2009-07-29 15:24   ` Magnus Damm
2009-07-29 15:33     ` pHilipp Zabel
2009-07-29 15:32   ` pHilipp Zabel
2009-07-29 23:40     ` Ian Molton
2009-07-29 21:12 ` pHilipp Zabel

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=4A6EFFAF.10603@mnementh.co.uk \
    --to=ian@mnementh.co.uk \
    --cc=akpm@linux-foundation.org \
    --cc=damm@opensource.se \
    --cc=g.liakhovetski@gmx.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matt@console-pimps.org \
    --cc=philipl@overt.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