[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20200701013320.130441-1-drew@beagleboard.org>
Date: Wed, 1 Jul 2020 03:33:18 +0200
From: Drew Fustini <drew@...gleboard.org>
To: Tony Lindgren <tony@...mide.com>, Rob Herring <robh+dt@...nel.org>,
linux-omap@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-gpio@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
Linus Walleij <linus.walleij@...aro.org>,
Haojian Zhuang <haojian.zhuang@...aro.org>,
devicetree@...r.kernel.org, bcousson@...libre.com,
Jason Kridner <jkridner@...gleboard.org>,
Robert Nelson <robertcnelson@...il.com>
Cc: Drew Fustini <drew@...gleboard.org>
Subject: [PATCH v4 0/2] pinctrl: single: support #pinctrl-cells = 2
Currently, pinctrl-single only allows #pinctrl-cells = 1.
This series will allow pinctrl-single to also support #pinctrl-cells = 2
If "pinctrl-single,pins" has 3 arguments (offset, conf, mux) then
pcs_parse_one_pinctrl_entry() does an OR operation on conf and mux to
get the value to store in the register.
To take advantage of #pinctrl-cells = 2, the AM33XX_PADCONF macro in
omap.h is modified to keep pin conf and pin mux values separate.
change log:
- v4: squash patches 2 and 3 together so that git biesct will not result
in a boot failure
- v3: change order of patches to make sure the pinctrl-single.c patch
does not break anything without the dts patches
- v2: remove outer parentheses from AM33XX_PADCONF macro as it causes a
compile error in dtc. I had added it per suggestion from checkpatch
about having parentheses around complex values.
Drew Fustini (2):
pinctrl: single: parse #pinctrl-cells = 2
ARM: dts: am33xx-l4: change #pinctrl-cells from 1 to 2
arch/arm/boot/dts/am33xx-l4.dtsi | 2 +-
drivers/pinctrl/pinctrl-single.c | 11 +++++++++--
include/dt-bindings/pinctrl/omap.h | 2 +-
3 files changed, 11 insertions(+), 4 deletions(-)
--
2.25.1
Powered by blists - more mailing lists