Kconfig 2.4 KB

1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859
  1. # Copyright (C) 2018 RDA Technologies Limited and/or its affiliates("RDA").
  2. # All rights reserved.
  3. #
  4. # This software is supplied "AS IS" without any warranties.
  5. # RDA assumes no responsibility or liability for the use of the software,
  6. # conveys no license or title under any patent, copyright, or mask work
  7. # right to the product. RDA reserves the right to make changes in the
  8. # software without notification. RDA also make no representation or
  9. # warranty that such application will be suitable for the specified use
  10. # without further testing or modification.
  11. menu "AP/CP RPC"
  12. config RPC_SEND_STACK_ALLOCA_LIMIT
  13. int "Size limit to use stack (alloca) on send"
  14. default 256
  15. help
  16. RPC send can be called in multiple threads. When one thread
  17. is wating response from peer, it is permitted to let another
  18. thread to send call packet to peer when one thread. In normal
  19. case, there are no differences due to there is only one
  20. thread in peer, and all requests are handled one by one.
  21. However, when peer is busy, it is possible there may exist
  22. differences, and async message can be faster. So, we can't
  23. use global memory for input and output parameters.
  24. When input and output parameter memory size is small, alloca
  25. will be used, and malloc/free can be saved. When memory size
  26. is large, malloc/free shall be used to avoid stack overflow.
  27. Anyway, malloc/free can be non-trivial operation.
  28. config RPC_PACKET_SIZE_MAX
  29. int "RPC packet max size"
  30. default 1024
  31. help
  32. The maximum of RPC packet size, including RPC call packet, RPC
  33. response packet and RPC async message packet.
  34. config RPC_EVENT_RANGE_COUNT
  35. int "RPC event range count"
  36. default 4
  37. help
  38. When RPC daemon received an event from peer, RPC daemon itself
  39. donesn't know how to do with the event. Application shoule
  40. register router for specified events, usually send the event
  41. to desired thread.
  42. It is tedious to use dynamic memory for the registration. So,
  43. static memory is used, and this configures the maximum count.
  44. config RPC_DEBUG_NOT_SEND
  45. bool "not send to peer for all RPC"
  46. default n
  47. help
  48. This is for debug only. When enabled, all RPC packet won't be sent
  49. to peer. This may be used in platform early debug if peer is not
  50. ready.
  51. endmenu