From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757292AbcC2PFV (ORCPT ); Tue, 29 Mar 2016 11:05:21 -0400 Received: from mout.kundenserver.de ([212.227.126.134]:64265 "EHLO mout.kundenserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753216AbcC2PFT (ORCPT ); Tue, 29 Mar 2016 11:05:19 -0400 From: Arnd Bergmann To: linux-arm-kernel@lists.infradead.org Cc: Viresh Kumar , Rafael Wysocki , arnd.bergmann@linaro.org, Kukjin Kim , Krzysztof Kozlowski , kgene.kim@samsung.com, heiko@sntech.de, xf@rock-chips.com, mmcclint@codeaurora.org, linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org, linux-samsung-soc@vger.kernel.org, linaro-kernel@lists.linaro.org Subject: Re: [PATCH V2 3/3] cpufreq: exynos: Use generic platdev driver Date: Tue, 29 Mar 2016 17:04:26 +0200 Message-ID: <3810049.oQlCXiQ5bk@wuerfel> User-Agent: KMail/4.11.5 (Linux/3.16.0-10-generic; KDE/4.11.5; x86_64; ; ) In-Reply-To: <81a8da75a0e7783e2b47f9e04297f167e8134afe.1459233524.git.viresh.kumar@linaro.org> References: <81a8da75a0e7783e2b47f9e04297f167e8134afe.1459233524.git.viresh.kumar@linaro.org> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Provags-ID: V03:K0:MAFld+3VQEy4EJ3I/ZepEiYJzfCbn0Z+bpLV9QjlyXpmvT3FL9j r7eVvL6nMRPPH93goIw9TSouyx6t3aFAeFdL0wrkpnq3Emvq6IwIJb+MqYpwK4QvzVePwhO cIpv07xpcQVznsU2+Qe1B9BS7bSFC7NHUz3k2fuQoI1Z3foQWQrW7TCHuO4cggwtabQoSTv Shht+7WdKoRElsnFmCPSg== X-UI-Out-Filterresults: notjunk:1;V01:K0:RqTskrPFEtc=:YH+KLR+mgU3lXxkx0cBELI /LXXIOca/2i6Gj74x1wkwz1V/bMy1EzbHjSQlJ9osNzyNdLa9izJIdOsvBuj7gSoKHkpDZooN suyVNW904wAenaQtLIeJaimMYbwdFIH5S/+Uwz3LJUVwGuCAtju5W/RXbUKnxrqt+nNZgeeIf J3A5xTi7HEz4+htv8cpCBJ6FhD0Qd2rJDWYFat79oiw2pUMkk+NV0jJyEofJulSUvZzxHlnfO lDACIQN2/gTF1ARSQWWVC/UNCQiuUwlA03uqvQUZUcFDsdU28zWACEJDp/ALHx1Ej3+UK7tCT RPZSl32burqJY+B7uIyUD5F4G6rnCXVs9QxejgoLlVt0OxWukhA9NVrEn60VDql2U8UWg6fYf PdtmfZHscPhB7P+ayHcAfvHCO6D6CpXWVHWgfjwU6xL2fgogew3gf8V2rMsynmCkGCgqMqOyj 0Sy7UtGaUd69fVMB8zIYTeIpEabyGutMuJiz1gRUjagsCu3dlr/3xYYhhABdIgdBoy/Lrkoyi Za0HwyrZReFfGR2XfRFhDRU0sgyAryt9o7doqshVbDjOETsLOzkko686Tn6F/oQAcfBL6dLxf AtdnUj8TWmk+kVudXF5GbwtPrGZi1Eg576DiU01VCzxRJ2COi7JwBXt5XgjRD4+b+R2Vln6Fq sWknY6f8PyndOR+X2+w0n6L3E0NsK2ImU+9wtEUWcjdU4j6mEzissOoUTc3vcWDfEHBEdbvMm IT0sG929ulfJBuCY Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tuesday 29 March 2016 12:09:49 Viresh Kumar wrote: > -static void __init exynos_cpufreq_init(void) > -{ > - struct device_node *root = of_find_node_by_path("/"); > - const struct of_device_id *match; > - > - match = of_match_node(exynos_cpufreq_matches, root); > - if (!match) { > - platform_device_register_simple("exynos-cpufreq", -1, NULL, 0); > - return; > - } > - > - platform_device_register_simple(match->data, -1, NULL, 0); > -} How is the "exynos-cpufreq" case handled now? Is that no longer used now? I assume the patch is correct based on Krzysztof's review, but it might be good to explain this better. Arnd