Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751220AbdFCSzb (ORCPT ); Sat, 3 Jun 2017 14:55:31 -0400 Received: from mail-wm0-f65.google.com ([74.125.82.65]:36265 "EHLO mail-wm0-f65.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750991AbdFCSz2 (ORCPT ); Sat, 3 Jun 2017 14:55:28 -0400 From: Christian Lamparter To: Varadarajan Narayanan Cc: robh+dt@kernel.org, mark.rutland@arm.com, mturquette@baylibre.com, sboyd@codeaurora.org, linus.walleij@linaro.org, andy.gross@linaro.org, david.brown@linaro.org, catalin.marinas@arm.com, will.deacon@arm.com, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-clk@vger.kernel.org, linux-gpio@vger.kernel.org, linux-arm-msm@vger.kernel.org, linux-soc@vger.kernel.org, linux-arm-kernel@lists.infradead.org, bjorn.andersson@linaro.org, absahu@codeaurora.org, sjaganat@codeaurora.org, sricharan@codeaurora.org, mraghava@codeaurora.org, Ram Chandra Jangir Subject: Re: [PATCH v4 1/6] pinctrl: qcom: Add ipq8074 pinctrl driver Date: Sat, 03 Jun 2017 20:55:23 +0200 Message-ID: <2668868.v3IoKk0Lz9@debian64> User-Agent: KMail/5.2.3 (Linux/4.12.0-rc2-wt+; KDE/5.28.0; x86_64; ; ) In-Reply-To: <1496474875-7190-2-git-send-email-varada@codeaurora.org> References: <1496474875-7190-1-git-send-email-varada@codeaurora.org> <1496474875-7190-2-git-send-email-varada@codeaurora.org> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2849 Lines: 91 On Saturday, June 3, 2017 12:57:50 PM CEST Varadarajan Narayanan wrote: > Add initial pinctrl driver to support pin configuration with > pinctrl framework for ipq8074. > > Signed-off-by: Manoharan Vijaya Raghavan > Signed-off-by: Varadarajan Narayanan > --- > +- bias-disable: > + Usage: optional > + Value type: > + Definition: The specified pins should be configued as no pull. > + > +- bias-pull-down: > + Usage: optional > + Value type: > + Definition: The specified pins should be configued as pull down. > + > +- bias-pull-up: > + Usage: optional > + Value type: > + Definition: The specified pins should be configued as pull up. > + > +#define REG_SIZE 0x1000 > +#define PINGROUP(id, f1, f2, f3, f4, f5, f6, f7, f8, f9) \ > + { \ > + .name = "gpio" #id, \ > + .pins = gpio##id##_pins, \ > + .npins = (unsigned int)ARRAY_SIZE(gpio##id##_pins), \ > + .funcs = (int[]){ \ > + msm_mux_gpio, /* gpio mode */ \ > + msm_mux_##f1, \ > + msm_mux_##f2, \ > + msm_mux_##f3, \ > + msm_mux_##f4, \ > + msm_mux_##f5, \ > + msm_mux_##f6, \ > + msm_mux_##f7, \ > + msm_mux_##f8, \ > + msm_mux_##f9 \ > + }, \ > + .nfuncs = 10, \ > + .ctl_reg = REG_SIZE * id, \ > + .io_reg = 0x4 + REG_SIZE * id, \ > + .intr_cfg_reg = 0x8 + REG_SIZE * id, \ > + .intr_status_reg = 0xc + REG_SIZE * id, \ > + .intr_target_reg = 0x8 + REG_SIZE * id, \ > + .mux_bit = 2, \ > + .pull_bit = 0, \ > + .drv_bit = 6, \ > + .oe_bit = 9, \ > + .in_bit = 0, \ > + .out_bit = 1, \ > + .intr_enable_bit = 0, \ > + .intr_status_bit = 0, \ > + .intr_target_bit = 5, \ > + .intr_raw_status_bit = 4, \ > + .intr_polarity_bit = 1, \ > + .intr_detection_bit = 2, \ > + .intr_detection_width = 2, \ > + } > + Hello, Back in May, Ram Chandra Jangir posted a rather interesting patch on the LEDE Mailing-List: |GPIO_PULL bits configurations in TLMM_GPIO_CFG register |differs for IPQ40xx from rest of the other qcom SoC's. |This change add support to configure the msm_gpio_pull |bits for ipq40xx, It is required to fix the proper |configurations of gpio-pull bits for nand pins mux. | |IPQ40xx SoC: |2'b10: Internal pull up enable. |2'b11: Unsupport | |For other SoC's: |2'b10: Keeper |2'b11: Pull-Up This information wasn't mentioned anywhere. In fact, the special pull-up configuration was only discovered due to an issue with the qpic NAND on the Cisco Meraki MR33. So I wonder what does the gpio-pull look like for the IPQ8074? Is it the same as the IPQ40XX or does it follow the older SoCs? I'm asking this because I'm preparing a modified version of this patch that will be posted once the IPQ8074 is ready. Regards, Christian