From patchwork Mon Aug 7 11:01:56 2017 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Michal Simek X-Patchwork-Id: 798584 Return-Path: X-Original-To: incoming@patchwork.ozlabs.org Delivered-To: patchwork-incoming@bilbo.ozlabs.org Authentication-Results: ozlabs.org; spf=none (mailfrom) smtp.mailfrom=vger.kernel.org (client-ip=209.132.180.67; helo=vger.kernel.org; envelope-from=linux-gpio-owner@vger.kernel.org; receiver=) Authentication-Results: ozlabs.org; dkim=fail reason="signature verification failed" (2048-bit key; unprotected) header.d=monstr-eu.20150623.gappssmtp.com header.i=@monstr-eu.20150623.gappssmtp.com header.b="MxGzcZkP"; dkim-atps=neutral Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by ozlabs.org (Postfix) with ESMTP id 3xQvlP1xhQz9t2R for ; Mon, 7 Aug 2017 21:03:13 +1000 (AEST) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753039AbdHGLCM (ORCPT ); Mon, 7 Aug 2017 07:02:12 -0400 Received: from mail-wm0-f67.google.com ([74.125.82.67]:35735 "EHLO mail-wm0-f67.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752938AbdHGLCI (ORCPT ); Mon, 7 Aug 2017 07:02:08 -0400 Received: by mail-wm0-f67.google.com with SMTP id r77so611537wmd.2 for ; Mon, 07 Aug 2017 04:02:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monstr-eu.20150623.gappssmtp.com; s=20150623; h=sender:from:to:cc:subject:date:message-id:in-reply-to:references :in-reply-to:references; bh=ADh2/sbrWg87AU37cbuq+BMG731P0x7NaTozX9aBvlk=; b=MxGzcZkPi9BaE5oXJ6kqgUgb4yAzlHHZorJ3V/KpYPoQz2TwabVErdKoqhmhSqdPH8 ztYO0eg/bIeIc5DMAffcPmrdCauRrmGqHM2gTEWdGhbkzifSY9V+eGX3ftOWlj/Ca6jB HJ7NEi5UYfNgb5ilQE2c4scrPaNZgvU11l38yXwcuTRs4MxKzUABo0qSNvcaGXbhkRmu MtacVFu/lflYvhnpzZvLw+/mkT0FUx6uIkoy6VVG6A6actnTBdpo8DJ/mpLIB6XX1sz6 cNGEvlhSIA2qiG8gUwezbibnkWyvlYwMgwuxcviyg8AIoHXcGog0DTw0H+E45thld6BE TeJA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:from:to:cc:subject:date:message-id :in-reply-to:references:in-reply-to:references; bh=ADh2/sbrWg87AU37cbuq+BMG731P0x7NaTozX9aBvlk=; b=tiCrLSeE+8WdUECHA0POsGhA/6IzxENLI15GxoNpb129Dk1CMqDPRaXtSRHvXdfnRV s9Vhx9s1szbiRW2/WyudmNFvPeSt8Pop7CR1BUAIg49/LbkEX5wwPjP0uX3MHfRo0dhi vEscyLXB4V+UCGaQTBE4+MqIPYVITZV+SybhfSP1TRqc61SP0Gq35qGKgv7+bfUiSd7+ OlPVFteFFKgBJ8UO75NWUU0dOzDCHlcuQHio2tzk7I8/5gu8coXeesbUHeuwWfw3UP7x l0ScQtTypwXCHM+OqnmjbofDykWxDR+Xs0S9o2bWsB6AHSd8/t283qsQ9FyLzmP03t0H CQDQ== X-Gm-Message-State: AHYfb5h6CRZmCEkOyqso9Zvuk8BALq9T73ZhIyWSxRtbtZVerpTve3A5 HTrsmohOALfykZGk X-Received: by 10.28.34.130 with SMTP id i124mr448576wmi.135.1502103727725; Mon, 07 Aug 2017 04:02:07 -0700 (PDT) Received: from localhost (nat-35.starnet.cz. [178.255.168.35]) by smtp.gmail.com with ESMTPSA id t66sm9833563wrc.36.2017.08.07.04.02.06 (version=TLS1_2 cipher=AES128-SHA bits=128/128); Mon, 07 Aug 2017 04:02:07 -0700 (PDT) From: Michal Simek To: linux-kernel@vger.kernel.org, monstr@monstr.eu Cc: Nava kishore Manne , =?UTF-8?q?S=C3=B6ren=20Brinkmann?= , Steffen Trumtrar , Linus Walleij , Peter Crosthwaite , linux-gpio@vger.kernel.org, Rob Herring , Josh Cartwright , linux-arm-kernel@lists.infradead.org Subject: [PATCH 3/8] gpio: zynq: Shift zynq_gpio_init() to subsys_initcall level Date: Mon, 7 Aug 2017 13:01:56 +0200 Message-Id: X-Mailer: git-send-email 1.9.1 In-Reply-To: References: In-Reply-To: References: Sender: linux-gpio-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-gpio@vger.kernel.org From: Nava kishore Manne In general situation on-SoC GPIO controller drivers should be probed after pinctrl/pinmux controller driver, because on-SoC GPIOs utilize a pin/pad as a resource provided and controlled by pinctrl subsystem. GPIO must come after pinctrl as gpios may need to mux pins....etc Looking at Xilinx SoC series pinctrl drivers, zynq*_pinctrl_init() functions are called at arch_initcall init levels, so the change of initcall level for gpio-zynq driver from postcore_initcall to subsys_initcall level is sufficient. Also note that the most of GPIO controller drivers settled at subsys_initcall level. If pinctrl subsystem manages pads with GPIO functions, the change is needed to avoid unwanted driver probe deferrals during kernel boot. Signed-off-by: Nava kishore Manne Signed-off-by: Michal Simek --- drivers/gpio/gpio-zynq.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/gpio/gpio-zynq.c b/drivers/gpio/gpio-zynq.c index 5198fa6e016a..bcf11f0ef5c3 100644 --- a/drivers/gpio/gpio-zynq.c +++ b/drivers/gpio/gpio-zynq.c @@ -929,7 +929,7 @@ static int __init zynq_gpio_init(void) { return platform_driver_register(&zynq_gpio_driver); } -postcore_initcall(zynq_gpio_init); +subsys_initcall(zynq_gpio_init); static void __exit zynq_gpio_exit(void) {