From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754240AbcI3CWx (ORCPT ); Thu, 29 Sep 2016 22:22:53 -0400 Received: from mail-pa0-f43.google.com ([209.85.220.43]:35693 "EHLO mail-pa0-f43.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750776AbcI3CWo (ORCPT ); Thu, 29 Sep 2016 22:22:44 -0400 Date: Fri, 30 Sep 2016 07:52:40 +0530 From: Viresh Kumar To: linus.walleij@linaro.org, Vladimir Zapolskiy Cc: Stefan Agner , shawnguo@kernel.org, aalonso@freescale.com, b38343@freescale.com, ldewangan@nvidia.com, van.freenix@gmail.com, p.zabel@pengutronix.de, linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] pinctrl: freescale: avoid overwriting pin config when freeing GPIO Message-ID: <20160930022240.GE14138@vireshk-i7> References: <20160927002650.4316-1-stefan@agner.ch> <17317e62-d9bf-4ab3-35b5-f2f9a4dcbedd@mentor.com> <960b299c947424598ec26bfcb36fd96b@agner.ch> <671a23a9ccdbdd6594ad89bf496c1490@agner.ch> <20160928020052.GB2551@vireshk-i7> <1a113c0f-4ee3-e61a-8927-b5e8b558822c@mentor.com> <20160929064605.GB14138@vireshk-i7> <77b229dc-3fce-b953-b53b-a94a1fb0e109@mentor.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <77b229dc-3fce-b953-b53b-a94a1fb0e109@mentor.com> User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 29-09-16, 15:16, Vladimir Zapolskiy wrote: > If you look at the top I agree that this solution may be only one platform > specific, but it fixes the broken driver of i.MX I2C bus controller. Yeah, I saw that.. > Why do you get an impression that it looks like a hack? Because we have to reorder things to make it work on a platform. This may break things on other platforms and we don't know about it yet. > Why pinctrl_select_state() is not done in gpio_request_one()? Because > the first function gets pin mux/config setting and the second does not. > How do you intend to get pin mux/config setting in gpio_request_one()? Lets see what Linus has to say on this.. > Anyway I don't see any problems in pinctrl or gpio subsystems, the bugs > must be addressed and fixed in i2c. I think it can be a gpio driver specific thing as well and not really subsystem level one. -- viresh