All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bartosz Golaszewski <brgl@bgdev.pl>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Grygorii Strashko <grygorii.strashko@ti.com>,
	"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Jerome Brunet <jbrunet@baylibre.com>
Subject: Re: [RFT PATCH v2] gpiolib: allow gpio irqchip to map irqs dynamically
Date: Tue, 1 Aug 2017 11:53:42 +0200	[thread overview]
Message-ID: <CAMRc=MdgOmVfQ9-qTQ2XOkj90GojBVco_qpQ3Ryms7F4YBLvdA@mail.gmail.com> (raw)
In-Reply-To: <CACRpkdbFVV669PxGDXO9Xzf-jj0sEKyQTvhdLMA_of16wBp7PQ@mail.gmail.com>

2017-08-01 9:52 GMT+02:00 Linus Walleij <linus.walleij@linaro.org>:
>
> Applied this rather than v1.
>
> But maybe we should get rid of ->irq_base from gpio-mockup.c
> and delete it, as the base is irqchip-internal.
>
> Bartosz what do you say? Do we need this in the mockup?
>
> Yours,
> Linus Walleij

Hi Linus,

a while ago I submitted a series[1] adding a simple framework for
simulating interrupts with the intention of removing most of the
irq_work code from gpio-mockup and iio-dummy-evgen. The third patch in
that series[2] does that for the mockup driver. I'll send a v2 shortly
and I hope to get it merged for v4.14.

Best regards,
Bartosz Golaszewski

[1] https://lkml.org/lkml/2017/7/19/698
[2] https://lkml.org/lkml/2017/7/19/696

  parent reply	other threads:[~2017-08-01  9:53 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-21 16:49 [RFT PATCH v2] gpiolib: allow gpio irqchip to map irqs dynamically Grygorii Strashko
2017-07-21 16:49 ` Grygorii Strashko
2017-08-01  7:52 ` Linus Walleij
2017-08-01  8:03   ` Jerome Brunet
2017-08-01 18:27     ` Grygorii Strashko
2017-09-15  8:26       ` Jerome Brunet
2017-09-21 11:41         ` Linus Walleij
2017-10-05 10:59           ` Marc Zyngier
2017-08-01  9:53   ` Bartosz Golaszewski [this message]
2017-09-28  8:33 ` Mika Westerberg
2017-09-28 14:02   ` Grygorii Strashko
2017-09-28 14:02     ` Grygorii Strashko
2017-09-28 14:26     ` Mika Westerberg
2017-10-08  0:27   ` Linus Walleij
2017-10-09 18:10     ` Grygorii Strashko
2017-10-09 19:57       ` Linus Walleij
2017-10-09 22:17         ` Grygorii Strashko

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='CAMRc=MdgOmVfQ9-qTQ2XOkj90GojBVco_qpQ3Ryms7F4YBLvdA@mail.gmail.com' \
    --to=brgl@bgdev.pl \
    --cc=grygorii.strashko@ti.com \
    --cc=jbrunet@baylibre.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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.