From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: Einar Vading <einar.vading@axis.com>
Cc: Vincent Whitchurch <rabinv@axis.com>,
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: SV: [PATCH RFC] gpio: new driver for a gpio simulator
Date: Fri, 12 Oct 2018 11:06:12 +0200 [thread overview]
Message-ID: <20181012090612.63f2p45d24gpilsm@pengutronix.de> (raw)
In-Reply-To: <1539331329658.80509@axis.com>
Hello Einar,
On Fri, Oct 12, 2018 at 08:02:09AM +0000, Einar Vading wrote:
> Since I was just evaluating the mockup driver to use in a test setup
> I'll give my 2 cents.
very welcome, thanks.
> The benefit of the simulator is that we get the possibility to, if I
> understand correctly, monitor an input for changes on the connected
> output. Sure, we could also use ftrace but I like the idea of having
> the two connected GPIOs. As a matter of fact I was just thinking about
> implementing something that gave the same functionality for the mockup
> driver.
>
> What I like from the mockup driver is the possibility to have *many*
> gpios on the same chip. We currently have a MCU I/O expander that
> gives us 110+ gpios. So for us 64 GPIOs is really not enough.
Currently several states are stored in an u32 where each bit corresponds
to a GPIO which simplifies some operations. Probably an array of
unsigned long could be used, which would have the benefit that set_bit
et al would work. Then we either need a compile time limit, a variadic
driver data struct or one additional allocation for each variable that
is an u32 currently.
Would it help to instanciate more than one gpio-simulator?
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-K�nig |
Industrial Linux Solutions | http://www.pengutronix.de/ |
next prev parent reply other threads:[~2018-10-12 16:37 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
2018-10-12 8:02 ` SV: " Einar Vading
2018-10-12 9:06 ` Uwe Kleine-König [this message]
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=20181012090612.63f2p45d24gpilsm@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--cc=brgl@bgdev.pl \
--cc=devicetree@vger.kernel.org \
--cc=einar.vading@axis.com \
--cc=kernel@pengutronix.de \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=rabinv@axis.com \
--cc=robh+dt@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).