From: Rojhalat Ibrahim <imr@rtschenk.de>
To: Gerhard Sittig <gsi@denx.de>
Cc: Alexandre Courbot <gnurou@gmail.com>,
Linus Walleij <linus.walleij@linaro.org>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
Grant Likely <grant.likely@linaro.org>,
Mark Brown <broonie@kernel.org>, Wolfram Sang <wsa@the-dreams.de>
Subject: Re: [PATCH 1/2][v5] gpiolib: allow simultaneous setting of multiple GPIO outputs
Date: Thu, 07 Aug 2014 11:52:57 +0200 [thread overview]
Message-ID: <2709746.qxeoZQ4oRv@pcimr> (raw)
In-Reply-To: <20140806124544.GE28369@book.gsilab.sittig.org>
On Wednesday 06 August 2014 14:45:44 Gerhard Sittig wrote:
>
> Could you spot the LCD driver mentioned by Mark? There are
> displays that implement a typically four or optionally eight bit
> data bus plus some three control lines (E/RW/RS), usually GPIO
> bitbanged -- so in total it's 7 or 11 software controlled pins.
> One of the controller chips is HD44780, compatibles have KS...
> and SED... names.
>
I found a few display drivers using GPIOs for enable and/or reset lines,
but none using GPIOs for the data lines.
> It's a pity that drivers/auxdisplay/ and drivers/staging/panel/
> only support parport(4) and not GPIO.
>
That could be an interesting application.
>
> Why is your FPGA netlist download driver not acceptable for
> mainline? Because it uses many GPIOs instead of a parallel or
> serial bus? Doesn't your code submission make parallel busses
> done by many GPIOs "more acceptable"? If your netlist download
> follows the ususal passive parallel approach, there should not be
> an issue. There are some FPGA netlist download drivers in
> drivers/misc/ and you might follow that pattern.
>
>
Thanks for the suggestion. I have no problem with submitting that driver.
Right now it's probably a little too board-specific for mainline, but
I think I could improve on that. The result would be a driver to configure
an Altera FPGA via the passive parallel configuration scheme using a number
of GPIOs specified via DT. The driver would depend on the gpiod_set_array
function and for now it would be the only user.
Do you think this has a chance to get merged? Should I post an extended
patch set including the FPGA configuration driver?
Rojhalat
next prev parent reply other threads:[~2014-08-07 9:53 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-16 13:51 [PATCH 1/2][v5] gpiolib: allow simultaneous setting of multiple GPIO outputs Rojhalat Ibrahim
2014-06-21 7:08 ` Alexandre Courbot
2014-06-21 20:24 ` Mark Brown
2014-07-07 15:23 ` Linus Walleij
2014-07-07 16:12 ` Rojhalat Ibrahim
2014-07-09 10:17 ` Linus Walleij
2014-07-30 9:12 ` Rojhalat Ibrahim
2014-07-30 10:41 ` Mark Brown
2014-07-30 11:04 ` Rojhalat Ibrahim
2014-07-31 2:35 ` Alexandre Courbot
2014-07-31 7:12 ` Gerhard Sittig
2014-07-31 8:42 ` Rojhalat Ibrahim
2014-08-06 12:45 ` Gerhard Sittig
2014-08-06 19:39 ` Mark Brown
2014-08-07 9:52 ` Rojhalat Ibrahim [this message]
2014-08-29 5:21 ` Linus Walleij
2014-08-29 8:15 ` Wolfram Sang
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=2709746.qxeoZQ4oRv@pcimr \
--to=imr@rtschenk.de \
--cc=broonie@kernel.org \
--cc=gnurou@gmail.com \
--cc=grant.likely@linaro.org \
--cc=gsi@denx.de \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=wsa@the-dreams.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 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).