From: Boris Brezillon <boris.brezillon@free-electrons.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Simon Hatliff <hatliff@cadence.com>,
Alexandre Courbot <gnurou@gmail.com>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Subject: Re: [PATCH 1/2] gpio: Add a driver for Cadence GPIO controller
Date: Mon, 10 Apr 2017 15:26:10 +0200 [thread overview]
Message-ID: <20170410152610.58bc589a@bbrezillon> (raw)
In-Reply-To: <3422ee23-53b5-8d09-2a5e-d700358ab09d@cadence.com>
On Thu, 30 Mar 2017 18:26:01 +0100
Simon Hatliff <hatliff@cadence.com> wrote:
> Hi Boris, Linus,
>
> On 30/03/17 12:29, Boris Brezillon wrote:
> > Hi Linus,
> >
> > On Thu, 30 Mar 2017 11:03:45 +0200
> > Linus Walleij <linus.walleij@linaro.org> wrote:
> >
> >> On Wed, Mar 29, 2017 at 6:04 PM, Boris Brezillon
> >> <boris.brezillon@free-electrons.com> wrote:
> >>
> >>> Add a driver for Cadence GPIO controller.
> >> IIUC Cadence do a lot of things. Are there variants of this controller?
> > I'll let Simon answer that one.
> This is a controller that has been around since 2000. It is not
> configurable in any way, so there are no variants. Cadence do not offer
> any other GPIO controllers as IP.
> >>> +static irqreturn_t cdns_gpio_irq_handler(int irq, void *dev)
> >>> +{
> >>> + struct cdns_gpio_chip *cgpio = dev;
> >>> + unsigned long status;
> >>> + int hwirq;
> >>> +
> >>> + /*
> >>> + * FIXME: If we have an edge irq that is masked we might lose it
> >>> + * since reading the STATUS register clears all IRQ flags.
> >>> + * We could store the status of all masked IRQ in the cdns_gpio_chip
> >>> + * struct but we then have no way to re-trigger the interrupt when
> >>> + * it is unmasked.
> >>> + */
> >> It is marked FIXME but do you think it can even be fixed? It seems
> >> like a hardware flaw. :(
> > Maybe not. Unless Simon comes up with a magic register to re-trigger an
> > interrupt :-).
> There are no plans to update the controller.
Linus, what should I do here? Drop support for edge interrupts?
next prev parent reply other threads:[~2017-04-10 13:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-29 16:04 [PATCH 1/2] gpio: Add a driver for Cadence GPIO controller Boris Brezillon
2017-03-29 16:04 ` [PATCH 2/2] dt-bindings: gpio: Document Cadence GPIO controller bindings Boris Brezillon
2017-03-30 8:37 ` Linus Walleij
2017-03-30 9:03 ` [PATCH 1/2] gpio: Add a driver for Cadence GPIO controller Linus Walleij
2017-03-30 11:29 ` Boris Brezillon
2017-03-30 11:51 ` Linus Walleij
2017-03-30 17:26 ` Simon Hatliff
2017-03-31 13:28 ` Boris Brezillon
2017-04-10 13:26 ` Boris Brezillon [this message]
2017-04-24 13:00 ` Linus Walleij
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=20170410152610.58bc589a@bbrezillon \
--to=boris.brezillon@free-electrons.com \
--cc=gnurou@gmail.com \
--cc=hatliff@cadence.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=thomas.petazzoni@free-electrons.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;
as well as URLs for NNTP newsgroup(s).