linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: William Breathitt Gray <vilhelm.gray@gmail.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Alexandre Courbot <gnurou@gmail.com>,
	"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v5] gpio: Add GPIO support for the WinSystems WS16C48
Date: Thu, 28 Jan 2016 08:50:58 -0500	[thread overview]
Message-ID: <20160128135058.GA16395@sophia> (raw)
In-Reply-To: <CACRpkdaMchsc9E-8JTMoKR6cFP9WEBTUrkPiQxqyrkGHXp-xWg@mail.gmail.com>

On Thu, Jan 28, 2016 at 09:47:43AM +0100, Linus Walleij wrote:
>Out of curiosity: what is your usecase for all these exotic
>GPIO cards?

My motivated mainly by philosophy. Despite their popularity in the
embedded systems industry, there isn't much support in the baseline
kernel for PC/104 and other cards. Typically, when a user purchases one
of these devices, they receive some general drivers which serve more as
proof that the device is working rather than as practical driver.

The user is lucky if they receive Linux drivers rather than just the
usual Windows drivers. Even if Linux drivers are provided, the drivers
are often written for ancient kernel versions (e.g. version 2.4), and
implement some custom character device structure rather than utilize the
Linux device model.

I'm writing these drivers to help bring support for these devices to the
baseline Linux kernel, in the hopes that it will be useful to someone,
and perhaps even motivate the companies to improve and share their own
Linux drivers.

William Breathitt Gray

      reply	other threads:[~2016-01-28 13:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-20 18:45 [PATCH v5] gpio: Add GPIO support for the WinSystems WS16C48 William Breathitt Gray
2016-01-28  8:47 ` Linus Walleij
2016-01-28 13:50   ` William Breathitt Gray [this message]

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=20160128135058.GA16395@sophia \
    --to=vilhelm.gray@gmail.com \
    --cc=gnurou@gmail.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 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).