Re: [PATCH 05/11] spi/pxa2xx: make clock rate configurable from platform data

[Rafael J. Wysocki]

On Thursday, January 10, 2013 03:58:52 PM Mika Westerberg wrote:
> On Thu, Jan 10, 2013 at 01:33:19PM +0000, Mark Brown wrote:
> > On Thu, Jan 10, 2013 at 02:18:08PM +0100, Rafael J. Wysocki wrote:
> > > On Thursday, January 10, 2013 12:51:59 PM Mark Brown wrote:
> > 
> > > > 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.
> > 
> > Right, but I'd expect you could enumerate the SoCs?  Someone might
> > decide to change the clock configuration for future SoCs anyway.
> 
> Well, they can use the same LPSS block with a different CPU but then we
> expect the ACPI IDs to change as well (so we can then make another set of
> clocks for those).

Also, as I said in another message, even if the LPSS block is used, the SPI
may not be exposed to us by the BIOS, so SoC enumeration is not sufficient
in general.

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@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/