From: Aman Sharma <210100011@iitb.ac.in>
To: Gregkh <gregkh@linuxfoundation.org>
Cc: linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: [PATCH v4] Staging: pi433: Updated bitrate range from datasheet
Date: Mon, 04 Mar 2024 15:56:09 +0530 [thread overview]
Message-ID: <34c89fc61663a5ecf3d83edebefc6b00@iitb.ac.in> (raw)
Updated bitrate range for FSK and OOK modulation from the RFM69
Datasheet.
The values are mentioned in Section 2.3.2 of the datasheet.
Signed-off-by: Aman Sharma <amansharma6122002@gmail.com>
---
V1->V2: Added explanation about values in commit msg
V2->V3: Added version comments after changelog
V3->V4: Corrected the Signed-off-by line
drivers/staging/pi433/Documentation/pi433.txt | 6 ++++--
drivers/staging/pi433/TODO | 1 -
2 files changed, 4 insertions(+), 3 deletions(-)
diff --git a/drivers/staging/pi433/Documentation/pi433.txt
b/drivers/staging/pi433/Documentation/pi433.txt
index 4a0d34b4ad37..9ce7282ef6f8 100644
--- a/drivers/staging/pi433/Documentation/pi433.txt
+++ b/drivers/staging/pi433/Documentation/pi433.txt
@@ -78,7 +78,8 @@ rf params:
Allowed values: 433050000...434790000
bit_rate
bit rate used for transmission.
- Allowed values: #####
+ Allowed values (For FSK): 1200...320000
+ Allowed values (For OOK): 1200...32768
dev_frequency
frequency deviation in case of FSK.
Allowed values: 600...500000
@@ -169,7 +170,8 @@ rf params:
Allowed values: 433050000...434790000
bit_rate
bit rate used for transmission.
- Allowed values: #####
+ Allowed values (For FSK): 1200...320000
+ Allowed values (For OOK): 1200...32768
dev_frequency
frequency deviation in case of FSK.
Allowed values: 600...500000
diff --git a/drivers/staging/pi433/TODO b/drivers/staging/pi433/TODO
index 63a40bfcc67e..61ed3a1578bc 100644
--- a/drivers/staging/pi433/TODO
+++ b/drivers/staging/pi433/TODO
@@ -2,4 +2,3 @@
* still TODOs, annotated in the code
* currently the code introduces new IOCTLs. I'm afraid this is a bad
idea.
-> Replace this with another interface, hints are welcome!
-* Some missing data (marked with ###) needs to be added in the
documentation
--
2.34.1
next reply other threads:[~2024-03-04 10:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-04 10:26 Aman Sharma [this message]
2024-03-05 14:12 ` [PATCH v4] Staging: pi433: Updated bitrate range from datasheet Gregkh
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=34c89fc61663a5ecf3d83edebefc6b00@iitb.ac.in \
--to=210100011@iitb.ac.in \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@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