All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: linux-kernel@vger.kernel.org
Cc: Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
	x86@kernel.org, Len Brown <lenb@kernel.org>,
	"Rafael J. Wysocki" <rjw@sisk.pl>,
	Mike Turquette <mturquette@linaro.org>,
	Arnd Bergmann <arnd@arndb.de>,
	Linus Walleij <linus.walleij@linaro.org>,
	Mark Brown <broonie@opensource.wolfsonmicro.com>,
	Heikki Krogerus <heikki.krogerus@linux.intel.com>,
	linux-acpi@vger.kernel.org
Subject: Re: [PATCH 0/3] x86: enable common clk and add support for Lynxpoint clocks
Date: Tue, 15 Jan 2013 07:27:23 +0200	[thread overview]
Message-ID: <20130115052723.GM13897@intel.com> (raw)
In-Reply-To: <1358174788-24439-1-git-send-email-mika.westerberg@linux.intel.com>

On Mon, Jan 14, 2013 at 04:46:25PM +0200, Mika Westerberg wrote:
> Hi all,
> 
> The discussion that lead to this patch series starts from the below thread:
> 
> 	http://thread.gmane.org/gmane.linux.kernel/1417691
> 
> In summary, there is no point in adding a special case code to the drivers
> in order to pass them a fixed clock rate, but instead x86 should just
> enable common clk subsystem and take advantage of it.
> 
> This has been proposed before by Mark Brown but for some reason it has not
> merged into x86 tree.
> 
> This series tries to do the same but in this time we have real users for
> the clk API.
> 
> [1/3] Enables the common clk framework on x86
> [2/3] Adds Intel Lynxpoint Low Power Subsystem specific clocks as platform
>       driver.
> [3/3] Creates the platform device for the LPSS clocks driver if we find out
>       that the Lynxpoint LPSS devices are available.
> 
> This series is based on Rafael's linux-pm/linux-next branch because there
> is a dependency to the ACPI scan rework by Rafael.

I meant that they apply on top of 3.8-rcX but in order to patch [2/3] to
work it needs to have the ACPI scan rework patches. Otherwise it is not
able to find the base addresses of the devices.

      parent reply	other threads:[~2013-01-15  5:23 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-14 14:46 [PATCH 0/3] x86: enable common clk and add support for Lynxpoint clocks Mika Westerberg
2013-01-14 14:46 ` [PATCH 1/3] x86: enable common clk on x86 Mika Westerberg
2013-01-15 23:59   ` Rafael J. Wysocki
2013-01-16  5:20     ` Mika Westerberg
2013-01-16 15:01       ` Rafael J. Wysocki
2013-01-16 15:28         ` Mika Westerberg
2013-01-17 22:38           ` Rafael J. Wysocki
2013-01-14 14:46 ` [PATCH 2/3] clk: x86: add support for Lynxpoint LPSS clocks Mika Westerberg
2013-01-15  3:11   ` Mark Brown
2013-01-14 14:46 ` [PATCH 3/3] ACPI: create Lynxpoint clocks if LPSS devices are found during scan Mika Westerberg
2013-01-17 23:07   ` Rafael J. Wysocki
2013-01-15  5:27 ` Mika Westerberg [this message]

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=20130115052723.GM13897@intel.com \
    --to=mika.westerberg@linux.intel.com \
    --cc=arnd@arndb.de \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=heikki.krogerus@linux.intel.com \
    --cc=hpa@zytor.com \
    --cc=lenb@kernel.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=mturquette@linaro.org \
    --cc=rjw@sisk.pl \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.