[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <90529114.hOo9bzgA6o@vostro.rjw.lan>
Date: Thu, 10 Jan 2013 14:18:08 +0100
From: "Rafael J. Wysocki" <rjw@...k.pl>
To: Mark Brown <broonie@...nsource.wolfsonmicro.com>
Cc: Mika Westerberg <mika.westerberg@...ux.intel.com>,
linux-kernel@...r.kernel.org, grant.likely@...retlab.ca,
linus.walleij@...aro.org, eric.y.miao@...il.com,
linux@....linux.org.uk, haojian.zhuang@...il.com,
chao.bi@...el.com, "H. Peter Anvin" <hpa@...ux.intel.com>
Subject: Re: [PATCH 05/11] spi/pxa2xx: make clock rate configurable from platform data
On Thursday, January 10, 2013 12:51:59 PM Mark Brown wrote:
> On Thu, Jan 10, 2013 at 01:54:41PM +0100, Rafael J. Wysocki wrote:
> > On Thursday, January 10, 2013 02:38:37 PM Mika Westerberg wrote:
>
> > > 3. We make the acpi_create_platform_device() match on, lets say
> > > "INT33C" (a partial match), and in such case it assumes that we are
> > > running on Lynxpoint. It will then create platform device for 'clk-lpt'.
>
> > > 4. Now the clk-lpt driver creates the clocks.
>
> > > 5. The SPI driver gets the clock it wants.
>
> > That sounds reasonable to me. Mark, what do you think?
>
> Sounds sensible, yes - about what I'd expect. Is it possible to match
> on CPUID or similar information (given that this is all in the SoC)
> instead of ACPI, that might be more robust I guess?
This particular part may be present in different SoCs.
Thanks,
Rafael
--
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists