Hello Greg, On Wed, Nov 07, 2018 at 10:43:17AM +0100, Greg Kroah-Hartman wrote: > On Wed, Nov 07, 2018 at 10:39:25AM +0100, Uwe Kleine-König wrote: > > On Wed, Nov 07, 2018 at 10:29:21AM +0100, Greg Kroah-Hartman wrote: > > > On Tue, Nov 06, 2018 at 10:37:37PM +0100, Uwe Kleine-König wrote: > > > > I'm not yet sure how to get the locking right. After the trigger driver > > > > got a pointer to the uart_ports structure the port must not go away > > > > until the statistics are checked. If you have an idea here that would > > > > be great. > > > > > > How does the networking core handle this type of interaction? Can't you > > > solve this the same way they do? > > > > the netdev trigger keeps the device active using dev_hold/dev_put. > > Ok, and why will that same scheme not work here as well? I'm not aware that there is an equivalent mechanism for UARTs (or ttys) that prevents unbinding the device. Best regards Uwe -- Pengutronix e.K. | Uwe Kleine-König | Industrial Linux Solutions | http://www.pengutronix.de/ |
