Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1732923

Re: [PATCH 00/16] gpio: Tight IRQ chip integration and banked infrastructure

Path csiph.com!news.redatomik.org!aioe.org!bofh.it!news.nic.it!robomod
From Thierry Reding <thierry.reding@gmail.com>
Newsgroups linux.kernel
Subject Re: [PATCH 00/16] gpio: Tight IRQ chip integration and banked infrastructure
Date Fri, 15 Sep 2017 17:20:02 +0200
Message-ID <uq0zo-4II-3@gated-at.bofh.it> (permalink)
References <ukZkB-vv-13@gated-at.bofh.it> <upCQq-5Ks-11@gated-at.bofh.it>
X-Original-To Linus Walleij <linus.walleij@linaro.org>
Dkim-Signature v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=Kp9KU3FN3R87TWDx/FaX7zYWft7xi0Y0iq73CyzH0nw=; b=skdV/BftfR7Crah+93gbILNUlaywmgKWoi8BZtPG+8t2xVJY9Ljlga50x234E2Fqrq iiQlBgfkNS/m/zxan+yrVB6KP7byPULLKefAokLVAPc/2xOtWYMnR1FpcUpUF9h0wDfC nfkQZo5iDGEuqIWk5Ja56m3RZOL1sy2QIwZRnRbV1r/wUqGcJtUZB9gnfT/dQQsZO/mX 4vg/biTaAytpnrYmLdeOvq+OZQe5bNhZyejjyQyeGhRR79ogoYJFeAr6dynYCho5PzKR Vcrk4+2ZaepaNbBbP44RCwCpQql6PA9GhT3m5j/QN1hLRTU2ugBEv6faVCpc8yAw060q 7WJg==
X-Google-Dkim-Signature v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=Kp9KU3FN3R87TWDx/FaX7zYWft7xi0Y0iq73CyzH0nw=; b=ZOVJutEr45W/gpEq7DMRXv/4U0D0IKEAo+TZ4vOjIBmMaH5Qm6G9BYoqpMtJqPZUBA DhumAM/COkaqpGQiuIu/bFw8XZCFgNP/yDx2WIG4kGnugITBJsxnZ6sWRMHLVWl9V3wq OsjkgndOL2Ln9J+ipcMw4ejxc0N2pIhWJmXESEOXUnMYV16naMSNXh54EjA0MdIA8hmp IaZQoxpyLyTl4JTuIrxcZYhax64kotc3DTQdhhzZ4EKAgjoni7y51e4huioJx4WsH0F9 AKRFAYId0ENuebe4htq0GTdfFEpuiGTAjKeYmfbggvH+1e1zT6+ajvQFl07xYlop5lXh 1IaQ==
X-Gm-Message-State AHPjjUgPuVW7nLsxlR+pK1/3UFC5UFJ6VdaP2mot9XY/aL18O1Kt9NDE SAltoO9HNjkAgQ==
X-Google-SMTP-Source AOwi7QCbFWKCgKU8x+bkDCxZy0l5/yNDRohpLNzwCp+a/sZxsoeXA+HT4b3/JZKh8WhM5XU/70IYTA==
X-Received by 10.159.198.10 with SMTP id f10mr11874487plo.14.1505488203079; Fri, 15 Sep 2017 08:10:03 -0700 (PDT)
MIME-Version 1.0
Content-Type multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="4Ckj6UjgE2iN1+kY"
Content-Disposition inline
User-Agent Mutt/1.9.0 (2017-09-02)
Sender robomod@news.nic.it
List-ID <linux-kernel.vger.kernel.org>
X-Mailing-List linux-kernel@vger.kernel.org
Approved robomod@news.nic.it
Lines 112
Organization linux.* mail to news gateway
X-Original-Cc Jonathan Hunter <jonathanh@nvidia.com>, "linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>, "linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>, "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>, ext Tony Lindgren <tony@atomide.com>
X-Original-Date Fri, 15 Sep 2017 08:09:57 -0700
X-Original-Message-ID <20170914185233.GA6410@aiwendil>
X-Original-References <20170901185736.28051-1-thierry.reding@gmail.com> <CACRpkdaRsG-9YU2ufb+FxGOO38+x=AAfVUqxH5s56NH2iLw7oA@mail.gmail.com>
X-Original-Sender linux-kernel-owner@vger.kernel.org
Xref csiph.com linux.kernel:1732923

