diff for duplicates of <1477400900.2482.51.camel@baylibre.com> diff --git a/a/1.txt b/N1/1.txt index 64f9d5d..e639d4e 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -39,7 +39,7 @@ Linus, Marc, The calculation is question here is meant to get the appropriate hwirq number from a particular gpio (and deal with the gpios that can't -provide an irq at all).? +provide an irq at all). If I look at other gpio drivers, many are doing exactly this kind of calculation before calling 'irq_create_mapping' in the to_irq callback. @@ -50,7 +50,7 @@ For example: Some can afford to create all the mappings in the probe and just call 'irq_find_mapping' (gpio/gpio_tegra.c) but this would not work here. We have only 8 upstream irqs for 130+ pins, so only 8 mappings possible at -a time.? +a time. My understanding is that irqdomain provide a way to map hwirq to linux virq (and back), not map gpio number to hwirq, right? @@ -69,7 +69,7 @@ still have to perform this kind of calculation, one way or the other. Actually this discussion go me thinking about another issue we have with this hardware. We are looking for a way to implement support for IRQ_TYPE_EDGE_BOTH -(needed for things like gpio-keys or mmc card detect).? +(needed for things like gpio-keys or mmc card detect). The controller can do each edge but not both at the same time. I'm thinking that implementing another irqdomain at the gpio level would allow to properly check the pad level in the EOI callback then diff --git a/a/content_digest b/N1/content_digest index 84f476b..47baee8 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -4,10 +4,24 @@ "ref\01477040798.15560.96.camel@baylibre.com\0" "ref\0CACRpkdYUVXny57AC9rKX3VRAyooEk_2XLvqe9jOuT3rOaE75rg@mail.gmail.com\0" "ref\0ec7c6cc5-cf9a-9c75-4b07-e337064c7d6e@arm.com\0" - "From\0jbrunet@baylibre.com (Jerome Brunet)\0" - "Subject\0[PATCH 4/9] pinctrl: meson: allow gpio to request irq\0" + "From\0Jerome Brunet <jbrunet@baylibre.com>\0" + "Subject\0Re: [PATCH 4/9] pinctrl: meson: allow gpio to request irq\0" "Date\0Tue, 25 Oct 2016 15:08:20 +0200\0" - "To\0linus-amlogic@lists.infradead.org\0" + "To\0Marc Zyngier <marc.zyngier@arm.com>" + " Linus Walleij <linus.walleij@linaro.org>\0" + "Cc\0Carlo Caione <carlo@caione.org>" + Kevin Hilman <khilman@baylibre.com> + open list:ARM/Amlogic Meson... <linux-amlogic@lists.infradead.org> + linux-arm-kernel@lists.infradead.org <linux-arm-kernel@lists.infradead.org> + linux-gpio@vger.kernel.org <linux-gpio@vger.kernel.org> + linux-kernel@vger.kernel.org <linux-kernel@vger.kernel.org> + devicetree@vger.kernel.org <devicetree@vger.kernel.org> + Thomas Gleixner <tglx@linutronix.de> + Jason Cooper <jason@lakedaemon.net> + Rob Herring <robh+dt@kernel.org> + Catalin Marinas <catalin.marinas@arm.com> + Will Deacon <will.deacon@arm.com> + " Russell King <linux@armlinux.org.uk>\0" "\00:1\0" "b\0" "On Tue, 2016-10-25 at 11:38 +0100, Marc Zyngier wrote:\n" @@ -51,7 +65,7 @@ "\n" "The calculation is question here is meant to get the appropriate hwirq\n" "number from a particular gpio (and deal with the gpios that can't\n" - "provide an irq at all).?\n" + "provide an irq at all).\302\240\n" "\n" "If I look at other gpio drivers, many are doing exactly this kind of\n" "calculation before calling 'irq_create_mapping' in the to_irq callback.\n" @@ -62,7 +76,7 @@ "Some can afford to create all the mappings in the probe and just call\n" "'irq_find_mapping' (gpio/gpio_tegra.c) but this would not work here. We\n" "have only 8 upstream irqs for 130+ pins, so only 8 mappings possible at\n" - "a time.?\n" + "a time.\302\240\n" "\n" "My understanding is that irqdomain provide a way to map hwirq to linux\n" "virq (and back), not map gpio number to hwirq, right?\n" @@ -81,7 +95,7 @@ "Actually this discussion go me thinking about another issue we have\n" "with this hardware.\n" "We are looking for a way to implement support for IRQ_TYPE_EDGE_BOTH\n" - "(needed for things like gpio-keys or mmc card detect).?\n" + "(needed for things like gpio-keys or mmc card detect).\302\240\n" "The controller can do each edge but not both at the same time.\n" "I'm thinking that implementing another irqdomain at the gpio level\n" "would allow to properly check the pad level in the EOI callback then\n" @@ -104,4 +118,4 @@ "\n" Jerome -3317382dd85991f2514cd61b66581076373808887aee72828a579d15fce3bab1 +3418e2dc7e96d5833988e2d012af1216d5c679dce63fbc0032e00587dbc7d2bd
diff --git a/a/content_digest b/N2/content_digest index 84f476b..5e9ae42 100644 --- a/a/content_digest +++ b/N2/content_digest @@ -7,7 +7,7 @@ "From\0jbrunet@baylibre.com (Jerome Brunet)\0" "Subject\0[PATCH 4/9] pinctrl: meson: allow gpio to request irq\0" "Date\0Tue, 25 Oct 2016 15:08:20 +0200\0" - "To\0linus-amlogic@lists.infradead.org\0" + "To\0linux-arm-kernel@lists.infradead.org\0" "\00:1\0" "b\0" "On Tue, 2016-10-25 at 11:38 +0100, Marc Zyngier wrote:\n" @@ -104,4 +104,4 @@ "\n" Jerome -3317382dd85991f2514cd61b66581076373808887aee72828a579d15fce3bab1 +d8828cfcd5b733b2abf2b5ea1dea702cdcd41f43b3083ecf07ecfa18ffe643f1
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.