From mboxrd@z Thu Jan 1 00:00:00 1970 From: Linus Walleij Subject: Re: [PATCH v3 2/3] gpiolib: Support 'gpio-reserved-ranges' property Date: Tue, 27 Mar 2018 15:24:16 +0200 Message-ID: References: <20180321165848.89751-1-swboyd@chromium.org> <20180321165848.89751-3-swboyd@chromium.org> <1521655150.23017.79.camel@linux.intel.com> <152166234504.91116.14942145962035607739@swboyd.mtv.corp.google.com> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Return-path: In-Reply-To: <152166234504.91116.14942145962035607739@swboyd.mtv.corp.google.com> Sender: linux-kernel-owner@vger.kernel.org To: Stephen Boyd Cc: Andy Shevchenko , "open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" , linux-arm-msm@vger.kernel.org, Timur Tabi , Stephen Boyd , "linux-kernel@vger.kernel.org" , Bjorn Andersson , Grant Likely , "open list:GPIO SUBSYSTEM" , Linux ARM List-Id: linux-arm-msm@vger.kernel.org On Wed, Mar 21, 2018 at 8:59 PM, Stephen Boyd wrote: > Quoting Andy Shevchenko (2018-03-21 10:59:10) >> On Wed, 2018-03-21 at 09:58 -0700, Stephen Boyd wrote: >> > From: Stephen Boyd >> > >> > Some qcom platforms make some GPIOs or pins unavailable for use by >> > non-secure operating systems, and thus reading or writing the >> > registers >> > for those pins will cause access control issues. Add support for a DT >> > property to describe the set of GPIOs that are available for use so >> > that >> > higher level OSes are able to know what pins to avoid reading/writing. >> > Non-DT platforms can add support by directly updating the >> > chip->valid_mask. >> >> > Signed-off-by: Stephen Boyd >> > Signed-off-by: Stephen Boyd >> >> Hmm... > > Don't look closely! :P Same physical person acting on behalf of two different legal entities right? Seems OK to me. Yours, Linus Walleij