Received: by 10.213.65.68 with SMTP id h4csp1410145imn; Wed, 21 Mar 2018 10:00:17 -0700 (PDT) X-Google-Smtp-Source: AG47ELuXwV8lcPCiUIGbqf5bdCU0o0QT+fLb9IdBB5ZE96flFsvTBeZMX2r/wkD8YN0BOW8YmdfG X-Received: by 10.99.166.10 with SMTP id t10mr6111419pge.357.1521651617626; Wed, 21 Mar 2018 10:00:17 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1521651617; cv=none; d=google.com; s=arc-20160816; b=ABhV1T6cMQ2ctVmJldnJvcB0oyzOyXgTBpT6M8JnUstMcny5qx6bUGDTzcG56Yqn6T DidJsga35n3fPWKWNTqrcuujmcD7d617YrQB2PmvuPFM2NE5G0IIkhJfhk+cf8z49e8C NCq9vCFb35sim0eHIfii6FfVLMqdWsMICw0dVgRkasOUD4i1jzsujBzKGABMFz3tVCkA cojoYs1hdcQCizLVv/6jG/tBRy9vxJyv25KGC+LsoFBcuOUvRl0PcKBYnSP/+yc7K3vM dBCvbFJ7WXZTopP7jfB0P+7wvaAwfA6Rx5MmSe8ynmM5XlJj+sUpF+eqicac5NjoP8K0 0oRA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:references:in-reply-to:message-id:date :subject:cc:to:from:dkim-signature:arc-authentication-results; bh=IsEWvgJNcKsjkd8SgDGPMM8oASotOa0bRX2Uz5aPRz4=; b=MV+YJZHiPDUm2jDVbrx8gkSqib84QpesZwnLXwPUSVwZe9hYwNvYSp7hZ2dqBQpFiY OGnYHjrrxpP8oQQOm5r1chJR9ZaFWOWSzZufLpPpGADk26ujs0As740XVLih1InCsj6f z3lMNkUG1cllMeMTZLXRkTFAAcVyclGnmwMFpOPr/Rp+SC+wOs2+z10VOLWHoN1Xw0Ft xy4RJzrn336tRoaKCXw/UHN9mrbcYg/i2hWSvASUt4d2mNfxD6UjeGvoXWecAjFPWnWM rsBHGaxaHWQhW0516ZYzAP4htYrK9kjoLzY9EHUPPYB8BhWEucdKgawGnyjoMuHLAp9g s2eQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@chromium.org header.s=google header.b=eUZE7trA; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=chromium.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id b14si3021250pge.252.2018.03.21.10.00.02; Wed, 21 Mar 2018 10:00:17 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@chromium.org header.s=google header.b=eUZE7trA; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=chromium.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752161AbeCUQ66 (ORCPT + 99 others); Wed, 21 Mar 2018 12:58:58 -0400 Received: from mail-pf0-f194.google.com ([209.85.192.194]:38733 "EHLO mail-pf0-f194.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751901AbeCUQ6w (ORCPT ); Wed, 21 Mar 2018 12:58:52 -0400 Received: by mail-pf0-f194.google.com with SMTP id d26so2211868pfn.5 for ; Wed, 21 Mar 2018 09:58:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; h=from:to:cc:subject:date:message-id:in-reply-to:references; bh=IsEWvgJNcKsjkd8SgDGPMM8oASotOa0bRX2Uz5aPRz4=; b=eUZE7trArtnpGQ+ass4gltzLJ/Y2c6gKUuqIew50pDpt3ym2qEel822QDk7vVRsD6q SW0LMJ7wnJ+7TUbCN8o/kORcow6QCFrIzv3fSAlw2tX0BpLPVVNfnLuSBHOEURV/Mqhw v5xcLdeh//1xUdmCVyftf9fYcPE+wh6szSIP4= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id:in-reply-to :references; bh=IsEWvgJNcKsjkd8SgDGPMM8oASotOa0bRX2Uz5aPRz4=; b=Zg8kmBc1R9XCTA7dflyKUzH022uedxKinAdDWxeI60SRjZ0ucB4RApm1K2TxthV3wR IVyl2/ZkMaPXaItHxi65qnMv4lJ2bWd1QDZTkOC4L0HdHl7zyWQpniMGo1qj7+8oaKXx 5RcqKkgE40mw0lAPuVsaQVlPrpSBfak9vPP06wPE63tZA/zS2bChIfunJdzbuLW7TPLZ hwywnzC5/bvy6i2jNkfqUFyvThSMdP3YkeLwFD+WiIdkJEGkrF8MxXLISILw0dvFrPQt vyhS3wOSTwvr6nL4U6qCxJNLVTg21hzhP8tiXp+3jxiObsb0WEkSlb7G25eJgL4m/YAj dMMw== X-Gm-Message-State: AElRT7F60jWjTIgWgNazyrxQ5S6xxcNbyu9zvtzZrps4zafWyjbbI6Y0 CqtmftgGTnAwmdGvx+bY+dVc2A== X-Received: by 10.98.37.132 with SMTP id l126mr17746314pfl.102.1521651532265; Wed, 21 Mar 2018 09:58:52 -0700 (PDT) Received: from swboyd.mtv.corp.google.com ([2620:0:1000:1511:d30e:62c6:f82c:ff40]) by smtp.gmail.com with ESMTPSA id u28sm10121806pfl.19.2018.03.21.09.58.51 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 21 Mar 2018 09:58:51 -0700 (PDT) From: Stephen Boyd To: Linus Walleij Cc: Stephen Boyd , linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org, linux-arm-msm@vger.kernel.org, Timur Tabi , Bjorn Andersson , Grant Likely , linux-gpio@vger.kernel.org, Andy Shevchenko Subject: [PATCH v3 1/3] dt-bindings: gpio: Add a gpio-reserved-ranges property Date: Wed, 21 Mar 2018 09:58:46 -0700 Message-Id: <20180321165848.89751-2-swboyd@chromium.org> X-Mailer: git-send-email 2.16.2.804.g6dcf76e118-goog In-Reply-To: <20180321165848.89751-1-swboyd@chromium.org> References: <20180321165848.89751-1-swboyd@chromium.org> Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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. Introduce 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. Cc: Grant Likely Cc: Signed-off-by: Stephen Boyd Signed-off-by: Stephen Boyd --- Documentation/devicetree/bindings/gpio/gpio.txt | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/Documentation/devicetree/bindings/gpio/gpio.txt b/Documentation/devicetree/bindings/gpio/gpio.txt index b5de08e3b1a2..a7c31de29362 100644 --- a/Documentation/devicetree/bindings/gpio/gpio.txt +++ b/Documentation/devicetree/bindings/gpio/gpio.txt @@ -151,9 +151,9 @@ in a lot of designs, some using all 32 bits, some using 18 and some using first 18 GPIOs, at local offset 0 .. 17, are in use. If these GPIOs do not happen to be the first N GPIOs at offset 0...N-1, an -additional bitmask is needed to specify which GPIOs are actually in use, -and which are dummies. The bindings for this case has not yet been -specified, but should be specified if/when such hardware appears. +additional set of tuples is needed to specify which GPIOs are unusable, with +the gpio-reserved-ranges binding. This property indicates the start and size +of the GPIOs that can't be used. Optionally, a GPIO controller may have a "gpio-line-names" property. This is an array of strings defining the names of the GPIO lines going out of the @@ -178,6 +178,7 @@ gpio-controller@00000000 { gpio-controller; #gpio-cells = <2>; ngpios = <18>; + gpio-reserved-ranges = <0 4>, <12 2>; gpio-line-names = "MMC-CD", "MMC-WP", "VDD eth", "RST eth", "LED R", "LED G", "LED B", "Col A", "Col B", "Col C", "Col D", "Row A", "Row B", "Row C", "Row D", "NMI button", -- Sent by a computer through tubes