From: pHilipp Zabel <philipp.zabel@gmail.com>
To: Magnus Damm <magnus.damm@gmail.com>
Cc: Guennadi Liakhovetski <g.liakhovetski@gmx.de>,
Ian Molton <ian@mnementh.co.uk>,
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: Wed, 29 Jul 2009 17:33:08 +0200 [thread overview]
Message-ID: <74d0deb30907290833m3d1ff596s180759fb961a8a8d@mail.gmail.com> (raw)
In-Reply-To: <aec7e5c30907290824p5e20fb14g3d14aece2d3e33c6@mail.gmail.com>
On Wed, Jul 29, 2009 at 5:24 PM, Magnus Damm<magnus.damm@gmail.com> wrote:
> On Thu, Jul 30, 2009 at 12:20 AM, pHilipp Zabel<philipp.zabel@gmail.com> wrote:
>> On Tue, Jul 28, 2009 at 9:51 AM, Guennadi
>> Liakhovetski<g.liakhovetski@gmx.de> wrote:
>>> If the platform device has a clock associated with the tmio-mmc device,
>>> use it.
>>>
>>> Signed-off-by: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
>>> Cc: Magnus Damm <damm@opensource.se>
>>> ---
>>>
>>> Depends (at least logically) on
>>> http://marc.info/?l=linux-kernel&m=124782904228865&w=2
>>>
>>> Sorry if I forgot anyone who volunteered to help out with MMC patches.
>>>
>>> drivers/mmc/host/tmio_mmc.c | 21 +++++++++++++++++++++
>>> drivers/mmc/host/tmio_mmc.h | 3 +++
>>> include/linux/mfd/tmio.h | 1 +
>>> 3 files changed, 25 insertions(+), 0 deletions(-)
>>>
>>> diff --git a/drivers/mmc/host/tmio_mmc.c b/drivers/mmc/host/tmio_mmc.c
>>> index c246191..2a01572 100644
>>> --- a/drivers/mmc/host/tmio_mmc.c
>>> +++ b/drivers/mmc/host/tmio_mmc.c
>>> @@ -567,6 +576,11 @@ static int __devinit tmio_mmc_probe(struct platform_device *dev)
>>> goto unmap_cnf;
>>> }
>>>
>>> + host->clk = clk_get(&dev->dev, pdata->clk_name);
>>
>> Instead of pdata->clk_name, this should be either NULL or better
>> "HCLK" (to differentiate from CLK32, not sure if we want to be able to
>> toggle that, too, in the future).
>> Passing the clock consumer ID via pdata is just wrong and shouldn't be
>> needed with clkdev.
>
> Really? I think that depends on the clock framework implementation.
> Remember that this needs to work on other architectures than just ARM.
Oh, clkdev is an ARM only thing. Maybe it would be worthwile to make
this even more generic instead?
regards
Philipp
next prev parent reply other threads:[~2009-07-29 15:33 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
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 [this message]
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=74d0deb30907290833m3d1ff596s180759fb961a8a8d@mail.gmail.com \
--to=philipp.zabel@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=damm@opensource.se \
--cc=g.liakhovetski@gmx.de \
--cc=ian@mnementh.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--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
Powered by JetHome