780-v5.11-net-usb-r8152-Provide-missing-documentation-for-some.patch 3.7 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172
  1. From 586f04ce6a391419ca3cc9cef6b6f38570cede88 Mon Sep 17 00:00:00 2001
  2. From: Lee Jones <[email protected]>
  3. Date: Mon, 2 Nov 2020 11:45:04 +0000
  4. Subject: [PATCH] net: usb: r8152: Provide missing documentation for
  5. some struct members
  6. commit 34e653efb602e0651867fb5ab14369b555a61dcd upstream.
  7. Fixes the following W=1 kernel build warning(s):
  8. drivers/net/usb/r8152.c:934: warning: Function parameter or member 'blk_hdr' not described in 'fw_mac'
  9. drivers/net/usb/r8152.c:934: warning: Function parameter or member 'reserved' not described in 'fw_mac'
  10. drivers/net/usb/r8152.c:947: warning: Function parameter or member 'blk_hdr' not described in 'fw_phy_patch_key'
  11. drivers/net/usb/r8152.c:947: warning: Function parameter or member 'reserved' not described in 'fw_phy_patch_key'
  12. drivers/net/usb/r8152.c:986: warning: Function parameter or member 'blk_hdr' not described in 'fw_phy_nc'
  13. drivers/net/usb/r8152.c:986: warning: Function parameter or member 'mode_pre' not described in 'fw_phy_nc'
  14. drivers/net/usb/r8152.c:986: warning: Function parameter or member 'mode_post' not described in 'fw_phy_nc'
  15. drivers/net/usb/r8152.c:986: warning: Function parameter or member 'reserved' not described in 'fw_phy_nc'
  16. Signed-off-by: Lee Jones <[email protected]>
  17. Acked-by: Hayes Wang <[email protected]>
  18. Link: https://lore.kernel.org/r/[email protected]
  19. Signed-off-by: Jakub Kicinski <[email protected]>
  20. ---
  21. drivers/net/usb/r8152.c | 6 ++++++
  22. 1 file changed, 6 insertions(+)
  23. --- a/drivers/net/usb/r8152.c
  24. +++ b/drivers/net/usb/r8152.c
  25. @@ -898,6 +898,7 @@ struct fw_header {
  26. * struct fw_mac - a firmware block used by RTL_FW_PLA and RTL_FW_USB.
  27. * The layout of the firmware block is:
  28. * <struct fw_mac> + <info> + <firmware data>.
  29. + * @blk_hdr: firmware descriptor (type, length)
  30. * @fw_offset: offset of the firmware binary data. The start address of
  31. * the data would be the address of struct fw_mac + @fw_offset.
  32. * @fw_reg: the register to load the firmware. Depends on chip.
  33. @@ -911,6 +912,7 @@ struct fw_header {
  34. * @bp_num: the break point number which needs to be set for this firmware.
  35. * Depends on the firmware.
  36. * @bp: break points. Depends on firmware.
  37. + * @reserved: reserved space (unused)
  38. * @fw_ver_reg: the register to store the fw version.
  39. * @fw_ver_data: the firmware version of the current type.
  40. * @info: additional information for debugging, and is followed by the
  41. @@ -936,8 +938,10 @@ struct fw_mac {
  42. /**
  43. * struct fw_phy_patch_key - a firmware block used by RTL_FW_PHY_START.
  44. * This is used to set patch key when loading the firmware of PHY.
  45. + * @blk_hdr: firmware descriptor (type, length)
  46. * @key_reg: the register to write the patch key.
  47. * @key_data: patch key.
  48. + * @reserved: reserved space (unused)
  49. */
  50. struct fw_phy_patch_key {
  51. struct fw_block blk_hdr;
  52. @@ -950,6 +954,7 @@ struct fw_phy_patch_key {
  53. * struct fw_phy_nc - a firmware block used by RTL_FW_PHY_NC.
  54. * The layout of the firmware block is:
  55. * <struct fw_phy_nc> + <info> + <firmware data>.
  56. + * @blk_hdr: firmware descriptor (type, length)
  57. * @fw_offset: offset of the firmware binary data. The start address of
  58. * the data would be the address of struct fw_phy_nc + @fw_offset.
  59. * @fw_reg: the register to load the firmware. Depends on chip.
  60. @@ -960,6 +965,7 @@ struct fw_phy_patch_key {
  61. * @mode_reg: the regitster of switching the mode.
  62. * @mod_pre: the mode needing to be set before loading the firmware.
  63. * @mod_post: the mode to be set when finishing to load the firmware.
  64. + * @reserved: reserved space (unused)
  65. * @bp_start: the start register of break points. Depends on chip.
  66. * @bp_num: the break point number which needs to be set for this firmware.
  67. * Depends on the firmware.