Hi Peter, Am 07.05.2015 um 18:46 schrieb Dr. H. Nikolaus Schaller <hns@xxxxxxxxxxxxx>: > Hi Peter, > > Am 07.05.2015 um 17:51 schrieb Peter Hurley <peter@xxxxxxxxxxxxxxxxxx>: > >> On 05/07/2015 11:34 AM, Dr. H. Nikolaus Schaller wrote: >>> Am 07.05.2015 um 16:56 schrieb Peter Hurley <peter@xxxxxxxxxxxxxxxxxx>: >>>> On 05/07/2015 08:46 AM, Dr. H. Nikolaus Schaller wrote: >> >>>> Both devicetree and tty/serial can already represent independent control; >>>> what is proposed is a way to express dependent control, and in all cases, >>>> that control stems directly from either the UART state itself or via >>>> commands sent over that interface. >>> >>> Yes. This is why I propose that the tty/uart driver can send an internal notification >>> to the device driver. And the device driver can register to be notified by the UART >>> that is identified by the phandle of the slave DT entry. >> >> I've not seen any code with your proposal, so that makes it impossible to >> compare competing solutions. > > If you can give me some (unspecified) time to do it, I can write (simplified) patches > to demonstrate the idea. > > I just hesitate to work out and submit a counter proposal to what Neil has submitted, > because it will become wasted effort if it is rejected before I am finished. We have progress and some code on our workbench that identifies the uart_port by phandle, resolves probing sequence and intercepts uart_update_mctrl calls. So we can let the attached slave driver know that the DTR line has changed, which is typically the power-on/off signal on UART/RS232. The driver can then power manage the device as needed (GPIO state, GPIO pulses, regulator, I2C or whatever). What we have not yet solved is the issue that a slave driver might want to know that the controlled slave device is active (i.e. is autonomously sending data to the UART). Even if the tty is not open. But we have an rough idea how we want to solve that. Patches will come asap. BR, Nikolaus -- 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
