All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vincent Whitchurch <vincent.whitchurch@axis.com>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: Linus Walleij <linus.walleij@linaro.org>,
	Bartosz Golaszewski <brgl@bgdev.pl>,
	Mark Rutland <mark.rutland@arm.com>,
	"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
	<devicetree@vger.kernel.org>,
	"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
	Rob Herring <robh+dt@kernel.org>,
	Sascha Hauer <kernel@pengutronix.de>
Subject: Re: [PATCH RFC] gpio: new driver for a gpio simulator
Date: Thu, 11 Oct 2018 11:49:05 +0200	[thread overview]
Message-ID: <20181011094905.47onipkrzdp25psq@axis.com> (raw)
In-Reply-To: <20181011081646.np2pte7eeohuyhh6@pengutronix.de>

On Thu, Oct 11, 2018 at 10:16:46AM +0200, Uwe Kleine-K�nig wrote:
> @Vincent: What is your usecase? I currently cannot imagine a use case
> that can be done with the mockup driver but not with the simulator.

I just needed a fake GPIO chip with a bunch of pins that I could use
before I got the hardware with a real GPIO expander.  In my case I only
needed to test output so IIRC I didn't use the debugfs interface at all
but instead used ftrace to check that my userspace triggered the correct
operations on the "pins".

So, yes, that would probably have worked just as well with this
simulator instead of the mockup driver.

  reply	other threads:[~2018-10-11  9:49 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-08 10:13 [PATCH RFC] gpio: new driver for a gpio simulator Uwe Kleine-König
2018-10-08 13:08 ` Uwe Kleine-König
2018-10-09 12:51 ` Linus Walleij
2018-10-09 19:11   ` Uwe Kleine-König
2018-10-10 11:47     ` Linus Walleij
2018-10-11  8:16       ` Uwe Kleine-König
2018-10-11  9:49         ` Vincent Whitchurch [this message]
2018-10-12  8:02           ` SV: " Einar Vading
2018-10-12  9:06             ` Uwe Kleine-König
2018-10-12  9:27               ` Einar Vading
2018-10-12  9:47                 ` Uwe Kleine-König
2018-10-15  9:54                   ` Bartosz Golaszewski
2018-10-15 20:03                     ` Uwe Kleine-König
2018-10-18 15:03                       ` Bartosz Golaszewski
2018-10-18 19:16                         ` Uwe Kleine-König
2018-10-30 12:45                           ` Linus Walleij
2018-11-03 21:15                             ` Uwe Kleine-König

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=20181011094905.47onipkrzdp25psq@axis.com \
    --to=vincent.whitchurch@axis.com \
    --cc=brgl@bgdev.pl \
    --cc=devicetree@vger.kernel.org \
    --cc=kernel@pengutronix.de \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=robh+dt@kernel.org \
    --cc=u.kleine-koenig@pengutronix.de \
    /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.