From: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
To: Ian Molton <ian@mnementh.co.uk>
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>,
Dmitry Baryshkov <dbaryshkov@gmail.com>
Subject: Re: [PATCH] tmio_mmc: Optionally support using platform clock
Date: Tue, 28 Jul 2009 17:45:46 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.64.0907281556160.6219@axis700.grange> (raw)
In-Reply-To: <4A6F0123.9040809@mnementh.co.uk>
On Tue, 28 Jul 2009, Ian Molton wrote:
> Guennadi Liakhovetski wrote:
> > If the platform device has a clock associated with the tmio-mmc device, use
> > it.
>
> Sorry, I misread there.
>
> I'm still not sure what to to about this though because we seem to be
> collecting numerous ways of passing clocks to this driver, this is the fourth,
> by my counting.
>
> the clock API could cope with all of them by simply allowing the driver to
> claim CLK_MMC (or such) from its parent, except that it cant cope with both
> the platform and MFD code providing clocks. The parent could be either the
> TMIO MFD core (for TMIO MFDs) or the CPU/SoC whatever, it woudlnt matter.
>
> In any case, still no, as with all the other TMIO clock code patches. This
> needs to be done properly.
Hi Ian
Thanks for the review.
I understand your concerns. Of course, the _proper_ solution would be to
implement an architecture-independent clock API, something like what
clocklib was trying to do. So, yes, if clocklib were in place now, I
certainly would have used it.
I searched for those clocklib submission attempts (Dmitry added to CC).
Last one I can find (maybe I missed some) is from July 2008 - more than a
year ago. So, looks like our options currently are:
1. wait for new submissions of clocklib - if any are planned
2. develop a completely new arch-independent clock API approach
3. take over patches from Dmitry and bring them to a state acceptable for
mainline
(any more I missed)
No idea about 1, hopefully, Dmitry can tell if he has any near future
plans to resubmit his patches.
I personally don't have free (as in beer) time to work on 2 or 3. Anyone?
So, unless we hear, that one of the 1-3 is going to happen real soon now,
I think, it would be unfair to leave SuperH without a proper MMC driver in
the mainline for an indefinite time, when one can be trivially achieved.
As for your debugging concern, we could allow configuration-less operation
only on SuperH in tmio_mmc, how about that?
Thanks
Guennadi
---
Guennadi Liakhovetski
next prev parent reply other threads:[~2009-07-28 15:45 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-28 7:51 Guennadi Liakhovetski
2009-07-28 11:48 ` Matt Fleming
2009-07-28 13:39 ` Ian Molton
2009-07-28 13:46 ` Ian Molton
2009-07-28 15:45 ` Guennadi Liakhovetski [this message]
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=Pine.LNX.4.64.0907281556160.6219@axis700.grange \
--to=g.liakhovetski@gmx.de \
--cc=akpm@linux-foundation.org \
--cc=damm@opensource.se \
--cc=dbaryshkov@gmail.com \
--cc=ian@mnementh.co.uk \
--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
all inboxes | Powered by JetHome®