From patchwork Wed Sep 19 21:02:18 2018 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Patchwork-Submitter: =?utf-8?b?UmFmYcWCIE1pxYJlY2tp?= X-Patchwork-Id: 971937 Return-Path: X-Original-To: incoming@patchwork.ozlabs.org Delivered-To: patchwork-incoming@bilbo.ozlabs.org Authentication-Results: ozlabs.org; spf=none (mailfrom) smtp.mailfrom=vger.kernel.org (client-ip=209.132.180.67; helo=vger.kernel.org; envelope-from=linux-gpio-owner@vger.kernel.org; receiver=) Authentication-Results: ozlabs.org; dmarc=pass (p=none dis=none) header.from=gmail.com Authentication-Results: ozlabs.org; dkim=pass (2048-bit key; unprotected) header.d=gmail.com header.i=@gmail.com header.b="D/E5P2nu"; dkim-atps=neutral Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by ozlabs.org (Postfix) with ESMTP id 42FslC5PcPz9sBs for ; Thu, 20 Sep 2018 07:03:03 +1000 (AEST) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728181AbeITCmo (ORCPT ); Wed, 19 Sep 2018 22:42:44 -0400 Received: from mail-lj1-f194.google.com ([209.85.208.194]:35126 "EHLO mail-lj1-f194.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728124AbeITCmo (ORCPT ); Wed, 19 Sep 2018 22:42:44 -0400 Received: by mail-lj1-f194.google.com with SMTP id p10-v6so6376970ljg.2; Wed, 19 Sep 2018 14:03:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:cc:subject:date:message-id:mime-version :content-transfer-encoding; bh=SjLfIVY+ZSAHdXuluR8I+iIHKz6Dk5sattt8USRnDkw=; b=D/E5P2nuP5J7hnYo6Ou6oz+p1OEJB885Bn06MLO8fdAX3i3AxYGFG79XbdArPNec8u wXg1D+BE1Qvh9nPEUK49EgCH9Eb0rd8INyTI/2nLtuLXW1nu//3x/OQOmEME0PVpsH6W ABNm8pKmNQf3mGFH4wT1dM/038SYvZdGjv2hMT58Or/3tBS1wQgq9wulNCBgsveh81RH Ryc2hitbMey/L1J/aMUW7tBnNFwvPoOdH/UhCUc+z/RuQb4AtHoohUv0fzF3AyN7UycN kPwp5Tk4C+ZCCVbp3pv7fHV4lOdHoZnewR5c1hPYRc935CcfsSTYEX38AlZIcz7dtmuT TNxg== 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:mime-version :content-transfer-encoding; bh=SjLfIVY+ZSAHdXuluR8I+iIHKz6Dk5sattt8USRnDkw=; b=Fw7k61WsL841gVKyYxacQpslghH0zrqdjvPPjRJlb9Sq4KVDIGfZvj5CQOtPnq3ByH hQPU2WeaJxvQhARbymQJmAqqDYmgew7OhgI78NTEUsCvWOFY943iooDV4RHAXkWU7nXc bIOwWIRsXZVpV43UnVNAFSCRXrhh7Qu0Ion3JfP0nrWCh/9Tz4O6C9CcdWi9SZuoJCTH 0XGMAMBBwYQ7N/iWcme+01Tx6oD3uaJN9Q4BkapEVjYfMN5Hd1yqZBjGqsQ2jmhnLJvI LPVj/ubC/aro6sSbCi8Qx6PWpcuEjXXL7f8DelJUaKafiMPet1O+z0X1uYyEm/7+Unlr I9mA== X-Gm-Message-State: APzg51Dv6L51sQ5hxU+vZ8yFAIRkdi7MW5QOZi6i7HWKYEpRjjLiztHX KhSD8imCDiBCqQDYlC2E2mlnkrUB X-Google-Smtp-Source: ANB0Vdbjzi7/8FcUGxsJWqezWqmrSWLCyhYDLGv6fhKHMT2eloAPptAA7WilHVP4yw0QGKKsiI5KCA== X-Received: by 2002:a2e:9ec9:: with SMTP id h9-v6mr17069561ljk.133.1537390979771; Wed, 19 Sep 2018 14:02:59 -0700 (PDT) Received: from linux-veee.lan (ip-194-187-74-233.konfederacka.maverick.com.pl. [194.187.74.233]) by smtp.gmail.com with ESMTPSA id a27-v6sm1263743lfi.59.2018.09.19.14.02.58 (version=TLS1_2 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Wed, 19 Sep 2018 14:02:58 -0700 (PDT) From: =?utf-8?b?UmFmYcWCIE1pxYJlY2tp?= To: Linus Walleij , linux-gpio@vger.kernel.org, Rob Herring , devicetree@vger.kernel.org Cc: Mark Rutland , Ray Jui , Scott Branden , Jon Mason , bcm-kernel-feedback-list@broadcom.com, linux-arm-kernel@lists.infradead.org, =?utf-8?b?UmFmYcWCIE1pxYJlY2tp?= Subject: [PATCH 1/2] dt-bindings: pinctrl: document Broadcom Northstar pin mux controller Date: Wed, 19 Sep 2018 23:02:18 +0200 Message-Id: <20180919210219.21921-1-zajec5@gmail.com> X-Mailer: git-send-email 2.13.7 MIME-Version: 1.0 Sender: linux-gpio-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-gpio@vger.kernel.org From: Rafał Miłecki Northstar has mux controller just like Northstar Plus and Northstar2. It's a bit different though (different registers & pins) so it requires its own binding. It's needed to allow other block bindings specify required mux setup. Signed-off-by: Rafał Miłecki Reviewed-by: Florian Fainelli --- .../devicetree/bindings/pinctrl/brcm,ns-pinmux.txt | 29 ++++++++++++++++++++++ 1 file changed, 29 insertions(+) create mode 100644 Documentation/devicetree/bindings/pinctrl/brcm,ns-pinmux.txt diff --git a/Documentation/devicetree/bindings/pinctrl/brcm,ns-pinmux.txt b/Documentation/devicetree/bindings/pinctrl/brcm,ns-pinmux.txt new file mode 100644 index 000000000000..0e913721ae9e --- /dev/null +++ b/Documentation/devicetree/bindings/pinctrl/brcm,ns-pinmux.txt @@ -0,0 +1,29 @@ +Broadcom Northstar pins mux controller + +Some of Northstar SoCs's pins can be used for various purposes thanks to the mux +controller. This binding allows describing mux controller and listing available +functions. They can be referenced later by other bindings to let system +configure controller correctly. + +Required properties: +- compatible: brcm,ns-pinmux +- reg: iomem address range of CRU (Central Resource Unit) pin registers +- reg-names: "cru_pins_control" - the only needed & supported reg right now + +List of supported functions and their groups: +- "spi": "spi_grp" + +For documentation of subnodes see: +Documentation/devicetree/bindings/pinctrl/pinctrl-bindings.txt + +Example: + pinctrl@1800c1c0 { + compatible = "brcm,ns-pinmux"; + reg = <0x1800c1c0 0x24>; + reg-names = "cru_pins_control"; + + spi { + function = "spi"; + groups = "spi_grp"; + }; + };