Hi Andrei,
> From: Andrei Emeltchenko <andrei.emeltchenko@xxxxxxxxx>
>
> Removes logically dead code since conditions were already checked in the
> previous statements.
this should be two patches.
> ---
> emulator/le.c | 11 ++---------
> 1 file changed, 2 insertions(+), 9 deletions(-)
>
> diff --git a/emulator/le.c b/emulator/le.c
> index 30daa63..91cf31c 100644
> --- a/emulator/le.c
> +++ b/emulator/le.c
> @@ -1236,21 +1236,14 @@ static void cmd_le_set_data_length(struct bt_le *hci,
> }
>
> /* Valid range for suggested max TX octets is 0x001b to 0x00fb */
> - if (tx_len < 0x001b || tx_len > 0x00fb) {
> + if (tx_len < DEFAULT_TX_LEN || tx_len > MAX_TX_LEN) {
MAX_TX_LEN is our max value. It just happens to be the same max for the parameter. So I would keep the magic numbers here unless we introduce official constants for default, min, max ranges somewhere else.
> cmd_status(hci, BT_HCI_ERR_INVALID_PARAMETERS,
> BT_HCI_CMD_LE_SET_DATA_LENGTH);
> return;
> }
>
> /* Valid range for suggested max TX time is 0x0148 to 0x0848 */
> - if (tx_time < 0x0148 || tx_time > 0x0848) {
> - cmd_status(hci, BT_HCI_ERR_INVALID_PARAMETERS,
> - BT_HCI_CMD_LE_SET_DATA_LENGTH);
> - return;
> - }
> -
> - /* Max TX len and time shall be less or equal supported */
And this check is just by accident the same as the other one before. The one before is checking the max allowed values from the specification.
This one is checking our max values. It just happens to be the same. Since this is an emulator and not real code that is heavy optimized, we should instead have hci->le_max_tx_time and hci->le_max_tx_len and assigned to our max value and then check against that.
We do exactly the same for white list size and resolving list size.
> - if (tx_len > MAX_TX_LEN || tx_time > MAX_TX_TIME) {
> + if (tx_time < DEFAULT_TX_TIME || tx_time > MAX_TX_TIME) {
> cmd_status(hci, BT_HCI_ERR_INVALID_PARAMETERS,
> BT_HCI_CMD_LE_SET_DATA_LENGTH);
> return;
Regards
Marcel
--
To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
