[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220118230312.GA4826@mail.google.com>
Date: Wed, 19 Jan 2022 12:03:12 +1300
From: Paulo Miguel Almeida <paulo.miguel.almeida.rodenas@...il.com>
To: gregkh@...uxfoundation.org, paulo.miguel.almeida.rodenas@...il.com,
realwakka@...il.com
Cc: linux-staging@...ts.linux.dev, linux-kernel@...r.kernel.org
Subject: [PATCH v3 0/3] staging: pi433: validate min/max bit rate settings
RF69 chip supports different bit rate settings depending on which frequency
modulation is used. Failing to correctly validate bit rate can lead to a
silent failure and cause packets not to be read/sent.
This series change the order in which the rf69 chip is configured and add
max bit rate validation.
Patch dependency:
This series depend on these patches as they change the same set of files:
- https://lore.kernel.org/lkml/20220108212728.GA7784@mail.google.com/
- https://lore.kernel.org/lkml/20220114221643.GA7843@mail.google.com/
Changelog:
v3: revert bitrate variable data type change. Req: Dan Carpenter
v2: change bitrate variable type to u32 as pointed by kernel test bot
v1: https://lore.kernel.org/lkml/20220116001726.GA22699@mail.google.com/
Paulo Miguel Almeida (3):
staging: pi433: fix validation for min bit rate supported by the
device
staging: pi433: change order in which driver config the rf69 chip
staging: pi433: validate max bit_rate based on modulation used
drivers/staging/pi433/TODO | 2 ++
drivers/staging/pi433/pi433_if.c | 8 ++++----
drivers/staging/pi433/rf69.c | 12 +++++++++---
3 files changed, 15 insertions(+), 7 deletions(-)
--
2.25.4
Powered by blists - more mailing lists