Open Source Telephony
 help / color / mirror / Atom feed
From: Denis Kenzior <denkenz@gmail.com>
To: "Любимов Максим" <m.lyubimov@aqsi.ru>, ofono@lists.linux.dev
Subject: Re: [PATCH 14/15] gatchat: added command completion by timeout
Date: Sun, 29 Oct 2023 15:59:08 -0500	[thread overview]
Message-ID: <d78baea0-813c-414d-bf8d-d9a06fbdb5fa@gmail.com> (raw)
In-Reply-To: <d9591456ec4294c216445b6b0b73d2b54d94c2e0.camel@aqsi.ru>

Hi Максим,

On 10/27/23 04:45, Любимов Максим wrote:
> On 18/10/2023 в 21:21 -0500, Denis Kenzior wrote:
>> So I think you're going to need to give a bit more context for how
>> this is
>> expected to work.  There are commands (on older modems) that can take
>> minutes to
>> complete.  This is why multiplexers were invented.  Now this is
>> probably quite
>> rare, but I imagine it can still happen.
> 
> This functionality was added because some modems sometimes do not
> respond to the command. Therefore, there is an endless wait for a
> response and blocking of other functions with a message that the action

Ok, but which modems?  Do you have an OFONO_AT_DEBUG log trace you can share?

Anyhow, at the very least you need to make this an opt-in feature.  As I pointed 
out, opting in *all* modem drivers into this functionality will break some of them.

> is still in progress. It was experimentally verified that if the
> command is repeated, the modem can immediately respond to it and there
> will be no blocking. What do you suggest to do if the modem does not
> respond to the command either after a minute, or after an hour, never?

Call the vendor and have them fix their firmware? :)  But seriously, how many 
commands are we talking about?  If it is one, then handle it specifically for 
that command.  If it is a dozen, create a utility function.

I'm not convinced adding this functionality directly to GAtChat is the right 
approach.  There is no such thing as 'AT command timeout' in V.250 specification 
or any other standard.  AT command cancellation as a concept exists, but it only 
works sometimes and only for some commands, and isn't what you're doing here 
from what I can tell.

What you're describing is vendor specific behavior and has to be treated as such.

> 
>> Also, what happens if the command times out?  You generate a
>> synthetic CME 100
>> error, but what then?
> 
> The function that sent the command must take action based on its
> operating logic, for example, repeat the command, or fail.
> 

Okay, so where is this code?

Regards,
-Denis

  reply	other threads:[~2023-10-29 20:59 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-17 10:48 [PATCH 01/15] Skipping AT+CUAD sending for QUECTEL_EC2X vendor MaxLyubimov
2023-10-17 10:48 ` [PATCH 02/15] drivers: adding support for the SIMCom A7605E-H MaxLyubimov
2023-10-19  1:30   ` Denis Kenzior
2023-10-27  7:52     ` Любимов Максим
2023-10-29 21:16       ` Denis Kenzior
2023-10-17 10:48 ` [PATCH 03/15] plugins: " MaxLyubimov
2023-10-19  1:42   ` Denis Kenzior
2023-10-27  9:01     ` Любимов Максим
2023-10-29 20:41       ` Denis Kenzior
2023-10-30  7:11         ` Любимов Максим
2023-10-17 10:48 ` [PATCH 04/15] build: " MaxLyubimov
2023-10-17 10:48 ` [PATCH 05/15] drivers: quectel: Add radio settings MaxLyubimov
2023-10-19  1:49   ` Denis Kenzior
2023-10-17 10:48 ` [PATCH 06/15] build: Add quectel radio settings rules MaxLyubimov
2023-10-17 10:48 ` [PATCH 07/15] plugins: quectel: Add radio settings MaxLyubimov
2023-10-19  2:00   ` Denis Kenzior
2023-10-17 10:48 ` [PATCH 08/15] drivers: gemalto: Add models list MaxLyubimov
2023-10-17 10:48 ` [PATCH 09/15] plugins: gemalto: Include " MaxLyubimov
2023-10-17 10:48 ` [PATCH 10/15] plugins: udevng: Add support gemalto EHS5-E MaxLyubimov
2023-10-17 10:48 ` [PATCH 11/15] gemalto: radio-settings: Add support EHS5-E MaxLyubimov
2023-10-17 10:48 ` [PATCH 12/15] Fix PPP LCP Configure-Reject MaxLyubimov
2023-10-19  2:08   ` Denis Kenzior
2023-10-17 10:49 ` [PATCH 13/15] atmodem: added context deactivation event handling MaxLyubimov
2023-10-19  2:13   ` Denis Kenzior
2023-10-17 10:49 ` [PATCH 14/15] gatchat: added command completion by timeout MaxLyubimov
2023-10-19  2:21   ` Denis Kenzior
2023-10-27  9:45     ` Любимов Максим
2023-10-29 20:59       ` Denis Kenzior [this message]
2023-10-30  7:04         ` Любимов Максим
2023-10-30 14:29           ` Denis Kenzior
2023-10-17 10:49 ` [PATCH 15/15] ppp: message tracing MaxLyubimov
2023-10-19  2:22   ` Denis Kenzior
2023-10-27 10:01     ` Любимов Максим
2023-10-29 21:05       ` Denis Kenzior
2023-10-30  6:34         ` Любимов Максим
2023-10-30 14:30           ` Denis Kenzior
2023-10-19  1:28 ` [PATCH 01/15] Skipping AT+CUAD sending for QUECTEL_EC2X vendor Denis Kenzior

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=d78baea0-813c-414d-bf8d-d9a06fbdb5fa@gmail.com \
    --to=denkenz@gmail.com \
    --cc=m.lyubimov@aqsi.ru \
    --cc=ofono@lists.linux.dev \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox