From: Greg KH <gregkh@linuxfoundation.org>
To: Paulo Miguel Almeida <paulo.miguel.almeida.rodenas@gmail.com>
Cc: realwakka@gmail.com, linux-staging@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: pi433: fix frequency deviation check
Date: Mon, 3 Jan 2022 14:27:10 +0100 [thread overview]
Message-ID: <YdL5rtWw2PTXdsRM@kroah.com> (raw)
In-Reply-To: <20220103081135.GA11642@mail.google.com>
On Mon, Jan 03, 2022 at 09:11:35PM +1300, Paulo Miguel Almeida wrote:
> rf69 datasheet states that frequency deviation must exceed 600 Hz but
> also that frequency deviation + (bitrate / 2) should be less than equal
> to 500 kHz to ensure proper modulation.
>
> This patch validates that both conditions are met so RF intersymbol
> interference is "avoided" where possible.
>
> Signed-off-by: Paulo Miguel Almeida <paulo.miguel.almeida.rodenas@gmail.com>
> ---
> drivers/staging/pi433/rf69.c | 20 ++++++++++++++++----
> 1 file changed, 16 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/staging/pi433/rf69.c b/drivers/staging/pi433/rf69.c
> index e62e61ef4d27..cc22915fd489 100644
> --- a/drivers/staging/pi433/rf69.c
> +++ b/drivers/staging/pi433/rf69.c
> @@ -255,17 +255,29 @@ int rf69_set_deviation(struct spi_device *spi, u32 deviation)
> int retval;
> u64 f_reg;
> u64 f_step;
> + u32 bit_rate_reg;
> + u32 bit_rate;
> u8 msb;
> u8 lsb;
> u64 factor = 1000000; // to improve precision of calculation
>
> - // TODO: Dependency to bitrate
> - if (deviation < 600 || deviation > 500000) {
> - dev_dbg(&spi->dev, "set_deviation: illegal input param");
> + // calculate bit rate
> + bit_rate_reg = rf69_read_reg(spi, REG_BITRATE_MSB) << 8;
> + bit_rate_reg |= rf69_read_reg(spi, REG_BITRATE_LSB);
> + bit_rate = F_OSC / bit_rate_reg;
> +
> + /*
> + * frequency deviation must exceed 600 Hz and but not exceed
> + * 500kHz when taking bitrate dependency into consideration
> + * to ensure proper modulation
> + */
> + if (deviation < 600 || (deviation + (bit_rate / 2)) > 500000) {
> + dev_dbg(&spi->dev,
> + "set_deviation: illegal input param: %u", deviation);
> return -EINVAL;
> }
>
> - // calculat f step
> + // calculate f step
This change should be a separate patch.
thanks,
greg k-h
next prev parent reply other threads:[~2022-01-03 13:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-03 8:11 [PATCH] staging: pi433: fix frequency deviation check Paulo Miguel Almeida
2022-01-03 10:00 ` Fabio Aiuto
2022-01-03 13:27 ` Greg KH [this message]
2022-01-03 22:23 ` [PATCH v2] " Paulo Miguel Almeida
2022-01-03 22:28 ` [PATCH] " Paulo Miguel Almeida
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=YdL5rtWw2PTXdsRM@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=paulo.miguel.almeida.rodenas@gmail.com \
--cc=realwakka@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).