Show key headers only | View raw


[Multipart message — attachments visible in raw view] - view raw

On Thu, Sep 14, 2017 at 03:54:56PM +0200, Linus Walleij wrote:
> On Fri, Sep 1, 2017 at 8:57 PM, Thierry Reding <thierry.reding@gmail.com> wrote:
> 
> > here's the latest series of patches that implement the tighter IRQ chip
> > integration as well as the banked GPIO infrastructure that we had
> > discussed a couple of weeks/months back.
> 
> Yes it has become really tasty now, don't you think :)
> 
> I really like the series.
> 
> Banks are handled in the core, exactly as I wanted.
> 
> I will likely go in and change some things I don't like, like switching
> num_pins in the bank to num_lines. I have preferred that terminology
> to avoid confusion with pin control. So GPIO chips have lines, not pins.
> But it's so minor that I can fix it up if you don't want to.

I rebased this on today's linux-next and noticed that there was a small
conflict. I can rebase and work in the changes that you requested.

I'm travelling this week and next, so it may take until after -rc2 that
I can send out a new version that's properly build-tested.

> We also need to go in and patch Documentation/gpio/driver.txt
> to represent the current best practice. But that can be later,
> separate patch.
> 
> > The first couple of patches are mostly preparatory work in order to
> > consolidate all IRQ chip related fields in a new structure and create
> > the base functionality for adding IRQ chips.
> >
> > After that, I've added the Tegra186 GPIO support patch that makes use of
> > the new tight integration.
> >
> > To round things off the new banked GPIO infrastructure is added (along
> > with some more preparatory work), followed by the conversion of the two
> > Tegra GPIO drivers to the new infrastructure.
> 
> I have put all on a branch for pushing to the test builders to begin with.
> 
> Then I plan to make one branch with all infrastructure patches
> (patches 1-10, 12-14) and pull that into devel, then apply patch
> 11 and 15-16 directly on devel.
> 
> That way other subsystems (pinctrl ...) can pull in the infrastructure
> for people adding new gpiochips this cycle.

Sounds good.

> > Any thoughts on this? I'd like to target 4.15 with this,
> 
> Me, too.
> 
> > unless you'd be
> > willing to take this into 4.14, which I doubt at this point. The absence
> > of a GPIO driver has been hampering Tegra186 support upstream for a
> > while now, so it'd be good to make progress on this.
> 
> Sorry about that. Let's move ahead with this now, it is neat and
> clean.
> 
> What I want (as maintainer) is a bit of fingerpointing at the drivers
> that need to be converted to use the new banking infrastructure
> so they don't stay with their old crappy design pattern. OMAP is
> a clear candidate right? (Added Tony to CC...)

OMAP should be able to use this infrastructure, but it may not want to
because the semantics would change slightly. Currently OMAP registers a
GPIO chip for each bank, whereas this infrastructure exposes multiple
banks via a single chip.

There might be some userspace that relies on the existence of multiple
chips, but Tony can probably knows that better than I.

> Who else?

gpio-intel-mid.c and gpio-merrifield.c look like they could use this new
infrastructure. So do gpio-pca953x.c, gpio-stmpe.c and gpio-tc3589x.c.

gpio-ws16c48.c is another one that uses a similar pattern.

Thierry

Back to linux.kernel | Previous | NextPrevious in thread | Next in thread | Find similar | Unroll thread


Thread

Re: [PATCH 00/16] gpio: Tight IRQ chip integration and banked infrastructure Linus Walleij <linus.walleij@linaro.org> - 2017-09-14 16:00 +0200
  Re: [PATCH 00/16] gpio: Tight IRQ chip integration and banked  infrastructure Thierry Reding <thierry.reding@gmail.com> - 2017-09-15 17:20 +0200
    Re: [PATCH 00/16] gpio: Tight IRQ chip integration and banked  infrastructure Tony Lindgren <tony@atomide.com> - 2017-09-15 19:00 +0200
      Re: [PATCH 00/16] gpio: Tight IRQ chip integration and banked  infrastructure Grygorii Strashko <grygorii.strashko@ti.com> - 2017-09-16 00:30 +0200
      Re: [PATCH 00/16] gpio: Tight IRQ chip integration and banked infrastructure Linus Walleij <linus.walleij@linaro.org> - 2017-09-21 14:10 +0200

csiph-web