devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: "Roy Luo" <royluo@google.com>, "Vinod Koul" <vkoul@kernel.org>,
	"Kishon Vijay Abraham I" <kishon@kernel.org>,
	"Rob Herring" <robh@kernel.org>,
	"Krzysztof Kozlowski" <krzk@kernel.org>,
	"Conor Dooley" <conor+dt@kernel.org>,
	"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
	"Thinh Nguyen" <Thinh.Nguyen@synopsys.com>,
	"Philipp Zabel" <p.zabel@pengutronix.de>,
	"Peter Griffin" <peter.griffin@linaro.org>,
	"André Draszik" <andre.draszik@linaro.org>,
	"Tudor Ambarus" <tudor.ambarus@linaro.org>
Cc: oe-kbuild-all@lists.linux.dev,
	Joy Chakraborty <joychakr@google.com>,
	Naveen Kumar <mnkumar@google.com>, Roy Luo <royluo@google.com>,
	linux-phy@lists.infradead.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-samsung-soc@vger.kernel.org
Subject: Re: [PATCH v1 1/4] usb: dwc3: Add Google SoC DWC3 glue driver
Date: Sat, 11 Oct 2025 11:39:41 +0800	[thread overview]
Message-ID: <202510111335.oyOAs9MB-lkp@intel.com> (raw)
In-Reply-To: <20251006232125.1833979-2-royluo@google.com>

Hi Roy,

kernel test robot noticed the following build warnings:

[auto build test WARNING on e5f0a698b34ed76002dc5cff3804a61c80233a7a]

url:    https://github.com/intel-lab-lkp/linux/commits/Roy-Luo/usb-dwc3-Add-Google-SoC-DWC3-glue-driver/20251010-092651
base:   e5f0a698b34ed76002dc5cff3804a61c80233a7a
patch link:    https://lore.kernel.org/r/20251006232125.1833979-2-royluo%40google.com
patch subject: [PATCH v1 1/4] usb: dwc3: Add Google SoC DWC3 glue driver
config: s390-randconfig-002-20251011 (https://download.01.org/0day-ci/archive/20251011/202510111335.oyOAs9MB-lkp@intel.com/config)
compiler: s390-linux-gcc (GCC) 15.1.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251011/202510111335.oyOAs9MB-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/202510111335.oyOAs9MB-lkp@intel.com/

All warnings (new ones prefixed by >>):

>> drivers/usb/dwc3/dwc3-google.c:467:12: warning: 'dwc3_google_resume' defined but not used [-Wunused-function]
     467 | static int dwc3_google_resume(struct dwc3_google *google, pm_message_t msg)
         |            ^~~~~~~~~~~~~~~~~~
>> drivers/usb/dwc3/dwc3-google.c:441:12: warning: 'dwc3_google_suspend' defined but not used [-Wunused-function]
     441 | static int dwc3_google_suspend(struct dwc3_google *google, pm_message_t msg)
         |            ^~~~~~~~~~~~~~~~~~~


vim +/dwc3_google_resume +467 drivers/usb/dwc3/dwc3-google.c

   440	
 > 441	static int dwc3_google_suspend(struct dwc3_google *google, pm_message_t msg)
   442	{
   443		if (pm_runtime_suspended(google->dev))
   444			return 0;
   445	
   446		if (google->dwc.current_dr_role == DWC3_GCTL_PRTCAP_HOST) {
   447			/*
   448			 * Follow dwc3_suspend_common() guidelines for deciding between
   449			 * a full teardown and hibernation.
   450			 */
   451			if (PMSG_IS_AUTO(msg) || device_may_wakeup(google->dev)) {
   452				dev_dbg(google->dev, "enter hibernation");
   453				pm_runtime_get_sync(google->usb_top_pd);
   454				device_wakeup_enable(google->usb_top_pd);
   455				dwc3_google_enable_pme_irq(google);
   456				google->is_hibernation = true;
   457				return 0;
   458			}
   459		}
   460	
   461		reset_control_bulk_assert(google->num_rsts, google->rsts);
   462		clk_bulk_disable_unprepare(google->num_clks, google->clks);
   463	
   464		return 0;
   465	}
   466	
 > 467	static int dwc3_google_resume(struct dwc3_google *google, pm_message_t msg)
   468	{
   469		int ret;
   470	
   471		if (google->is_hibernation) {
   472			dev_dbg(google->dev, "exit hibernation");
   473			dwc3_google_disable_pme_irq(google);
   474			device_wakeup_disable(google->usb_top_pd);
   475			pm_runtime_put_sync(google->usb_top_pd);
   476			google->is_hibernation = false;
   477			return 0;
   478		}
   479	
   480		ret = clk_bulk_prepare_enable(google->num_clks, google->clks);
   481		if (ret)
   482			return ret;
   483	
   484		ret = reset_control_bulk_deassert(google->num_rsts, google->rsts);
   485		if (ret) {
   486			clk_bulk_disable_unprepare(google->num_clks, google->clks);
   487			return ret;
   488		}
   489	
   490		return 0;
   491	}
   492	

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

  parent reply	other threads:[~2025-10-11  3:40 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-06 23:21 [PATCH v1 0/4] Add Google Tensor SoC USB support Roy Luo
2025-10-06 23:21 ` [PATCH v1 1/4] usb: dwc3: Add Google SoC DWC3 glue driver Roy Luo
2025-10-07  0:46   ` Krzysztof Kozlowski
2025-10-07 18:08     ` Roy Luo
2025-10-11  3:39   ` kernel test robot [this message]
2025-10-06 23:21 ` [PATCH v1 2/4] dt-bindings: usb: dwc3: Add Google SoC DWC3 USB Roy Luo
2025-10-07  0:44   ` Krzysztof Kozlowski
2025-10-07  9:09     ` Peter Griffin
2025-10-07 14:18       ` Krzysztof Kozlowski
2025-10-07 18:49         ` Roy Luo
2025-10-06 23:21 ` [PATCH v1 3/4] usb: dwc3: Add Google SoC USB PHY driver Roy Luo
2025-10-07  0:42   ` Krzysztof Kozlowski
2025-10-07  5:51   ` Greg Kroah-Hartman
2025-10-07 18:57     ` Roy Luo
2025-10-06 23:21 ` [PATCH v1 4/4] dt-bindings: phy: google: Add Google SoC USB PHY Roy Luo
2025-10-07  0:45   ` Krzysztof Kozlowski
2025-10-07 19:04     ` Roy Luo
2025-10-07  1:06 ` [PATCH v1 0/4] Add Google Tensor SoC USB support Krzysztof Kozlowski
2025-10-07 18:03   ` Roy Luo

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=202510111335.oyOAs9MB-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=Thinh.Nguyen@synopsys.com \
    --cc=andre.draszik@linaro.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=joychakr@google.com \
    --cc=kishon@kernel.org \
    --cc=krzk@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-phy@lists.infradead.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=mnkumar@google.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=p.zabel@pengutronix.de \
    --cc=peter.griffin@linaro.org \
    --cc=robh@kernel.org \
    --cc=royluo@google.com \
    --cc=tudor.ambarus@linaro.org \
    --cc=vkoul@kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).