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

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20130111105938.GU20956@opensource.wolfsonmicro.com>
Date:	Fri, 11 Jan 2013 10:59:38 +0000
From:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
To:	"Rafael J. Wysocki" <rjw@...k.pl>
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 Thu, Jan 10, 2013 at 10:56:36PM +0100, Rafael J. Wysocki wrote:
> On Thursday, January 10, 2013 03:58:52 PM Mika Westerberg wrote:

> > 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.

The clock is going to be there in the SoC - given that you're just
exposing a fixed rate clock it's not going to do anything except use a
little memory if its' there.

Download attachment "signature.asc" of type "application/pgp-signature" (837 bytes)