From: khilman@baylibre.com (Kevin Hilman)
To: linus-amlogic@lists.infradead.org
Subject: [PATCH v6 2/9] irqchip: add Amlogic Meson GPIO irqchip driver
Date: Fri, 09 Jun 2017 14:15:45 -0700 [thread overview]
Message-ID: <m2vao46ewu.fsf@baylibre.com> (raw)
In-Reply-To: <1496999266.3552.61.camel@baylibre.com> (Jerome Brunet's message of "Fri, 09 Jun 2017 11:07:46 +0200")
Jerome Brunet <jbrunet@baylibre.com> writes:
> On Thu, 2017-06-08 at 21:38 +0200, Heiner Kallweit wrote:
>> Add a driver supporting the GPIO interrupt controller on certain
>> Amlogic meson SoC's.
>>
>> Signed-off-by: Heiner Kallweit <hkallweit1@gmail.com>
[...]
>> +static unsigned int meson_irq_startup(struct irq_data *data)
>> +{
>> + irq_chip_unmask_parent(data);
>> + /*
>> + ?* An extra bit was added to allow having the same gpio hwirq twice
>> + ?* for handling IRQ_TYPE_EDGE_BOTH. Remove this bit to get the
>> + ?* gpio hwirq.
>> + ?*/
>> + meson_irq_set_hwirq(data, data->hwirq >> 1);
>
> Please keep in mind that any device can use this controller as irq parent.
> It has to make sense, even when not serving the gpio driver.
>
> This hack means that, in DT, we'd have to multiply by 2 the values given under
> section "22.3 GPIO interrupts" of the datasheet. This is an example Linux
> specific stuff in DT.
> It also means that the controller declares a lot more lines that it really has
> ...
>
> This is all to accommodate your hack around IRQ_TYPE_BOTH and creating the
> mapping from the irq_set_type callback of the GPIO driver, which is still think
> should be dropped at this point.
+1
Please drop the hack for IRQ_TYPE_BOTH so we can reach agreement on the
basic design and functionality. The gymnastics required to support this
hack (due to broken hardware) are getting in the way of getting basic
functionality merged.
Also, we already know from previous discussions between Jerome and the
IRQ maintainers that hacks for IRQ_TYPE_BOTH like this have been very
thoroughly rejected. So while the IRQ maintainers haven't chimed in on
this series, we have a very good idea what they will say when they do.
So please, pretty please, let's avoid giving the IRQ maintainers a fun
reason to NAK, and drop the IRQ_TYPE_BOTH stuff until we have an agreed
upon way to support the hardware that actually works.
Thanks,
Kevin
WARNING: multiple messages have this Message-ID (diff)
From: Kevin Hilman <khilman-rdvid1DuHRBWk0Htik3J/w@public.gmane.org>
To: Heiner Kallweit
<hkallweit1-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
Jerome Brunet <jbrunet-rdvid1DuHRBWk0Htik3J/w@public.gmane.org>
Cc: Mark Rutland <mark.rutland-5wv7dgnIgG8@public.gmane.org>,
Marc Zyngier <marc.zyngier-5wv7dgnIgG8@public.gmane.org>,
Linus Walleij
<linus.walleij-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>,
Thomas Gleixner <tglx-hfZtesqFncYOwBW4kG4KsQ@public.gmane.org>,
Rob Herring <robh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
Neil Armstrong
<narmstrong-rdvid1DuHRBWk0Htik3J/w@public.gmane.org>,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-amlogic-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
linux-gpio-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
"thierry.reding@gmail.com"
<thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
Thierry Reding <treding-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
Subject: Re: [PATCH v6 2/9] irqchip: add Amlogic Meson GPIO irqchip driver
Date: Fri, 09 Jun 2017 14:15:45 -0700 [thread overview]
Message-ID: <m2vao46ewu.fsf@baylibre.com> (raw)
In-Reply-To: <1496999266.3552.61.camel-rdvid1DuHRBWk0Htik3J/w@public.gmane.org> (Jerome Brunet's message of "Fri, 09 Jun 2017 11:07:46 +0200")
Jerome Brunet <jbrunet-rdvid1DuHRBWk0Htik3J/w@public.gmane.org> writes:
> On Thu, 2017-06-08 at 21:38 +0200, Heiner Kallweit wrote:
>> Add a driver supporting the GPIO interrupt controller on certain
>> Amlogic meson SoC's.
>>
>> Signed-off-by: Heiner Kallweit <hkallweit1-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
[...]
>> +static unsigned int meson_irq_startup(struct irq_data *data)
>> +{
>> + irq_chip_unmask_parent(data);
>> + /*
>> + * An extra bit was added to allow having the same gpio hwirq twice
>> + * for handling IRQ_TYPE_EDGE_BOTH. Remove this bit to get the
>> + * gpio hwirq.
>> + */
>> + meson_irq_set_hwirq(data, data->hwirq >> 1);
>
> Please keep in mind that any device can use this controller as irq parent.
> It has to make sense, even when not serving the gpio driver.
>
> This hack means that, in DT, we'd have to multiply by 2 the values given under
> section "22.3 GPIO interrupts" of the datasheet. This is an example Linux
> specific stuff in DT.
> It also means that the controller declares a lot more lines that it really has
> ...
>
> This is all to accommodate your hack around IRQ_TYPE_BOTH and creating the
> mapping from the irq_set_type callback of the GPIO driver, which is still think
> should be dropped at this point.
+1
Please drop the hack for IRQ_TYPE_BOTH so we can reach agreement on the
basic design and functionality. The gymnastics required to support this
hack (due to broken hardware) are getting in the way of getting basic
functionality merged.
Also, we already know from previous discussions between Jerome and the
IRQ maintainers that hacks for IRQ_TYPE_BOTH like this have been very
thoroughly rejected. So while the IRQ maintainers haven't chimed in on
this series, we have a very good idea what they will say when they do.
So please, pretty please, let's avoid giving the IRQ maintainers a fun
reason to NAK, and drop the IRQ_TYPE_BOTH stuff until we have an agreed
upon way to support the hardware that actually works.
Thanks,
Kevin
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2017-06-09 21:15 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-08 19:14 [PATCH v6 0/9] pinctrl: meson: add support for GPIO IRQs Heiner Kallweit
2017-06-08 19:14 ` Heiner Kallweit
2017-06-08 19:37 ` [PATCH v6 1/9] pinctrl: meson: add interrupts to pinctrl data Heiner Kallweit
2017-06-08 19:37 ` Heiner Kallweit
2017-06-09 7:30 ` Linus Walleij
2017-06-09 7:30 ` Linus Walleij
2017-06-08 19:38 ` [PATCH v6 2/9] irqchip: add Amlogic Meson GPIO irqchip driver Heiner Kallweit
2017-06-08 19:38 ` Heiner Kallweit
2017-06-09 7:31 ` Linus Walleij
2017-06-09 7:31 ` Linus Walleij
2017-06-09 9:07 ` Jerome Brunet
2017-06-09 9:07 ` Jerome Brunet
2017-06-09 18:38 ` Heiner Kallweit
2017-06-09 18:38 ` Heiner Kallweit
2017-06-09 21:15 ` Kevin Hilman [this message]
2017-06-09 21:15 ` Kevin Hilman
2017-06-09 22:30 ` Heiner Kallweit
2017-06-09 22:30 ` Heiner Kallweit
2017-06-09 23:30 ` Kevin Hilman
2017-06-09 23:30 ` Kevin Hilman
2017-06-08 19:38 ` [PATCH v6 3/9] dt-bindings: add Amlogic Meson GPIO interrupt-controller DT binding documentation Heiner Kallweit
2017-06-08 19:38 ` Heiner Kallweit
2017-06-08 19:38 ` [PATCH v6 4/9] ARM: dts: meson: add GPIO interrupt-controller support Heiner Kallweit
2017-06-08 19:38 ` Heiner Kallweit
2017-06-08 19:39 ` [PATCH v6 5/9] ARM64: " Heiner Kallweit
2017-06-08 19:39 ` Heiner Kallweit
2017-06-08 19:39 ` [PATCH v6 6/9] pinctrl: meson: add support for GPIO interrupts Heiner Kallweit
2017-06-08 19:39 ` Heiner Kallweit
2017-06-09 9:06 ` Jerome Brunet
2017-06-09 9:06 ` Jerome Brunet
2017-06-09 18:09 ` Heiner Kallweit
2017-06-09 18:09 ` Heiner Kallweit
2017-06-08 19:39 ` [PATCH v6 7/9] pinctrl: meson: update DT binding documentation Heiner Kallweit
2017-06-08 19:39 ` Heiner Kallweit
2017-06-08 19:39 ` [PATCH v6 8/9] ARM: dts: meson: mark gpio controllers as interrupt controllers Heiner Kallweit
2017-06-08 19:39 ` Heiner Kallweit
2017-06-08 19:39 ` [PATCH v6 9/9] ARM64: " Heiner Kallweit
2017-06-08 19:39 ` Heiner Kallweit
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=m2vao46ewu.fsf@baylibre.com \
--to=khilman@baylibre.com \
--cc=linus-amlogic@lists.infradead.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 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.