Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S965016AbaKNJk6 (ORCPT ); Fri, 14 Nov 2014 04:40:58 -0500 Received: from mail-ie0-f174.google.com ([209.85.223.174]:59260 "EHLO mail-ie0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754852AbaKNJk4 (ORCPT ); Fri, 14 Nov 2014 04:40:56 -0500 MIME-Version: 1.0 In-Reply-To: <20141104215153.GA25606@psi-dev26.jf.intel.com> References: <20141103152743.GB1618@lahna.fi.intel.com> <20141103154207.GC1618@lahna.fi.intel.com> <20141103155011.GH27425@saruman> <20141103184247.GD1618@lahna.fi.intel.com> <20141103221903.GA20305@psi-dev26.jf.intel.com> <20141104075936.GF1618@lahna.fi.intel.com> <20141104180526.GB2224@psi-dev26.jf.intel.com> <20141104185702.GR1618@lahna.fi.intel.com> <20141104191115.GC2224@psi-dev26.jf.intel.com> <20141104193424.GT1618@lahna.fi.intel.com> <20141104215153.GA25606@psi-dev26.jf.intel.com> Date: Fri, 14 Nov 2014 10:40:55 +0100 Message-ID: Subject: Re: [PATCH] pinctrl: baytrail: show output gpio state correctly on Intel Baytrail From: Linus Walleij To: David Cohen , Greg Kroah-Hartman , Grant Likely Cc: Mika Westerberg , Felipe Balbi , "linux-kernel@vger.kernel.org" , "linux-gpio@vger.kernel.org" , stable , Mathias Nyman Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Nov 4, 2014 at 10:51 PM, David Cohen wrote: > On Tue, Nov 04, 2014 at 09:34:24PM +0200, Mika Westerberg wrote: >> to a list of devices we depend on, we can defer this particular driver >> going further in probe until all the dependencies listed in _DEP are >> resolved. > > That's the best way to prevent this issue IMHO, but looks like it's > already being addressed: > https://lkml.org/lkml/2014/10/27/455 -EPROVE_DEFER will solve (hackishly) the probing problem. It will not solve remove() or power up/down sequencing. Yours, Linus Walleij -- 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/