This is second iteration of the series. First revision is available here: https://lkml.org/lkml/2013/1/14/213 Idea is to let the LPSS peripheral drivers to use common clk framework to get clock rate or enable/disable the functional clock. The discussion started in this 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. We try to address that in this series. Instead of enabling the common clk framework by default we place it under CONFIG_X86_INTEL_LPSS config option. This option then selects what is necessary to support the LPSS peripheral drivers. We then create the Lynxpoint clock tree and populate it accordingly. Changes to previous version: - add config option CONFIG_X86_INTEL_LPSS - pass flags to acpi_create_platform_device() instead of calling function in drivers/acpi/scan.c - create the clock platform devices in drivers/acpi/acpi_platform.c Please review. Mika Westerberg (3): x86: add support for Intel Low Power Subsystem clk: x86: add support for Lynxpoint LPSS clocks ACPI / platform: create LPSS clocks if Lynxpoint devices are found during scan arch/x86/Kconfig | 10 +++++ drivers/acpi/acpi_platform.c | 25 ++++++++++- drivers/acpi/internal.h | 6 ++- drivers/acpi/scan.c | 22 +++++----- drivers/clk/Makefile | 1 + drivers/clk/x86/Makefile | 2 + drivers/clk/x86/clk-lpss.c | 99 ++++++++++++++++++++++++++++++++++++++++++ drivers/clk/x86/clk-lpss.h | 36 +++++++++++++++ drivers/clk/x86/clk-lpt.c | 86 ++++++++++++++++++++++++++++++++++++ 9 files changed, 275 insertions(+), 12 deletions(-) create mode 100644 drivers/clk/x86/Makefile create mode 100644 drivers/clk/x86/clk-lpss.c create mode 100644 drivers/clk/x86/clk-lpss.h create mode 100644 drivers/clk/x86/clk-lpt.c -- 1.7.10.4 -- To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
