From: Linus Walleij <linus.walleij@linaro.org>
To: Davide Hug <d@videhug.ch>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Grygorii Strashko <grygorii.strashko@ti.com>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>
Subject: Re: Should irq_enable/disable be flagging/unflagging gpio lines used as irq?
Date: Tue, 1 Aug 2017 09:37:12 +0200 [thread overview]
Message-ID: <CACRpkdZ2gm6gE+M2OLHBchUtS+F-L+UYSVSZyXOJin9j9Q4EVg@mail.gmail.com> (raw)
In-Reply-To: <20170713221729.cb6352445665b4e3d71d1cb1@videhug.ch>
On Thu, Jul 13, 2017 at 10:17 PM, Davide Hug <d@videhug.ch> wrote:
> Thanks. I probably should have pointed out that I'm just getting started.
> I thought this driver that does not load would be a good place to do that. But
> obviously a "completely broken" driver that "breaks with the current semantics
> of the GPIO interrupt" is the wrong place to get started and learn how things
> should be done.
>
> So this driver should probably be rewritten using timer based polling and the
> descriptor based gpio interface. But since it is a really specific driver for
> sensors that are already discontinued it probably doesn't make much sense. And
> I'm not yet up to the task anyway.
I'm not so sure about that. You might be the only one with the right hardware
to fix the problem. Also it is never our intention to discourage anyone to
hack on the kernel.
If you have this hardware and know what you want to get out of it, go for it.
> Are the drivers listed in Documentation/gpio/drivers-on-gpio.txt good examples
> of GPIO consumer drivers?
I think some, I am fixing others, anything just including
<linux/gpio/consumer.h>
and no other GPIO header are usually good examples.
Yours,
Linus Walleij
next prev parent reply other threads:[~2017-08-01 7:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-11 17:55 Should irq_enable/disable be flagging/unflagging gpio lines used as irq? Davide Hug
2017-07-12 11:35 ` Linus Walleij
2017-07-12 18:33 ` Grygorii Strashko
2017-07-12 21:41 ` Thomas Gleixner
2017-07-13 20:17 ` Davide Hug
2017-08-01 7:37 ` Linus Walleij [this message]
2017-08-25 22:45 ` Davide Hug
2017-09-08 14:22 ` Linus Walleij
2017-09-10 14:16 ` Davide Hug
2017-09-12 13:57 ` Linus Walleij
2017-11-20 22:48 ` Davide Hug
2017-11-30 13:55 ` 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=CACRpkdZ2gm6gE+M2OLHBchUtS+F-L+UYSVSZyXOJin9j9Q4EVg@mail.gmail.com \
--to=linus.walleij@linaro.org \
--cc=d@videhug.ch \
--cc=grygorii.strashko@ti.com \
--cc=linux-gpio@vger.kernel.org \
--cc=tglx@linutronix.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).