> -----Original Message----- > From: Alan Cox [mailto:alan@xxxxxxxxxxxxxxxxxxx] > Sent: Thursday, October 07, 2010 4:00 PM > To: Savoy, Pavan > Cc: Jiri Slaby; gregkh@xxxxxxx; linux-kernel@xxxxxxxxxxxxxxx; > devel@xxxxxxxxxxxxxxxxxxxx; linux-bluetooth@xxxxxxxxxxxxxxx > Subject: Re: [PATCH 1/2] drivers:staging:ti-st: move TI_ST from staging > > > But, I want to attach my data not when ldsic is opened, but when ldisc is > registered. > > I want to begin accessing the data when ldisc is opened. > > How can you attach per tty data when the ldisc is registered - the > relevant tty driver might not even have been loaded at that point. The > user may not even have been to the shop and bought it even ! > > What sort of data is this ? Data related to requesting the user-space to open/install the ldisc. Imagine a UEVENT structure or PID of the user-space process to which I need to send a signal .. I currently use rfkill. > > to be like a bunch of helpers (1 for FM, 1 for GPS, 1 for NFC, 1 for power- > management), also the problem of who owns the /dev/tty begins to occur, > Bluetooth has a utility called hciattach, I don't want my FM radio software to > run hciattach when /dev/radio0 is opened and communicated via FM. > > I would have assumed the hotplug script would have run your own attach > and daemon and the FM radio etc would talk to the ldisc via other kernel > interfaces it presented. > > So whenever the hardware is detected it would load the hardware driver > The hardware driver would create a tty instance for each physical port > The hotplug user space would run 'ti-st-attach' as a helper which would > load the ldisc and set up the bluetooth as well as providing exported > methods for FM radio etc. Yes, pretty similar to what I am doing now. I have this daemon which waits for events from my ldisc driver, and on receiving the notification it opens the uart, ioctl's the TIOCSETD and allows the tty to be accessed over the ldisc. > > In any case, the ti-st/ seems better now by look of things, I certainly > welcome suggestions to improve it. > > Also, is there any plan to re-write whole of TTY like a the i2C or the SPI > bus structure? > > > > Here I can imagine, all TTY line disciplines being sort of protocol/client > drivers, the TTY sub-system in itself would be like the algos driver and then > > The uart drivers (like 8250.c) can be the adapter drivers.. What say? > > They already are, with the one oddity being that something needs to have > it opened from user space and to attach the ldisc. Thats fixable but hard > to fix and I'm not aware of any plan to do so - mostly because nobody > needs it so far. Yes, that oddity was the reason this notification had to be done. I could as well have opened it up on boot and attached the ldisc, but I chose to use it whenever other drivers wanted to - as in when hci0 is UP, or /dev/radio0 is opened. > Alan _______________________________________________ devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxx http://driverdev.linuxdriverproject.org/mailman/listinfo/devel
