Wireless Daemon for Linux
 help / color / mirror / Atom feed
From: Denis Kenzior <denkenz at gmail.com>
To: iwd at lists.01.org
Subject: Re: [PATCH 2/2] Document initial signal level notification
Date: Fri, 20 May 2022 15:13:06 -0500	[thread overview]
Message-ID: <b59a8875-ec79-e863-3369-9f0fbcf21621@gmail.com> (raw)
In-Reply-To: 20220520185948.9533-2-jesse@twosheds.org

[-- Attachment #1: Type: text/plain, Size: 2248 bytes --]

Hi Jesse,

On 5/20/22 13:59, Jesse Lentz wrote:
> Document the initial "Changed" method call following SignalLevelAgent
> registration.
> ---
>   doc/station-api.txt | 27 ++++++++++++++-------------
>   1 file changed, 14 insertions(+), 13 deletions(-)
> 
> diff --git a/doc/station-api.txt b/doc/station-api.txt
> index 0bb372ab..05dd137e 100644
> --- a/doc/station-api.txt
> +++ b/doc/station-api.txt
> @@ -182,16 +182,17 @@ Methods		void Release(object device) [noreply]
>   		void Changed(object device, uint8 level) [noreply]
>   
>   			This method gets called when the signal strength
> -			measurement for the device's connected network
> -			changes enough to go from one level to another out
> -			of the N ranges defined by the array of (N-1)
> -			threshold values passed to RegisterSignalLevelAgent().
> -			The level parameter is in the range from 0 to N,
> -			0 being the strongest signal or above the first
> -			threshold value in the array, and N being the
> -			weakest and below the last threshold value.  For
> -			example if RegisterSignalLevelAgent was called with
> -			the array [-40, -50, -60], the 'level' parameter of
> -			0 would mean signal is received at -40 or more dBm
> -			and 3 would mean below -60 dBm and might correspond
> -			to 1 out of 4 bars on a UI signal meter.
> +			measurement for the device's connected network changes
> +			enough to go from one level to another out of the N
> +			ranges defined by the array of (N-1) threshold values
> +			passed to RegisterSignalLevelAgent().  It also gets
> +			called immediately after the signal level agent is
> +			registered.  The level parameter is in the range from 0
> +			to N, 0 being the strongest signal or above the first
> +			threshold value in the array, and N being the weakest
> +			and below the last threshold value.  For example if
> +			RegisterSignalLevelAgent was called with the array [-40,

I think this line might be over 80 chars.

> +			-50, -60], the 'level' parameter of 0 would mean signal
> +			is received at -40 or more dBm and 3 would mean below
> +			-60 dBm and might correspond to 1 out of 4 bars on a UI
> +			signal meter.
> 

Otherwise looks good!

Regards,
-Denis

             reply	other threads:[~2022-05-20 20:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-20 20:13 Denis Kenzior [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-05-20 21:53 [PATCH 2/2] Document initial signal level notification Jesse Lentz
2022-05-20 21:14 Denis Kenzior
2022-05-20 20:54 Jesse Lentz
2022-05-20 18:59 Jesse Lentz

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=b59a8875-ec79-e863-3369-9f0fbcf21621@gmail.com \
    --to=iwd@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