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 -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
