From: Paulo Miguel Almeida <paulo.miguel.almeida.rodenas@gmail.com>
To: gregkh@linuxfoundation.org,
paulo.miguel.almeida.rodenas@gmail.com, realwakka@gmail.com
Cc: linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: [PATCH 1/2] staging: pi433: add missing register contants
Date: Sun, 23 Jan 2022 20:39:55 +1300 [thread overview]
Message-ID: <20220123073955.GA79659@mail.google.com> (raw)
In-Reply-To: <20220123073855.GA79453@mail.google.com>
add missing register constants present in RFM69 and/or RFM69HW so that
we don't need to hardcode values when referencing them.
this patch adds REG_TESTLNA, REG_TESTAFC constants
Signed-off-by: Paulo Miguel Almeida <paulo.miguel.almeida.rodenas@gmail.com>
---
drivers/staging/pi433/rf69_registers.h | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/staging/pi433/rf69_registers.h b/drivers/staging/pi433/rf69_registers.h
index a170c66c3d5b..0d6737738841 100644
--- a/drivers/staging/pi433/rf69_registers.h
+++ b/drivers/staging/pi433/rf69_registers.h
@@ -89,9 +89,11 @@
#define REG_AESKEY16 0x4D
#define REG_TEMP1 0x4E
#define REG_TEMP2 0x4F
+#define REG_TESTLNA 0x58
#define REG_TESTPA1 0x5A /* only present on RFM69HW */
#define REG_TESTPA2 0x5C /* only present on RFM69HW */
#define REG_TESTDAGC 0x6F
+#define REG_TESTAFC 0x71
/******************************************************/
/* RF69/SX1231 bit definition */
--
2.25.4
next prev parent reply other threads:[~2022-01-23 7:40 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-23 7:38 [PATCH 0/2] staging: pi433: add debugfs interface Paulo Miguel Almeida
2022-01-23 7:39 ` Paulo Miguel Almeida [this message]
2022-01-23 7:40 ` [PATCH 2/2] " Paulo Miguel Almeida
2022-01-23 11:20 ` Greg KH
2022-01-24 4:14 ` Paulo Miguel Almeida
2022-01-24 4:25 ` [PATCH v2 0/2] " Paulo Miguel Almeida
2022-01-24 4:26 ` [PATCH v2 1/2] staging: pi433: add missing register contants Paulo Miguel Almeida
2022-01-24 4:27 ` [PATCH v2 2/2] staging: pi433: add debugfs interface Paulo Miguel Almeida
2022-01-26 12:03 ` Greg KH
2022-01-29 3:35 ` Paulo Miguel Almeida
2022-01-26 13:21 ` Dan Carpenter
2022-01-29 3:30 ` Paulo Miguel Almeida
2022-01-30 2:57 ` [PATCH v3] " Paulo Miguel Almeida
2022-01-31 13:45 ` Dan Carpenter
2022-01-31 16:45 ` Greg KH
2022-01-31 19:37 ` Paulo Miguel Almeida
2022-02-04 5:06 ` [PATCH v4] " Paulo Miguel Almeida
2022-02-04 8:04 ` [PATCH v5] " Paulo Miguel Almeida
2022-02-04 9:02 ` Dan Carpenter
2022-02-04 8:55 ` [PATCH v4] " Dan Carpenter
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=20220123073955.GA79659@mail.google.com \
--to=paulo.miguel.almeida.rodenas@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--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).