{"id":818906,"url":"http://patchwork.ozlabs.org/api/covers/818906/?format=json","web_url":"http://patchwork.ozlabs.org/project/linux-gpio/cover/1506480343-9597-1-git-send-email-yamada.masahiro@socionext.com/","project":{"id":42,"url":"http://patchwork.ozlabs.org/api/projects/42/?format=json","name":"Linux GPIO development","link_name":"linux-gpio","list_id":"linux-gpio.vger.kernel.org","list_email":"linux-gpio@vger.kernel.org","web_url":"","scm_url":"","webscm_url":"","list_archive_url":"","list_archive_url_format":"","commit_url_format":""},"msgid":"<1506480343-9597-1-git-send-email-yamada.masahiro@socionext.com>","list_archive_url":null,"date":"2017-09-27T02:45:41","name":"[v7,0/2] gpio: uniphier: UniPhier GPIO driver","submitter":{"id":65882,"url":"http://patchwork.ozlabs.org/api/people/65882/?format=json","name":"Masahiro Yamada","email":"yamada.masahiro@socionext.com"},"mbox":"http://patchwork.ozlabs.org/project/linux-gpio/cover/1506480343-9597-1-git-send-email-yamada.masahiro@socionext.com/mbox/","series":[{"id":5272,"url":"http://patchwork.ozlabs.org/api/series/5272/?format=json","web_url":"http://patchwork.ozlabs.org/project/linux-gpio/list/?series=5272","date":"2017-09-27T02:45:42","name":"gpio: uniphier: UniPhier GPIO driver","version":7,"mbox":"http://patchwork.ozlabs.org/series/5272/mbox/"}],"comments":"http://patchwork.ozlabs.org/api/covers/818906/comments/","headers":{"Return-Path":"<linux-gpio-owner@vger.kernel.org>","X-Original-To":"incoming@patchwork.ozlabs.org","Delivered-To":"patchwork-incoming@bilbo.ozlabs.org","Authentication-Results":["ozlabs.org;\n\tspf=none (mailfrom) smtp.mailfrom=vger.kernel.org\n\t(client-ip=209.132.180.67; helo=vger.kernel.org;\n\tenvelope-from=linux-gpio-owner@vger.kernel.org;\n\treceiver=<UNKNOWN>)","ozlabs.org;\n\tdkim=fail reason=\"signature verification failed\" (2048-bit key;\n\tunprotected) header.d=nifty.com header.i=@nifty.com\n\theader.b=\"nkxImDzr\"; dkim-atps=neutral"],"Received":["from vger.kernel.org (vger.kernel.org [209.132.180.67])\n\tby ozlabs.org (Postfix) with ESMTP id 3y22L96Bxyz9sPr\n\tfor <incoming@patchwork.ozlabs.org>;\n\tWed, 27 Sep 2017 12:47:45 +1000 (AEST)","(majordomo@vger.kernel.org) by vger.kernel.org via listexpand\n\tid S967333AbdI0Cro (ORCPT <rfc822;incoming@patchwork.ozlabs.org>);\n\tTue, 26 Sep 2017 22:47:44 -0400","from conuserg-07.nifty.com ([210.131.2.74]:58217 \"EHLO\n\tconuserg-07.nifty.com\" rhost-flags-OK-OK-OK-OK) by vger.kernel.org\n\twith ESMTP id S935664AbdI0Crm (ORCPT\n\t<rfc822; linux-gpio@vger.kernel.org>); Tue, 26 Sep 2017 22:47:42 -0400","from pug.e01.socionext.com (p14092-ipngnfx01kyoto.kyoto.ocn.ne.jp\n\t[153.142.97.92]) (authenticated)\n\tby conuserg-07.nifty.com with ESMTP id v8R2jiYM009483;\n\tWed, 27 Sep 2017 11:45:44 +0900"],"DKIM-Filter":"OpenDKIM Filter v2.10.3 conuserg-07.nifty.com v8R2jiYM009483","DKIM-Signature":"v=1; a=rsa-sha256; c=relaxed/relaxed; d=nifty.com;\n\ts=dec2015msa; t=1506480345;\n\tbh=9f5KEOhk8tR5mDxywlVv5uyQMyzdIUM31kLDnTFSZuI=;\n\th=From:To:Cc:Subject:Date:From;\n\tb=nkxImDzrB/qedxVjx4Fhl6IyJDz6u8rrPwAXdCuKESh3y6xoVg91wF/orZPvHkq7W\n\tKiQtL2pKVDHeXRTMXeEJcGM6vTgenl+ARTevYJWywAyCHk0vWRIIdBbCrmh9LOUr+V\n\tnlB96n0q1XedNrGMlBe163LVThHPpwvSfQtUZ5t79JgAV/bKpYvAydIjVqM5QB2GSH\n\tLrMHyqEXq25O0RhHmRc55r3undWTFfG91hLtutq3YvlO576QmmmWLiXARoJmv1gZnX\n\tYKfrGmJUvJooYBHFuESwGVK0AD0z8MnCUl36utgdnmNEDg50FbxtCTUxG/ui874TQ0\n\tKzW/D6AfyZkHQ==","X-Nifty-SrcIP":"[153.142.97.92]","From":"Masahiro Yamada <yamada.masahiro@socionext.com>","To":"linux-gpio@vger.kernel.org","Cc":"devicetree@vger.kernel.org, Rob Herring <robh@kernel.org>,\n\tMasami Hiramatsu <mhiramat@kernel.org>,\n\tJassi Brar <jaswinder.singh@linaro.org>,\n\tMasahiro Yamada <yamada.masahiro@socionext.com>,\n\tMauro Carvalho Chehab <mchehab@kernel.org>,\n\tRandy Dunlap <rdunlap@infradead.org>,\n\tLinus Walleij <linus.walleij@linaro.org>, linux-kernel@vger.kernel.org,\n\t\"David S. Miller\" <davem@davemloft.net>,\n\tRob Herring <robh+dt@kernel.org>,\n\tGreg Kroah-Hartman <gregkh@linuxfoundation.org>,\n\tMark Rutland <mark.rutland@arm.com>, linux-arm-kernel@lists.infradead.org","Subject":"[PATCH v7 0/2] gpio: uniphier: UniPhier GPIO driver","Date":"Wed, 27 Sep 2017 11:45:41 +0900","Message-Id":"<1506480343-9597-1-git-send-email-yamada.masahiro@socionext.com>","X-Mailer":"git-send-email 2.7.4","Sender":"linux-gpio-owner@vger.kernel.org","Precedence":"bulk","List-ID":"<linux-gpio.vger.kernel.org>","X-Mailing-List":"linux-gpio@vger.kernel.org"},"content":"This series adds UniPhier GPIO driver.\n\nThe interrupt controller part is implemented by using hierarchy irqdomain.\n\nIMHO, the problem of the hierarchy irqdomain is that drivers must hard-code\nthe fwspec of the interrupt parent.  We will never know the DT binding of\nthe parent unless we parse #interrupt-cell, etc.\n\nI asked about this:\nhttps://lkml.org/lkml/2017/7/6/758\n\nApparently, the current kernel does not provide a systematic way to\ndescribe it.\n\nIn v1-v3, I hard-coded the parent hwirq numbers in the driver because\nirqchip drivers are forced to hard-code more or less about the parent.\nThis was not accepted by Linus Walleij.\n\nIn v4, I tried to use the new API irq_domain_push_irq().  I needed to\nchange the irqdomain framework to make it work for DT, but seemed\ncontroversial in the irqdomain subsystem review.\n\nIn v5, I tried another solution.  At first I thought it worked, but\nI found a dead-lock if an irq is disposed from the .alloc hook.\n\nAfter I considered more, I thought \"interrupts\" property does not\nmake much sense here because the last cell (which usually specifies\nthe trigger type) is useless for the hierarchy irqdomain.\n\nI decided to use a vendor-specific property.  This is what some drivers\nactually do.\n\n\nChanges in v7:\n  - Rename uniphier_gpio_irq_get_hwirq()\n    (I just missed to \"git commit\" before \"git send-email\")\n\nChanges in v6:\n  - Add \"socionext,interrupt-ranges\"\n\nChanges in v5:\n  - Split into a separate patch for DT binding\n  - Add a new patch to export of_phandle_args_to_fwspec\n  - Split DT binding into a separate file\n  - v4 depends on some patches that change irq_domain_push_irq(), but\n    they got negative feedback in the irqdomain subsystem review.\n    Yet another approach here.  Parse \"interrupts\" property in\n    .alloc() hook.  If the parent IRQ is already mapped, dispose it\n    and re-alloc in irqdomain manner.\n\nChanges in v4:\n  - Add COMPILE_TEST and select IRQ_DOMAIN_HIERARCHY\n  - Reimplement irqchip part by using irq_domain_push_irq()\n\nChanges in v3:\n  - Add .irq_set_affinity() hook\n  - Use irq_domain_create_hierarchy() instead of legacy\n    irq_domain_add_hierarchy()\n\nChanges in v2:\n  - Remove +32 offset for parent interrupts to follow the GIC\n    binding convention\n  - Let uniphier_gpio_irq_alloc() fail if nr_irqs != 1\n  - Allocate gpio_chip statically because just one instance is\n    supported\n  - Fix suspend and resume hooks\n\nMasahiro Yamada (2):\n  dt-bindings: gpio: uniphier: add UniPhier GPIO binding\n  gpio: uniphier: add UniPhier GPIO controller driver\n\n .../devicetree/bindings/gpio/gpio-uniphier.txt     |  40 ++\n MAINTAINERS                                        |   1 +\n drivers/gpio/Kconfig                               |   8 +\n drivers/gpio/Makefile                              |   1 +\n drivers/gpio/gpio-uniphier.c                       | 507 +++++++++++++++++++++\n include/dt-bindings/gpio/uniphier-gpio.h           |  18 +\n 6 files changed, 575 insertions(+)\n create mode 100644 Documentation/devicetree/bindings/gpio/gpio-uniphier.txt\n create mode 100644 drivers/gpio/gpio-uniphier.c\n create mode 100644 include/dt-bindings/gpio/uniphier-gpio.h"}