Hi Giacinto, > > was it necessary to remove entirely the NEED_THREADS flag? > > > > I was going to use it in the Gemalto driver, to speed up the device > > recognition, because for some modules it is hit and miss. > > But only as an optional feature, because in some systems it might be > > missing. > > > > Also, for some high-speed modems which take long to boot, there is a > > potential critical race in the recognition that the use threads can solve > > easily. The alternative is to increase the internal timers a lot. > > > > I likely need to add a new flag for it. > > using threads is not the solution. This can be all done properly with single > thread event loop driven methods. > > for sure, and in fact as of now the support is optional. > But I already need to ask for an extension of the Powered timout from 20 to > 60 seconds because several LTE chipsets take at least 30-40 seconds to boot > once they have already enumerated on USB. It would be good to shorten this > time. > > Besides, several modules use the option linux driver, which blocks in case > the port doesn't answer. > This single call: > g_at_chat_unref(port); > blocks either 30s or 1 minute, depending on the system. I might step into it > twice during my hardware initialization for several 3G models. > It helps to run this line on a separate thread unblocking the rest.
no it does not. Nothing in GAtChat is thread safe. So running this in a separate thread just means you are having tons of race conditions on your hand. Regards Marcel _______________________________________________ ofono mailing list ofono@ofono.org https://lists.ofono.org/mailman/listinfo/ofono
