linguini1 commented on issue #15856: URL: https://github.com/apache/nuttx/issues/15856#issuecomment-2726702267
> If the user only cares about normal precision, it creates a cleaner code. > and yes it is possible to add the extra precision one. However i dont see the use? Can be done at a later stage if there is demand. I have demand for it. I understand the argument that fractional dBm may be unimportant because of path loss fluctuations, but there is an alternative reason why it would matter: current draw. My application is a low power one and I would like full control over the current draw from transmitting. > I understand your issue where two fractionals round to the same number. But is it possible to select either one anyway? Flooring or c eiling all numbers, not round. Flooring 2.1 and 2.4 will both yield 2. Ceil will yield 3. Round will yield 2. > In case that even that cant work, you might have to pick ones yourself. Maybe, but I think all drivers should behave consistently. Is it always picking the closest level? Always flooring? Always ceiling? I think that the transmit power that is set should be greater or equal to the number the user requests to avoid surprises. I understand wanting to make things appear cleaner or avoiding breaking legacy commands but I think this would be an unnecessary limitation. I have this use case now and I'm sure others will too. Adding it later will just require more modifications. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@nuttx.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
