From: Hugo Lefeuvre <hle@owl.eu.com>
To: Marcus Wolf <linux@wolf-entwicklungen.de>
Cc: Valentin Vidic <Valentin.Vidic@CARNet.hr>,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
hle@owl.eu.com
Subject: rf69_set_deviation in rf69.c (pi433 driver)
Date: Mon, 4 Jun 2018 23:11:20 -0400 [thread overview]
Message-ID: <20180605031120.GB1981@hle-laptop.local> (raw)
[-- Attachment #1: Type: text/plain, Size: 1647 bytes --]
Hi Marcus,
I have been taking a look at the pi433 driver these last days, and started
working on the remaining TODOs. I just stumbled across the following
one (drivers/staging/pi433/rf69.c):
245 // TODO: Dependency to bitrate
246 if (deviation < 600 || deviation > 500000) {
247 dev_dbg(&spi->dev, "set_deviation: illegal input param");
248 return -EINVAL;
249 }
According to the datasheet[0], the deviation should always be smaller
than 300kHz, and the following equation should be respected:
(1) FDA + BRF/2 =< 500 kHz
Why did you choose 500kHz as max for FDA, instead of 300kHz ? It looks like
a bug to me.
Concerning the TODO, I can see two solutions currently:
1. Introduce a new rf69_get_bit_rate function which reads REG_BITRATE_MSB
and REG_BITRATE_LSB and returns reconstructed BRF.
We could use this function in rf69_set_deviation to retrieve the BRF.
+ clean
+ intuitive
- heavy / slow
2. Store BRF somewhere in rf69.c, initialize it with the default value
(4.8 kb/s) and update it when rf69_set_bit_rate is called.
+ easy
- dirty, doesn't fit well with the design of rf69.c (do not store
anything, simply expose API)
I'd really prefer going for the first one, but I wanted to have your opinion
on this.
Thanks for your work !
Best regards,
Hugo
[0] http://www.hoperf.com/upload/rf/RFM69CW-V1.1.pdf
[CC-ing Valentin Vidic, he was quite active on the pi433 driver these
last months]
--
Hugo Lefeuvre (hle) | www.owl.eu.com
4096/ 9C4F C8BF A4B0 8FC5 48EB 56B8 1962 765B B9A8 BACA
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2018-06-05 3:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-05 3:11 Hugo Lefeuvre [this message]
2018-06-19 10:19 ` Marcus Wolf
2018-06-22 2:03 ` Hugo Lefeuvre
2018-06-22 8:46 ` Valentin Vidic
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=20180605031120.GB1981@hle-laptop.local \
--to=hle@owl.eu.com \
--cc=Valentin.Vidic@CARNet.hr \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@wolf-entwicklungen.de \
/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
all inboxes | Powered by JetHome®