From: Michael Welling <mwelling@ieee.org>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Alexandre Courbot <gnurou@gmail.com>,
folkert <folkert@vanheusden.com>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>
Subject: Re: Fw: [3.18.3] poll() on gpio pins broken
Date: Tue, 17 Mar 2015 11:47:25 -0500 [thread overview]
Message-ID: <20150317164724.GA3610@deathray> (raw)
In-Reply-To: <CACRpkdaC6A1D-rOeCywR9QHRc9wdKTcHVjEMfYCHrg0Jz0vwxg@mail.gmail.com>
On Tue, Mar 17, 2015 at 05:39:01PM +0100, Linus Walleij wrote:
> On Mon, Mar 9, 2015 at 9:22 PM, Michael Welling <mwelling@ieee.org> wrote:
> > On Mon, Mar 09, 2015 at 04:52:26PM +0100, Linus Walleij wrote:
>
> >> Whoever comes up with a cleaner sysfs or a clean device interface
> >> will win the argument and lock the path for the other approach.
> >> It's like a forking path with no going back or something.
> >
> > There is no need to fork and in fact it would probably be a bad idea.
>
> For the record I am *NOT* talking about this:
> https://en.wikipedia.org/wiki/Fork_%28software_development%29
>
Okay.
> > At EMAC we support both sysfs and character device simultaneously.
> > Sysfs for the ease of use and ioctl for real time advantages.
>
> What is EMAC?
It is the company that I am currently working for.
www.emacinc.com
>
> > Not saying that it is a good reference but the two interfaces "could" co-exist.
>
> Hm....
>
> I would more think about deprecating the sysfs in favor of the dev
> node.
What happens to all of the users of the sysfs interface when this happens?
>
> But this is getting terribly academic since we're just talking, noone is
> really implementing anything.
Without a specification nothing is ever going to be implemented.
If not here, where will we be able to discuss the implementation details?
>
> Yours,
> Linus Walleij
next prev parent reply other threads:[~2015-03-17 16:47 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-29 15:29 Fw: [3.18.3] poll() on gpio pins broken folkert
2015-01-30 23:45 ` Michael Welling
2015-01-31 8:33 ` folkert
2015-01-31 13:39 ` Alexandre Courbot
2015-01-31 13:53 ` folkert
2015-02-03 9:03 ` Michael Welling
2015-02-13 3:43 ` Linus Walleij
2015-02-19 8:53 ` folkert
2015-02-19 16:52 ` Linus Walleij
2015-02-26 10:27 ` Alexandre Courbot
2015-02-27 13:15 ` Linus Walleij
2015-02-27 13:19 ` folkert
2015-03-02 6:20 ` Alexandre Courbot
2015-03-02 6:16 ` Alexandre Courbot
2015-03-02 7:27 ` Michael Welling
2015-03-03 8:27 ` Alexandre Courbot
2015-03-03 10:31 ` Linus Walleij
2015-03-04 12:43 ` Alexandre Courbot
2015-03-09 15:52 ` Linus Walleij
2015-03-09 19:02 ` folkert
2015-03-09 20:22 ` Michael Welling
2015-03-17 16:39 ` Linus Walleij
2015-03-17 16:47 ` Michael Welling [this message]
2015-03-19 8:30 ` Linus Walleij
2015-02-26 10:29 ` Alexandre Courbot
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=20150317164724.GA3610@deathray \
--to=mwelling@ieee.org \
--cc=folkert@vanheusden.com \
--cc=gnurou@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 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.