From: Rob Herring <robh@kernel.org>
To: Phil Edworthy <phil.edworthy@renesas.com>
Cc: Hoan Tran <hotran@apm.com>,
Linus Walleij <linus.walleij@linaro.org>,
Mark Rutland <mark.rutland@arm.com>,
Andy Shevchenko <andy.shevchenko@gmail.com>,
Michel Pollet <michel.pollet@bp.renesas.com>,
linux-gpio@vger.kernel.org, devicetree@vger.kernel.org,
linux-renesas-soc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] gpio: dwapb: Add support for 32 interrupts
Date: Mon, 9 Apr 2018 14:20:13 -0500 [thread overview]
Message-ID: <20180409192013.5rytwgoixtyraow3@rob-hp-laptop> (raw)
In-Reply-To: <1522246950-9110-1-git-send-email-phil.edworthy@renesas.com>
On Wed, Mar 28, 2018 at 03:22:30PM +0100, Phil Edworthy wrote:
> The DesignWare GPIO IP can be configured for either 1 or 32 interrupts,
> but the driver currently only supports 1 interrupt. See the DesignWare
> DW_apb_gpio Databook description of the 'GPIO_INTR_IO' parameter.
Someday h/w designers will realize this does nothing to optimize
interrupt handling...
> This change allows the driver to work with up to 32 interrupts, it will
> get as many interrupts as specified in the DT 'interrupts' property.
> It doesn't do anything clever with the different interrupts, it just calls
> the same handler used for single interrupt hardware.
>
> Signed-off-by: Phil Edworthy <phil.edworthy@renesas.com>
> ---
> Note: There are a few lines over 80 chars, but this is just guidance, right?
> Especially as there are already some lines over 80 chars.
Code, yes, but not for paragraphs of text in DT bindings.
> ---
> .../devicetree/bindings/gpio/snps-dwapb-gpio.txt | 10 ++++-
> drivers/gpio/gpio-dwapb.c | 44 +++++++++++++++++-----
> include/linux/platform_data/gpio-dwapb.h | 3 +-
> 3 files changed, 45 insertions(+), 12 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/gpio/snps-dwapb-gpio.txt b/Documentation/devicetree/bindings/gpio/snps-dwapb-gpio.txt
> index 4a75da7..e343581 100644
> --- a/Documentation/devicetree/bindings/gpio/snps-dwapb-gpio.txt
> +++ b/Documentation/devicetree/bindings/gpio/snps-dwapb-gpio.txt
> @@ -26,8 +26,14 @@ controller.
> the second encodes the triger flags encoded as described in
> Documentation/devicetree/bindings/interrupt-controller/interrupts.txt
> - interrupt-parent : The parent interrupt controller.
> -- interrupts : The interrupt to the parent controller raised when GPIOs
> - generate the interrupts.
> +- interrupts : The interrupts to the parent controller raised when GPIOs
> + generate the interrupts. If the controller provides one combined interrupt
> + for all GPIOs, specify a single interrupt. If the controller provides one
> + interrupt for each GPIO, provide a list of interrupts that correspond to each
> + of the GPIO pins. When specifying multiple interrupts, if any of the GPIOs are
> + not connected to an interrupt, use the interrupt-mask property.
> +- interrupt-mask : a 32-bit bit mask that specifies which interrupts in the list
> + of interrupts is valid, bit is 1 for a valid irq.
This is not a standard property and would need a vendor prefix. However,
I'd prefer you just skip any not connected interrupts with an invalid
interrupt number. Then the GPIO number is the index into "interrupts".
> - snps,nr-gpios : The number of pins in the port, a single cell.
This BTW should be deprecated to use "nr-gpios" instead, but that's
another patch.
> - resets : Reset line for the controller.
>
next prev parent reply other threads:[~2018-04-09 19:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-28 14:22 Phil Edworthy
2018-03-29 9:39 ` Phil Edworthy
2018-03-30 21:26 ` Andy Shevchenko
2018-04-05 9:42 ` Phil Edworthy
2018-04-06 9:57 ` Geert Uytterhoeven
2018-04-06 10:20 ` Phil Edworthy
2018-04-11 10:17 ` Phil Edworthy
2018-04-09 19:20 ` Rob Herring [this message]
2018-04-10 6:24 ` Phil Edworthy
2018-04-10 14:23 ` Phil Edworthy
2018-04-10 14:29 ` Geert Uytterhoeven
2018-04-10 15:00 ` Phil Edworthy
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=20180409192013.5rytwgoixtyraow3@rob-hp-laptop \
--to=robh@kernel.org \
--cc=andy.shevchenko@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=hotran@apm.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=michel.pollet@bp.renesas.com \
--cc=phil.edworthy@renesas.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®