[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20160817155452.GA14957@amd>
Date: Wed, 17 Aug 2016 17:54:52 +0200
From: Pavel Machek <pavel@....cz>
To: Rob Herring <robh@...nel.org>
Cc: Sebastian Reichel <sre@...nel.org>,
Tony Lindgren <tony@...mide.com>,
Mark Rutland <mark.rutland@....com>,
Marcel Holtmann <marcel@...tmann.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Jiri Slaby <jslaby@...e.com>, Ville Tervo <ville.tervo@....fi>,
Filip Matijević <filip.matijevic.pz@...il.com>,
Aaro Koskinen <aaro.koskinen@....fi>,
Pali Rohár <pali.rohar@...il.com>,
Ivaylo Dimitrov <ivo.g.dimitrov.75@...il.com>,
linux-bluetooth@...r.kernel.org,
"linux-serial@...r.kernel.org" <linux-serial@...r.kernel.org>,
linux-omap <linux-omap@...r.kernel.org>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [RFC 3/7] dt: bindings: Add nokia-bluetooth
Hi!
> >> > + - reset-gpios: Should specify the gpio for bluetooth reset
> >> > + - host-wakeup-gpios: Should specify the gpio for host wakeup
> >>
> >> Should be interrupt instead?
> >
> > Yes this is mostly an interrupt, but I need to read the current
> > line state.
>
> When? If the interrupt is level triggered, then you can get the line
> state based on whether you get an interrupt or not. If this needs to
> be a wakeup source (see the wakeup source binding), then it needs to
> be an interrupt.
What is wrong with GPIO? It is simply a piece of wire. Yes, we'll
configure it to generate an interrupt, or maybe not, but that's
software detail, the device tree just should not care....
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
Powered by blists - more mailing lists