From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mika Westerberg Subject: Re: [PATCH RESEND] pinctrl: intel: Turn Baytrail support to tristate Date: Thu, 26 Jan 2017 11:38:23 +0200 Message-ID: <20170126093823.GG17297@lahna.fi.intel.com> References: <20170125162608.58bfbfb1@endymion> <20170126091931.GD17297@lahna.fi.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from mga05.intel.com ([192.55.52.43]:12742 "EHLO mga05.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753169AbdAZJi2 (ORCPT ); Thu, 26 Jan 2017 04:38:28 -0500 Content-Disposition: inline In-Reply-To: Sender: linux-gpio-owner@vger.kernel.org List-Id: linux-gpio@vger.kernel.org To: Takashi Iwai Cc: Linus Walleij , Jean Delvare , Paul Gortmaker , "linux-gpio@vger.kernel.org" , LKML , Heikki Krogerus , Mathias Nyman On Thu, Jan 26, 2017 at 10:26:56AM +0100, Takashi Iwai wrote: > I guess it would break things on some machines if the module loading > order isn't setup properly. For example, it's known that > pinctrl-cherrytrail breaks MMC or others if it's loaded too lately. Yes, if you have rootfs on eMMC and it requires a GPIO then of course you need to make sure your initrd includes the necessary drivers. Same goes with other media that can be used as rootfs.