diff for duplicates of <1477409478.2482.113.camel@baylibre.com> diff --git a/a/1.txt b/N1/1.txt index 07b11d6..5a7be50 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -1,5 +1,5 @@ On Tue, 2016-10-25 at 15:47 +0100, Marc Zyngier wrote: ->? +> > > > But why are those number different? Why don't you use the same > > > namespace? If gpio == hwirq, all your problems are already > > > solved. If @@ -13,7 +13,7 @@ On Tue, 2016-10-25 at 15:47 +0100, Marc Zyngier wrote: > > 1. We have 2 instances of pinctrl, to guarantee that the linux gpio > > number == hwirq, we would have to guarantee the order in which they > > are -> > probed. At least this my understanding? +> > probed. At least this my understanding > > Maybe I wasn't clear enough, and my use of gpio is probably wrong. So > Linux has a gpio number, which is obviously an abstract number (just @@ -80,7 +80,7 @@ numbers, 0 if there is no interrupt. So could either find or create the mapping. A. With the hardware at hand, and the limited upstream interrupt - number, i don't see how we could create the mapping beforehand.? + number, i don't see how we could create the mapping beforehand. > > > @@ -113,7 +113,7 @@ So could either find or create the mapping. > > > > 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 @@ -131,12 +131,12 @@ So could either find or create the mapping. > > > same. > > > I fail to see what the benefit is. > > -> > The separate piece of hw is the gpio itself.? +> > The separate piece of hw is the gpio itself. > > The irq-controller (in irqchip) can't read the gpio state because > > it is > > simply another device. > > -> > The domain I'm thinking about wouldn't do much, I reckon.? +> > The domain I'm thinking about wouldn't do much, I reckon. > > It would just register an irqchip which would only implement eoi. > > For everything else, it would rely the parent controller. > > From your explanation, I understood this is the purpose of diff --git a/a/content_digest b/N1/content_digest index 581321c..42cc33d 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -8,14 +8,28 @@ "ref\0dee26f0b-e175-f8a0-2b73-08e8e324841c@arm.com\0" "ref\01477405332.2482.87.camel@baylibre.com\0" "ref\0bbc268c8-35c3-206a-46b1-62cebef174b2@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 17:31:18 +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 15:47 +0100, Marc Zyngier wrote:\n" - ">?\n" + ">\302\240\n" "> > > But why are those number different? Why don't you use the same\n" "> > > namespace? If gpio == hwirq, all your problems are already\n" "> > > solved. If\n" @@ -29,7 +43,7 @@ "> > 1. We have 2 instances of pinctrl, to guarantee that the linux gpio\n" "> > number == hwirq, we would have to guarantee the order in which they\n" "> > are\n" - "> > probed. At least this my understanding?\n" + "> > probed. At least this my understanding\302\240\n" "> \n" "> Maybe I wasn't clear enough, and my use of gpio is probably wrong. So\n" "> Linux has a gpio number, which is obviously an abstract number (just\n" @@ -96,7 +110,7 @@ "\n" "So could either find or create the mapping.\n" " A. With the hardware at hand, and the limited upstream interrupt\n" - " number, i don't see how we could create the mapping beforehand.?\n" + " number, i don't see how we could create the mapping beforehand.\302\240\n" "\n" "> \n" "> > \n" @@ -129,7 +143,7 @@ "> > > > with this hardware.\n" "> > > > We are looking for a way to implement support for\n" "> > > > 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\n" "> > > > level\n" @@ -147,12 +161,12 @@ "> > > same.\n" "> > > I fail to see what the benefit is.\n" "> > \n" - "> > The separate piece of hw is the gpio itself.?\n" + "> > The separate piece of hw is the gpio itself.\302\240\n" "> > The irq-controller (in irqchip) can't read the gpio state because\n" "> > it is\n" "> > simply another device.\n" "> > \n" - "> > The domain I'm thinking about wouldn't do much, I reckon.?\n" + "> > The domain I'm thinking about wouldn't do much, I reckon.\302\240\n" "> > It would just register an irqchip which would only implement eoi.\n" "> > For everything else, it would rely the parent controller.\n" "> > From your explanation, I understood this is the purpose of\n" @@ -216,4 +230,4 @@ "> \n" "> \tM." -d9077c4de97c5a3b7cb4255dcbea26415d364e1037f55460a31f714124d004b8 +3f1ed6e10f1c4f9e4269f6145184d02787c2413539932d063d6ac455eea6dbcf
diff --git a/a/content_digest b/N2/content_digest index 581321c..5c4c9b9 100644 --- a/a/content_digest +++ b/N2/content_digest @@ -11,7 +11,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 17:31:18 +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 15:47 +0100, Marc Zyngier wrote:\n" @@ -216,4 +216,4 @@ "> \n" "> \tM." -d9077c4de97c5a3b7cb4255dcbea26415d364e1037f55460a31f714124d004b8 +49c405e851cb482c5322305c0c54362192bafb9cbc0c32946a168a6f382e9c9e
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.