From mboxrd@z Thu Jan 1 00:00:00 1970 From: Timur Tabi Subject: Re: [PATCH 3/4] [v6] pinctrl: qcom: disable GPIO groups with no pins Date: Thu, 16 Nov 2017 20:58:57 -0600 Message-ID: References: <1510096056-13765-1-git-send-email-timur@codeaurora.org> <1510096056-13765-4-git-send-email-timur@codeaurora.org> <20171117024332.GU11955@codeaurora.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20171117024332.GU11955@codeaurora.org> Content-Language: en-US Sender: linux-gpio-owner@vger.kernel.org To: Stephen Boyd Cc: linux-arm-msm@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-gpio@vger.kernel.org, Linus Walleij , Andy Shevchenko , Mika Westerberg , thierry.reding@gmail.com, david.brown@linaro.org, andy.gross@linaro.org, Bjorn Andersson List-Id: linux-arm-msm@vger.kernel.org On 11/16/17 8:43 PM, Stephen Boyd wrote: >> Most access to unavailable GPIOs can be blocked via the gpio_chip.request >> function. The one exception is when gpiochip_add_data() scans all of > If patch 1 is applied is this statement still true? Nope. >> the GPIOs without "requesting" them. To cover this case, > s/GPIOs/GPIOs for their direction/ perhaps? Ok. -- Qualcomm Datacenter Technologies, Inc. as an affiliate of Qualcomm Technologies, Inc. Qualcomm Technologies, Inc. is a member of the Code Aurora Forum, a Linux Foundation Collaborative Project.