linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bjorn Andersson <bjorn.andersson@linaro.org>
To: Christian Lamparter <chunkeey@googlemail.com>
Cc: John Crispin <john@phrozen.org>,
	linux-gpio@vger.kernel.org,
	Ram Chandra Jangir <rjangir@codeaurora.org>,
	Linus Walleij <linus.walleij@linaro.org>,
	chrisrblake93@gmail.com
Subject: Re: [PATCH 2/2] pinctrl: qcom: ipq4019: add remaining pin definitions
Date: Wed, 17 May 2017 12:24:20 -0700	[thread overview]
Message-ID: <20170517192420.GE12920@tuxbook> (raw)
In-Reply-To: <2990002.PvbIJhg18q@debian64>

On Wed 17 May 08:44 PDT 2017, Christian Lamparter wrote:

> On Wednesday, May 10, 2017 3:23:28 PM CEST Bjorn Andersson wrote:
> > On Wed 10 May 04:27 PDT 2017, Christian Lamparter wrote:
> > 
> > > From: Ram Chandra Jangir <rjangir@codeaurora.org>
> > > 
> > > Populate default values for various GPIO functions.
> > > 
> > > Cc: Bjorn Andersson <bjorn.andersson@linaro.org>
> > > Cc: John Crispin <john@phrozen.org>
> > > Signed-off-by: Ram Chandra Jangir <rjangir@codeaurora.org>
> > 
> > Thanks Christian for attempting to forward this, when doing so you
> > should add your sob here.
> Ok, will do that.
> 
> > I do however have some comments and requests for changes. @Ram would you
> > be interested in this feedback and be willing to work on getting these
> > additions upstream? Or do you have the ability to do this Christian?
> I think this was enough time for Ram to comment.
> 
> @Bjorn, can you tell me what you want to see changed? 

I just wanted to make sure that someone was willing to follow up on my
code review before spending the time looking through it.

> I didn't see any commments in the reply. As for my ability: I can do
> development on my two customer routers: IPQ4018 (AVM FB4040) and IPQ4019
> (Asus RT-AC58U). Furthermore, I can ask Chris Blake, he owns a IPQ4029
> (Meraki MR33).
>  
> This should cover Ethernet (RMGII, PSGMII, MDIO and MDC), NAND,
> PCIe, SPI0, UART0/1, I2C0/1. If John is willing to join, he could
> verify emmc/sdio.
> 

I'm happy with this, will take a look at your patch!

> Thanks,
> Christian
> 
> PS.: Last week, Ram has posted a update to pinctrl:
> <http://www.mail-archive.com/lede-dev@lists.infradead.org/msg07387.html>
> |From e77af7de404eb464f7da9e0daeb8b362cc66a7ba Mon Sep 17 00:00:00 2001
> |From: Ram Chandra Jangir <rjan...@codeaurora.org>
> |Date: Tue, 9 May 2017 11:45:00 +0530
> |Subject: [PATCH] msm: pinctrl: Add support to configure ipq40xx GPIO_PULL bits
> |
> |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
> |[...]
> I'll add this to the series as well.
> 

I will give this some more thought, but initially I think the proposed
solution is too verbose for my taste- so far this is the only platform
I've seen having this.

I think I would prefer if we extend the msm_pinctrl_soc_data with a
single

  bool pull_no_keeper;

and then check if this is set in the four places that matters
pinctrl-msm.

Regards,
Bjorn

  reply	other threads:[~2017-05-17 19:24 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-10 11:27 [PATCH 1/2] dt-bindings: pinctrl: add most other IPQ4019 pin functions and groups Christian Lamparter
     [not found] ` <d53b7a9b1bab818536680123136ac58481d959c8.1494415174.git.chunkeey-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org>
2017-05-10 11:27   ` [PATCH 1/2] pinctrl: qcom: ipq4019: " Christian Lamparter
     [not found]     ` <20170510112712.14744-1-chunkeey-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org>
2017-05-13  0:10       ` Rob Herring
2017-05-13 16:03         ` Christian Lamparter
2017-05-16  0:13           ` Rob Herring
2017-05-10 11:27   ` [PATCH 2/2] pinctrl: qcom: ipq4019: add remaining pin definitions Christian Lamparter
     [not found]     ` <3dac044cd9a879cad145f9a04dcc3d225721aa3c.1494415174.git.chunkeey-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org>
2017-05-10 22:23       ` Bjorn Andersson
2017-05-17 15:44         ` Christian Lamparter
2017-05-17 19:24           ` Bjorn Andersson [this message]
2017-05-17 20:07     ` Bjorn Andersson
2017-05-18 18:38       ` Christian Lamparter
2017-05-20  5:08         ` Bjorn Andersson
2017-05-23 16:58           ` Christian Lamparter
2017-05-23 19:28             ` Bjorn Andersson
2017-05-24 13:04               ` Ram Chandra Jangir
2017-07-06  6:02                 ` Bjorn Andersson
2017-07-14 13:18                   ` Christian Lamparter
2017-05-13  0:07 ` [PATCH 1/2] dt-bindings: pinctrl: add most other IPQ4019 pin functions and groups Rob Herring

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170517192420.GE12920@tuxbook \
    --to=bjorn.andersson@linaro.org \
    --cc=chrisrblake93@gmail.com \
    --cc=chunkeey@googlemail.com \
    --cc=john@phrozen.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=rjangir@codeaurora.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).