Hi!
> >>> Main reason is, that I would need to go
> >>> through the UART to “communicate" with the w2sg0004.
> >>
> >> You can always "communicate” through the UART. Even without DT. As long as
> >> the connected chip is powered up by any means (could be some fixed-regulator
> >> or hard wired).
> >
> > But you don't know "how" to communicate through the uart.
>
> Maybe we are talking using different assumptions. As long as you have a user space
> gpsd daemon that talks to the gps chip the kernel simply has to transparently (except
> line disciplines) pass the data to the uart.
Forget userspace, some other operating system (or future linux) may
want to put gps handling into the kernel. (To hide differences between
different GPSes).
> > Because we want the phone to boot knowing "I have a bluetooth" or "I
> > have a GPS", as it would if it was connected using USB, and not having
> > user figure out what commands he needs to do to enable reasonable
> > hardware support (and getting it wrong, because you need to specify
> > _many_ critical parameters to hciattach).
>
> Yes, this is indeed something I also would like to see for the GTA04 (and other)
> devices.
>
> So the reason is that some kernel driver wants to use the tty/uart to communicate
> directly with the chip. This is very similar to a gpio that some driver wants to use.
>
> Thus please consider the
>
> / {
> bt {
> compatible = "vendor,product“;
> uart = <&uart1>;
> enable = <&gpio17 34 0>;
> };
> };
Would work, too, but I and everyone knows that subnode is better,
easier solution.
> approach.
>
> And if you want to hide uart1 from the user-space, that should be a property
> of the uart1 node (whereever it is defined).
Sorry? That would be one heck of layering violation.
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 devicetree" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
