linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bartosz Golaszewski <bgolaszewski@baylibre.com>
To: Linus Walleij <linus.walleij@linaro.org>,
	Alexandre Courbot <gnurou@gmail.com>,
	Bamvor Jian Zhang <bamvor.zhangjian@linaro.org>,
	Lars-Peter Clausen <lars@metafoo.de>
Cc: linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
	Bartosz Golaszewski <bgolaszewski@baylibre.com>
Subject: [PATCH v3 0/2] gpio: mockup: extensions for testing purposes
Date: Mon,  6 Feb 2017 15:11:06 +0100	[thread overview]
Message-ID: <1486390268-31362-1-git-send-email-bgolaszewski@baylibre.com> (raw)

Hi Linus,

this is a follow-up to the gpio-mockup series. I dropped the resource
managed version of irq_alloc_descs() to avoid needing an ack from the
irq subsystem maintainers. I omitted all the already applied patches
too.

Rebased on top of gpio/devel and retested.

v2 -> v3:
- dropped the resource managed irq allocation and added a remove
  function instead
- also selected IRQ_WORK in gpio Kconfig
- included <gpio/consumer.h> from gpio-mockup.c instead of indirectly
  from gpiolib.h

Bartosz Golaszewski (2):
  gpio: mockup: add a dummy irqchip
  gpio: mockup: implement event injecting over debugfs

 drivers/gpio/Kconfig       |   2 +
 drivers/gpio/gpio-mockup.c | 195 ++++++++++++++++++++++++++++++++++++++++++++-
 2 files changed, 196 insertions(+), 1 deletion(-)

-- 
2.9.3

             reply	other threads:[~2017-02-06 14:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-06 14:11 Bartosz Golaszewski [this message]
2017-02-06 14:11 ` [PATCH v3 1/2] gpio: mockup: add a dummy irqchip Bartosz Golaszewski
2017-02-13  7:36   ` Linus Walleij
2017-02-06 14:11 ` [PATCH v3 2/2] gpio: mockup: implement event injecting over debugfs Bartosz Golaszewski
2017-02-13  7:38   ` 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=1486390268-31362-1-git-send-email-bgolaszewski@baylibre.com \
    --to=bgolaszewski@baylibre.com \
    --cc=bamvor.zhangjian@linaro.org \
    --cc=gnurou@gmail.com \
    --cc=lars@metafoo.de \
    --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 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).