From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752271AbcERXbP (ORCPT ); Wed, 18 May 2016 19:31:15 -0400 Received: from devils.ext.ti.com ([198.47.26.153]:54228 "EHLO devils.ext.ti.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751386AbcERXbL (ORCPT ); Wed, 18 May 2016 19:31:11 -0400 From: Dave Gerlach To: , , , , CC: Viresh Kumar , Rob Herring , "Rafael J . Wysocki" , Tony Lindgren , Mark Rutland , Nishanth Menon , Dave Gerlach , Yegor Yefremov Subject: [PATCH 0/2] cpufreq: Introduce TI CPUFreq/OPP Driver Date: Wed, 18 May 2016 18:30:24 -0500 Message-ID: X-Mailer: git-send-email 2.7.3 MIME-Version: 1.0 Content-Type: text/plain Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi, This series introduces the ti-cpufreq driver which parses SoC data and provides opp-supported-hw data to the OPP core in order to enable the proper OPPs for the silicon in use. It still relies on the cpufreq-dt driver to actually provide cpufreq and creates the "cpufreq-dt" platform driver after it probes as the sti-cpufreq driver does. This series will add support for am335x, am437x, dra7xx, and am57xx platforms, otherwise other TI devices will rely on the recently introduced cpufreq-dt-platdev code [1] to create the cpufreq-dt device. This means that the aforementioned platforms do *not* need to be added to cpufreq-dt-platdev. DTS patches for the above platforms are being sent in a separate series right after this one. Even without merging the DTS series, this series will not break backwards compatibility for those platforms above that already have operating-points v1 tables as the ti-cpufreq driver fails through and creates the cpufreq-dt platform device if no operating-points-v2 table is found. This series is based on linux-next next-20160517 tag, it depends on [2] which drops the default creation of the cpufreq-dt device from omap platform code, otherwise we'd end up with a duplicate because this driver creates it also. Regards, Dave [1] http://permalink.gmane.org/gmane.linux.power-management.general/73887 [2] http://permalink.gmane.org/gmane.linux.power-management.general/75215 Dave Gerlach (2): Documentation: dt: add bindings for ti-cpufreq cpufreq: ti: Add cpufreq driver to determine available OPPs at runtime .../devicetree/bindings/cpufreq/ti-cpufreq.txt | 89 ++++++++ drivers/cpufreq/Kconfig.arm | 11 + drivers/cpufreq/Makefile | 1 + drivers/cpufreq/ti-cpufreq.c | 254 +++++++++++++++++++++ 4 files changed, 355 insertions(+) create mode 100644 Documentation/devicetree/bindings/cpufreq/ti-cpufreq.txt create mode 100644 drivers/cpufreq/ti-cpufreq.c -- 2.7.3 From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dave Gerlach Subject: [PATCH 0/2] cpufreq: Introduce TI CPUFreq/OPP Driver Date: Wed, 18 May 2016 18:30:24 -0500 Message-ID: Mime-Version: 1.0 Content-Type: text/plain Return-path: Sender: devicetree-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org, linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, linux-pm-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org Cc: Viresh Kumar , Rob Herring , "Rafael J . Wysocki" , Tony Lindgren , Mark Rutland , Nishanth Menon , Dave Gerlach , Yegor Yefremov List-Id: devicetree@vger.kernel.org Hi, This series introduces the ti-cpufreq driver which parses SoC data and provides opp-supported-hw data to the OPP core in order to enable the proper OPPs for the silicon in use. It still relies on the cpufreq-dt driver to actually provide cpufreq and creates the "cpufreq-dt" platform driver after it probes as the sti-cpufreq driver does. This series will add support for am335x, am437x, dra7xx, and am57xx platforms, otherwise other TI devices will rely on the recently introduced cpufreq-dt-platdev code [1] to create the cpufreq-dt device. This means that the aforementioned platforms do *not* need to be added to cpufreq-dt-platdev. DTS patches for the above platforms are being sent in a separate series right after this one. Even without merging the DTS series, this series will not break backwards compatibility for those platforms above that already have operating-points v1 tables as the ti-cpufreq driver fails through and creates the cpufreq-dt platform device if no operating-points-v2 table is found. This series is based on linux-next next-20160517 tag, it depends on [2] which drops the default creation of the cpufreq-dt device from omap platform code, otherwise we'd end up with a duplicate because this driver creates it also. Regards, Dave [1] http://permalink.gmane.org/gmane.linux.power-management.general/73887 [2] http://permalink.gmane.org/gmane.linux.power-management.general/75215 Dave Gerlach (2): Documentation: dt: add bindings for ti-cpufreq cpufreq: ti: Add cpufreq driver to determine available OPPs at runtime .../devicetree/bindings/cpufreq/ti-cpufreq.txt | 89 ++++++++ drivers/cpufreq/Kconfig.arm | 11 + drivers/cpufreq/Makefile | 1 + drivers/cpufreq/ti-cpufreq.c | 254 +++++++++++++++++++++ 4 files changed, 355 insertions(+) create mode 100644 Documentation/devicetree/bindings/cpufreq/ti-cpufreq.txt create mode 100644 drivers/cpufreq/ti-cpufreq.c -- 2.7.3 -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html From mboxrd@z Thu Jan 1 00:00:00 1970 From: d-gerlach@ti.com (Dave Gerlach) Date: Wed, 18 May 2016 18:30:24 -0500 Subject: [PATCH 0/2] cpufreq: Introduce TI CPUFreq/OPP Driver Message-ID: To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org Hi, This series introduces the ti-cpufreq driver which parses SoC data and provides opp-supported-hw data to the OPP core in order to enable the proper OPPs for the silicon in use. It still relies on the cpufreq-dt driver to actually provide cpufreq and creates the "cpufreq-dt" platform driver after it probes as the sti-cpufreq driver does. This series will add support for am335x, am437x, dra7xx, and am57xx platforms, otherwise other TI devices will rely on the recently introduced cpufreq-dt-platdev code [1] to create the cpufreq-dt device. This means that the aforementioned platforms do *not* need to be added to cpufreq-dt-platdev. DTS patches for the above platforms are being sent in a separate series right after this one. Even without merging the DTS series, this series will not break backwards compatibility for those platforms above that already have operating-points v1 tables as the ti-cpufreq driver fails through and creates the cpufreq-dt platform device if no operating-points-v2 table is found. This series is based on linux-next next-20160517 tag, it depends on [2] which drops the default creation of the cpufreq-dt device from omap platform code, otherwise we'd end up with a duplicate because this driver creates it also. Regards, Dave [1] http://permalink.gmane.org/gmane.linux.power-management.general/73887 [2] http://permalink.gmane.org/gmane.linux.power-management.general/75215 Dave Gerlach (2): Documentation: dt: add bindings for ti-cpufreq cpufreq: ti: Add cpufreq driver to determine available OPPs at runtime .../devicetree/bindings/cpufreq/ti-cpufreq.txt | 89 ++++++++ drivers/cpufreq/Kconfig.arm | 11 + drivers/cpufreq/Makefile | 1 + drivers/cpufreq/ti-cpufreq.c | 254 +++++++++++++++++++++ 4 files changed, 355 insertions(+) create mode 100644 Documentation/devicetree/bindings/cpufreq/ti-cpufreq.txt create mode 100644 drivers/cpufreq/ti-cpufreq.c -- 2.7.3