linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vincent Pelletier <plr.vincent@gmail.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: "linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>
Subject: Re: [RFC] qnap-tsx51: add new driver for leds and button support on QNAP TS-x51 series
Date: Sat, 18 Jun 2016 07:18:06 +0000	[thread overview]
Message-ID: <20160618071806.546da3fa@gmail.com> (raw)
In-Reply-To: <CACRpkdZx8S61zZhcWfEniC-yDhMXyTwZYgXc=sO+74kujT=g-w@mail.gmail.com>

Hello,

On Fri, 17 Jun 2016 23:02:47 +0200, Linus Walleij
<linus.walleij@linaro.org> wrote:
> Well ask yourself what you are doing I guess, GPIO is
> General Purpose Input Output, a trap some people fall into
> is confusing that with their special purpose input/outputs,
> and sometimes they are input-only or output-only on top of
> that. That is not GPIO.
> 
> So what is the use case for these electronics? If it is not
> supposed to be used by misc input/output, it is not GPIO,
> and it is better for the driver to manage it at will.

Thanks, I think it is the distinction I did not do.

Just to confirm my understanding:
- from the chip (and its module) point of view, these signals are
  GPIOs, because they cannot presume how it is wired
- but from the platform point of view (this specific NAS model), these
  GPIOs are wired to leds and buttons, so they are leds and buttons
  and not GPIOs anymore

So using GPIO numbers is acceptable in such driver.

Is this correct ?
If it is, I will submit my patch on platform-drivers ML.

Regards,
-- 
Vincent Pelletier

  reply	other threads:[~2016-06-18  7:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-06  0:44 [RFC] qnap-tsx51: add new driver for leds and button support on QNAP TS-x51 series Vincent Pelletier
2016-06-14  7:17 ` Linus Walleij
2016-06-15  0:45   ` Vincent Pelletier
2016-06-17 21:02     ` Linus Walleij
2016-06-18  7:18       ` Vincent Pelletier [this message]
2016-06-18  8:00         ` 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=20160618071806.546da3fa@gmail.com \
    --to=plr.vincent@gmail.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@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).