kw2xrf: set tx_power in gnrc_netdev_t#5834
Conversation
|
Please specify in the commit message which driver you are talking about ;-) |
|
(and in the PR title) |
|
the same is missing for the at86rf driver |
|
@cgundogan but there the option getter gets the option directly from the device. |
|
@miri64 but AFAIK this is what should not happen. Isn't the |
|
There are no rules to that. I would argue, if the connection to the device is fast enough its worth saving the RAM to get the value directly from the device. |
|
(also the |
|
AFAIR the incentive was to reduce the register access, which is basically an SPI access |
|
needs some modifications in |
|
These changes should also be noted for #5469. |
|
I added checks to verify that the tx_power passed by e.g. Regarding the discussion whether to cache values in |
|
and again: verified by live testing on hardware (Edit): works! |
|
@jfischer-phytec-iot could you tests this one and adapt changes into #5469? |
|
PING! (Edit) I'll squash in the meantime and let Murdock go over it |
without this patch, tx_power is directly set on the device but not in gnrc_netdev_t. Thus, calling ifconfig in shell shows tx_power always at 0dBm, never showing the correct, current value. Additionally, it verifies that given tx_power to be set is in valid range.
1e0cc18 to
fc9e1d9
Compare
|
juhu, Murdock says okay--no weird, unrelated errors anymore--finally! |
|
Murdock is happy, but after @OlegHahm enabled this review feature this requires an approved review. @jfischer-phytec-iot seems to be on vacation, anybody else ( @miri64, @cgundogan, @jremmert-phytec-iot ) willing to look over this? So we can move on ... |
|
There wasn't any ACK, right? So even with the old system this wouldn't have been mergeable ;-) |
|
@miri64 I hoped @jfischer-phytec-iot would ACK, but no response so far. |
|
sorry, I am all the time busy with work and the usb stack, also I got no notifications from the github 😠 |
without this patch, tx_power is directly set on the device but not in
gnrc_netdev_t. Thus, calling ifconfig in shell shows tx_power always
at 0dBm, never showing the correct, current value.
Btw. verified by testing, 5 min ago 😄