All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Ladislav Michl <oss-lists@triops.cz>
Cc: oe-kbuild-all@lists.linux.dev
Subject: Re: [RFC] usb: dwc3: dwc3-octeon: Fix USB PHY High-Speed PLL Initialization
Date: Tue, 17 Oct 2023 13:59:58 +0800	[thread overview]
Message-ID: <202310171355.p5enLEbv-lkp@intel.com> (raw)
In-Reply-To: <ZShGmL4mph91Ncib@lenoch>

Hi Ladislav,

[This is a private test report for your RFC patch.]
kernel test robot noticed the following build warnings:

[auto build test WARNING on usb/usb-testing]
[also build test WARNING on usb/usb-next usb/usb-linus westeri-thunderbolt/next linus/master v6.6-rc6 next-20231016]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]

url:    https://github.com/intel-lab-lkp/linux/commits/Ladislav-Michl/usb-dwc3-dwc3-octeon-Fix-USB-PHY-High-Speed-PLL-Initialization/20231017-112612
base:   https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git usb-testing
patch link:    https://lore.kernel.org/r/ZShGmL4mph91Ncib%40lenoch
patch subject: [RFC] usb: dwc3: dwc3-octeon: Fix USB PHY High-Speed PLL Initialization
config: m68k-allyesconfig (https://download.01.org/0day-ci/archive/20231017/202310171355.p5enLEbv-lkp@intel.com/config)
compiler: m68k-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231017/202310171355.p5enLEbv-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/202310171355.p5enLEbv-lkp@intel.com/

All warnings (new ones prefixed by >>):

>> drivers/usb/dwc3/dwc3-octeon.c:614: warning: This comment starts with '/**', but isn't a kernel-doc comment. Refer Documentation/doc-guide/kernel-doc.rst
    * Performs a full reset of the UPHY PLL. Note that this is normally done


vim +614 drivers/usb/dwc3/dwc3-octeon.c

   612	
   613	/**
 > 614	 * Performs a full reset of the UPHY PLL. Note that this is normally done
   615	 * internally by a state machine when the UPHY is brought out of reset but this
   616	 * version gives far more time for things to settle before continuing.
   617	 */
   618	static int dwc3_uphy_pll_reset(struct dwc3_octeon *octeon)
   619	{
   620		u16 ctrl, pwr;
   621	
   622		/* 1. Turn on write enable so we can assert reset to the PLL VCO */
   623		ctrl = dwc3_octeon_indirect_read(octeon, DWC3_INT_IND_UPHY_PLL_RESET);
   624		ctrl |= DWC3_INT_IND_UPHY_PLL_RESET_WE;
   625		dwc3_octeon_indirect_write(octeon, DWC3_INT_IND_UPHY_PLL_RESET, ctrl);
   626	
   627		/* 2. Turn on write enable for PLL power control */
   628		pwr = dwc3_octeon_indirect_read(octeon, DWC3_INT_IND_UPHY_PLL_PU);
   629		pwr |= DWC3_INT_IND_UPHY_PLL_PU_WE;
   630		dwc3_octeon_indirect_write(octeon, DWC3_INT_IND_UPHY_PLL_PU, pwr);
   631	
   632		/* 3. Assert VCO reset */
   633		ctrl |= DWC3_INT_IND_UPHY_PLL_RESET_VCO_RST;
   634		dwc3_octeon_indirect_write(octeon, DWC3_INT_IND_UPHY_PLL_RESET, ctrl);
   635	
   636		/* 4. Power off the PLL */
   637		pwr &= ~DWC3_INT_IND_UPHY_PLL_PU_POWER_EN;
   638		dwc3_octeon_indirect_write(octeon, DWC3_INT_IND_UPHY_PLL_PU, pwr);
   639		usleep_range(1000, 2000);
   640	
   641		/* 5. Power on the PLL while VCO is held in reset */
   642		pwr |= DWC3_INT_IND_UPHY_PLL_PU_POWER_EN;
   643		dwc3_octeon_indirect_write(octeon, DWC3_INT_IND_UPHY_PLL_PU, pwr);
   644	
   645		/* Wait for things to stabilize before taking VCO out of reset */
   646		usleep_range(1000, 2000);
   647	
   648		/* 6. Take the VCO out of reset */
   649		ctrl &= ~DWC3_INT_IND_UPHY_PLL_RESET_VCO_RST;
   650		dwc3_octeon_indirect_write(octeon, DWC3_INT_IND_UPHY_PLL_RESET, ctrl);
   651		usleep_range(1000, 2000);
   652	
   653		/* 7. Put the VCO back in reset */
   654		ctrl |= ~DWC3_INT_IND_UPHY_PLL_RESET_VCO_RST;
   655		dwc3_octeon_indirect_write(octeon, DWC3_INT_IND_UPHY_PLL_RESET, ctrl);
   656	
   657		/* 8. Power off the PLL */
   658		pwr &= ~DWC3_INT_IND_UPHY_PLL_PU_POWER_EN;
   659		dwc3_octeon_indirect_write(octeon, DWC3_INT_IND_UPHY_PLL_PU, pwr);
   660		usleep_range(1000, 2000);
   661	
   662		/* 9. Power on the PLL while VCO is held in reset */
   663		pwr |= DWC3_INT_IND_UPHY_PLL_PU_POWER_EN;
   664		dwc3_octeon_indirect_write(octeon, DWC3_INT_IND_UPHY_PLL_PU, pwr);
   665	
   666		/* 10. Take the VCO out of reset */
   667		ctrl &= ~DWC3_INT_IND_UPHY_PLL_RESET_VCO_RST;
   668		dwc3_octeon_indirect_write(octeon, DWC3_INT_IND_UPHY_PLL_RESET, ctrl);
   669	
   670		/* 11. Turn off write enables */
   671		pwr &= ~DWC3_INT_IND_UPHY_PLL_PU_WE;
   672		dwc3_octeon_indirect_write(octeon, DWC3_INT_IND_UPHY_PLL_PU, pwr);
   673	
   674		ctrl &= ~DWC3_INT_IND_UPHY_PLL_RESET_WE;
   675		dwc3_octeon_indirect_write(octeon, DWC3_INT_IND_UPHY_PLL_RESET, ctrl);
   676	
   677		usleep_range(1000, 2000);
   678	
   679		/* Return if we have lock or not */
   680		return dwc3_octeon_pll_locked(octeon);
   681	}
   682	

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

      parent reply	other threads:[~2023-10-17  6:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-12 19:18 [RFC] usb: dwc3: dwc3-octeon: Fix USB PHY High-Speed PLL Initialization Ladislav Michl
2023-10-12 22:23 ` Thinh Nguyen
2023-10-13  5:16   ` Ladislav Michl
2023-10-20 23:11     ` Thinh Nguyen
2023-10-17  5:59 ` kernel test robot [this message]

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=202310171355.p5enLEbv-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=oss-lists@triops.cz \
    /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.