Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757428Ab2JQQfx (ORCPT ); Wed, 17 Oct 2012 12:35:53 -0400 Received: from mail-ie0-f174.google.com ([209.85.223.174]:42674 "EHLO mail-ie0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756420Ab2JQQfv (ORCPT ); Wed, 17 Oct 2012 12:35:51 -0400 MIME-Version: 1.0 In-Reply-To: <1350401000-9453-1-git-send-email-s-guiriec@ti.com> References: <1350401000-9453-1-git-send-email-s-guiriec@ti.com> Date: Wed, 17 Oct 2012 22:05:50 +0530 Message-ID: Subject: Re: [PATCH] i2c: omap: adopt pinctrl support From: Shubhrajyoti Datta To: Sebastien Guiriec Cc: Tony Lindgren , Jean Delvare , Ben Dooks , Wolfram Sang , linux-omap@vger.kernel.org, linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org, Felipe Balbi , Shubhrajyoti Datta Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1183 Lines: 27 On Tue, Oct 16, 2012 at 8:53 PM, Sebastien Guiriec wrote: > Some GPIO expanders need some early pin control muxing. Due to > legacy boards sometimes the driver uses subsys_initcall instead of > module_init. This patch takes advantage of defer probe feature > and pin control in order to wait until pin control probing before > GPIO driver probing. It has been tested on OMAP5 board with TCA6424 > driver. > > log: > > [0.482299] omap_i2c i2c.15: could not find pctldev for node /ocp/pinmux@4a00 > 2840/pinmux_i2c5_pins, deferring probe > [0.482330] platform i2c.15: Driver omap_i2c requests probe deferral > [0.484466] Advanced Linux Sound Architecture Driver Initialized. > > [4.746917] omap_i2c i2c.15: bus 4 rev2.4.0 at 100 kHz > [4.755279] gpiochip_find_base: found new base at 477 > [4.761169] gpiochip_add: registered GPIOs 477 to 500 on device: tca6424a > Thanks, Acked-by: Shubhrajyoti D -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/