From: kernel test robot <lkp@intel.com>
To: cros-kernel-buildreports@googlegroups.com
Cc: oe-kbuild-all@lists.linux.dev
Subject: [android-common:android13-5.10 4980/30000] drivers/usb/host/xhci-ring.c:2900:5: warning: no previous prototype for 'xhci_handle_event'
Date: Mon, 6 Nov 2023 04:45:20 +0800 [thread overview]
Message-ID: <202311060408.2WEgiDs9-lkp@intel.com> (raw)
Hi Howard,
FYI, the error/warning still remains.
tree: https://android.googlesource.com/kernel/common android13-5.10
head: 2fea3eca9608d8c14fb6963bfe830dfa5985d7de
commit: 26afe6712de0fad3a5de2b372286d029f8ff3231 [4980/30000] FROMLIST: usb: host: export symbols for xhci hooks usage
config: x86_64-rhel-8.3 (https://download.01.org/0day-ci/archive/20231106/202311060408.2WEgiDs9-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231106/202311060408.2WEgiDs9-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202311060408.2WEgiDs9-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/usb/host/xhci-ring.c:2900:5: warning: no previous prototype for 'xhci_handle_event' [-Wmissing-prototypes]
2900 | int xhci_handle_event(struct xhci_hcd *xhci)
| ^~~~~~~~~~~~~~~~~
drivers/usb/host/xhci-ring.c:2976:6: warning: no previous prototype for 'xhci_update_erst_dequeue' [-Wmissing-prototypes]
2976 | void xhci_update_erst_dequeue(struct xhci_hcd *xhci,
| ^~~~~~~~~~~~~~~~~~~~~~~~
vim +/xhci_handle_event +2900 drivers/usb/host/xhci-ring.c
2893
2894 /*
2895 * This function handles all OS-owned events on the event ring. It may drop
2896 * xhci->lock between event processing (e.g. to pass up port status changes).
2897 * Returns >0 for "possibly more events to process" (caller should call again),
2898 * otherwise 0 if done. In future, <0 returns should indicate error code.
2899 */
> 2900 int xhci_handle_event(struct xhci_hcd *xhci)
2901 {
2902 union xhci_trb *event;
2903 int update_ptrs = 1;
2904 u32 trb_type;
2905 int ret;
2906
2907 /* Event ring hasn't been allocated yet. */
2908 if (!xhci->event_ring || !xhci->event_ring->dequeue) {
2909 xhci_err(xhci, "ERROR event ring not ready\n");
2910 return -ENOMEM;
2911 }
2912
2913 event = xhci->event_ring->dequeue;
2914 /* Does the HC or OS own the TRB? */
2915 if ((le32_to_cpu(event->event_cmd.flags) & TRB_CYCLE) !=
2916 xhci->event_ring->cycle_state)
2917 return 0;
2918
2919 trace_xhci_handle_event(xhci->event_ring, &event->generic);
2920
2921 /*
2922 * Barrier between reading the TRB_CYCLE (valid) flag above and any
2923 * speculative reads of the event's flags/data below.
2924 */
2925 rmb();
2926 trb_type = TRB_FIELD_TO_TYPE(le32_to_cpu(event->event_cmd.flags));
2927 /* FIXME: Handle more event types. */
2928
2929 switch (trb_type) {
2930 case TRB_COMPLETION:
2931 handle_cmd_completion(xhci, &event->event_cmd);
2932 break;
2933 case TRB_PORT_STATUS:
2934 handle_port_status(xhci, event);
2935 update_ptrs = 0;
2936 break;
2937 case TRB_TRANSFER:
2938 ret = handle_tx_event(xhci, &event->trans_event);
2939 if (ret >= 0)
2940 update_ptrs = 0;
2941 break;
2942 case TRB_DEV_NOTE:
2943 handle_device_notification(xhci, event);
2944 break;
2945 default:
2946 if (trb_type >= TRB_VENDOR_DEFINED_LOW)
2947 handle_vendor_event(xhci, event, trb_type);
2948 else
2949 xhci_warn(xhci, "ERROR unknown event type %d\n", trb_type);
2950 }
2951 /* Any of the above functions may drop and re-acquire the lock, so check
2952 * to make sure a watchdog timer didn't mark the host as non-responsive.
2953 */
2954 if (xhci->xhc_state & XHCI_STATE_DYING) {
2955 xhci_dbg(xhci, "xHCI host dying, returning from "
2956 "event handler.\n");
2957 return 0;
2958 }
2959
2960 if (update_ptrs)
2961 /* Update SW event ring dequeue pointer */
2962 inc_deq(xhci, xhci->event_ring);
2963
2964 /* Are there more items on the event ring? Caller will call us again to
2965 * check.
2966 */
2967 return 1;
2968 }
2969 EXPORT_SYMBOL_GPL(xhci_handle_event);
2970
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2023-11-05 20:46 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=202311060408.2WEgiDs9-lkp@intel.com \
--to=lkp@intel.com \
--cc=cros-kernel-buildreports@googlegroups.com \
--cc=oe-kbuild-all@lists.linux.dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.