All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ladislav Michl <oss-lists@triops.cz>
To: Thinh Nguyen <Thinh.Nguyen@synopsys.com>
Cc: Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Liang He <windhl@126.com>,
	"linux-mips@vger.kernel.org" <linux-mips@vger.kernel.org>,
	"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>
Subject: Re: [PATCH v2 2/3] usb: dwc3: dwc3-octeon: Move node parsing into driver probe
Date: Thu, 13 Jul 2023 23:37:34 +0200	[thread overview]
Message-ID: <ZLBunhzPaRsFlg41@lenoch> (raw)
In-Reply-To: <20230705230827.ckzaryaaz73sjrqb@synopsys.com>

On Wed, Jul 05, 2023 at 11:08:31PM +0000, Thinh Nguyen wrote:
> On Sun, Jul 02, 2023, Ladislav Michl wrote:
> > From: Ladislav Michl <ladis@linux-mips.org>
> > 
> > Make dwc3_octeon_clocks_start just start the clocks.
> 
> This commit message is different than the subject. Also, please explain
> why we need to move this logic to probe in this commit message body.
> 
> > 
> > Signed-off-by: Ladislav Michl <ladis@linux-mips.org>
> > ---
> >  CHANGES:
> >  -v2: if else block bracket according CodingStyle
> >  
> >  drivers/usb/dwc3/dwc3-octeon.c | 148 ++++++++++++++++-----------------
> >  1 file changed, 71 insertions(+), 77 deletions(-)
> > 
> > diff --git a/drivers/usb/dwc3/dwc3-octeon.c b/drivers/usb/dwc3/dwc3-octeon.c
> > index 8d5facd881c1..668f6d3490b1 100644
> > --- a/drivers/usb/dwc3/dwc3-octeon.c
> > +++ b/drivers/usb/dwc3/dwc3-octeon.c
> > @@ -300,67 +300,14 @@ static int dwc3_octeon_config_power(struct device *dev, void __iomem *base)
> >  	return 0;
> >  }
> >  
> > -static int dwc3_octeon_clocks_start(struct device *dev, void __iomem *base)
> > +static int dwc3_octeon_clocks_start(struct device *dev, void __iomem *base,
> > +				    int ref_clk_sel, int ref_clk_fsel,
> > +				    int mpll_mul)
> >  {
> > -	int i, div, mpll_mul, ref_clk_fsel, ref_clk_sel = 2;
> > -	u32 clock_rate;
> > +	int div;
> >  	u64 val;
> >  	void __iomem *uctl_ctl_reg = base + USBDRD_UCTL_CTL;
> >  
> > -	if (dev->of_node) {
> > -		const char *ss_clock_type;
> > -		const char *hs_clock_type;
> > -
> > -		i = of_property_read_u32(dev->of_node,
> > -					 "refclk-frequency", &clock_rate);
> > -		if (i) {
> > -			dev_err(dev, "No UCTL \"refclk-frequency\"\n");
> > -			return -EINVAL;
> > -		}
> > -		i = of_property_read_string(dev->of_node,
> > -					    "refclk-type-ss", &ss_clock_type);
> > -		if (i) {
> > -			dev_err(dev, "No UCTL \"refclk-type-ss\"\n");
> > -			return -EINVAL;
> > -		}
> > -		i = of_property_read_string(dev->of_node,
> > -					    "refclk-type-hs", &hs_clock_type);
> > -		if (i) {
> > -			dev_err(dev, "No UCTL \"refclk-type-hs\"\n");
> > -			return -EINVAL;
> > -		}
> > -		if (strcmp("dlmc_ref_clk0", ss_clock_type) == 0) {
> > -			if (strcmp(hs_clock_type, "dlmc_ref_clk0") == 0)
> > -				ref_clk_sel = 0;
> > -			else if (strcmp(hs_clock_type, "pll_ref_clk") == 0)
> > -				ref_clk_sel = 2;
> > -			else
> > -				dev_warn(dev, "Invalid HS clock type %s, using pll_ref_clk instead\n",
> > -					 hs_clock_type);
> > -		} else if (strcmp(ss_clock_type, "dlmc_ref_clk1") == 0) {
> > -			if (strcmp(hs_clock_type, "dlmc_ref_clk1") == 0)
> > -				ref_clk_sel = 1;
> > -			else if (strcmp(hs_clock_type, "pll_ref_clk") == 0)
> > -				ref_clk_sel = 3;
> > -			else {
> > -				dev_warn(dev, "Invalid HS clock type %s, using pll_ref_clk instead\n",
> > -					 hs_clock_type);
> > -				ref_clk_sel = 3;
> > -			}
> > -		} else
> > -			dev_warn(dev, "Invalid SS clock type %s, using dlmc_ref_clk0 instead\n",
> > -				 ss_clock_type);
> > -
> > -		if ((ref_clk_sel == 0 || ref_clk_sel == 1) &&
> > -		    (clock_rate != 100000000))
> > -			dev_warn(dev, "Invalid UCTL clock rate of %u, using 100000000 instead\n",
> > -				 clock_rate);
> > -
> > -	} else {
> > -		dev_err(dev, "No USB UCTL device node\n");
> > -		return -EINVAL;
> > -	}
> > -
> >  	/*
> >  	 * Step 1: Wait for all voltages to be stable...that surely
> >  	 *         happened before starting the kernel. SKIP
> > @@ -404,24 +351,6 @@ static int dwc3_octeon_clocks_start(struct device *dev, void __iomem *base)
> >  	val &= ~USBDRD_UCTL_CTL_REF_CLK_SEL;
> >  	val |= FIELD_PREP(USBDRD_UCTL_CTL_REF_CLK_SEL, ref_clk_sel);
> >  
> > -	ref_clk_fsel = 0x07;
> > -	switch (clock_rate) {
> > -	default:
> > -		dev_warn(dev, "Invalid ref_clk %u, using 100000000 instead\n",
> > -			 clock_rate);
> > -		fallthrough;
> > -	case 100000000:
> > -		mpll_mul = 0x19;
> > -		if (ref_clk_sel < 2)
> > -			ref_clk_fsel = 0x27;
> > -		break;
> > -	case 50000000:
> > -		mpll_mul = 0x32;
> > -		break;
> > -	case 125000000:
> > -		mpll_mul = 0x28;
> > -		break;
> > -	}
> >  	val &= ~USBDRD_UCTL_CTL_REF_CLK_FSEL;
> >  	val |= FIELD_PREP(USBDRD_UCTL_CTL_REF_CLK_FSEL, ref_clk_fsel);
> >  
> > @@ -505,8 +434,72 @@ static void __init dwc3_octeon_phy_reset(void __iomem *base)
> >  static int dwc3_octeon_probe(struct platform_device *pdev)
> >  {
> >  	struct device *dev = &pdev->dev;
> > +	struct device_node *node = dev->of_node;
> >  	struct dwc3_data *data;
> > -	int err;
> > +	int err, ref_clk_sel, ref_clk_fsel, mpll_mul;
> > +	uint32_t clock_rate;
> 
> Use u32?

I do not like homebrew types when we have standard ones. But it seems almost
all usb code is using u32, so I can live with that.

> > +	const char *hs_clock_type, *ss_clock_type;
> > +
> > +	if (!node) {
> > +		dev_err(dev, "No USB UCTL device node\n");
> > +		return -EINVAL;
> > +	}
> > +
> > +	if (of_property_read_u32(node, "refclk-frequency", &clock_rate)) {
> > +		dev_err(dev, "No UCTL \"refclk-frequency\"\n");
> > +		return -EINVAL;
> > +	}
> > +	if (of_property_read_string(node, "refclk-type-ss", &ss_clock_type)) {
> > +		dev_err(dev, "No UCTL \"refclk-type-ss\"\n");
> > +		return -EINVAL;
> > +	}
> > +	if (of_property_read_string(node, "refclk-type-hs", &hs_clock_type)) {
> > +		dev_err(dev, "No UCTL \"refclk-type-hs\"\n");
> > +		return -EINVAL;
> > +	}
> > +
> > +	ref_clk_sel = 2;
> > +	if (strcmp("dlmc_ref_clk0", ss_clock_type) == 0) {
> > +		if (strcmp(hs_clock_type, "dlmc_ref_clk0") == 0)
> > +			ref_clk_sel = 0;
> > +		else if (strcmp(hs_clock_type, "pll_ref_clk") == 0)
> > +			ref_clk_sel = 2;
> > +		else
> > +			dev_warn(dev, "Invalid HS clock type %s, using pll_ref_clk instead\n",
> > +				 hs_clock_type);
> > +	} else if (strcmp(ss_clock_type, "dlmc_ref_clk1") == 0) {
> 
> Did you run checkpatch? I still see some minor formatting issues.

Yes I did. What complain do you see from checkpatch?

> > +		if (strcmp(hs_clock_type, "dlmc_ref_clk1") == 0)
> > +			ref_clk_sel = 1;
> > +		else if (strcmp(hs_clock_type, "pll_ref_clk") == 0) {
> > +			ref_clk_sel = 3;
> > +		} else {
> > +			dev_warn(dev, "Invalid HS clock type %s, using pll_ref_clk instead\n",
> > +				 hs_clock_type);
> > +			ref_clk_sel = 3;
> > +		}
> > +	} else {
> > +		dev_warn(dev, "Invalid SS clock type %s, using dlmc_ref_clk0 instead\n",
> > +			 ss_clock_type);
> > +	}
> > +
> > +	ref_clk_fsel = 0x07;
> > +	switch (clock_rate) {
> > +	default:
> > +		dev_warn(dev, "Invalid ref_clk %u, using 100000000 instead\n",
> > +			 clock_rate);
> > +		fallthrough;
> > +	case 100000000:
> > +		mpll_mul = 0x19;
> > +		if (ref_clk_sel < 2)
> > +			ref_clk_fsel = 0x27;
> > +		break;
> > +	case 50000000:
> > +		mpll_mul = 0x32;
> > +		break;
> > +	case 125000000:
> > +		mpll_mul = 0x28;
> > +		break;
> > +	}
> >  
> >  	data = devm_kzalloc(dev, sizeof(*data), GFP_KERNEL);
> >  	if (!data)
> > @@ -516,7 +509,8 @@ static int dwc3_octeon_probe(struct platform_device *pdev)
> >  	if (IS_ERR(data->base))
> >  		return PTR_ERR(data->base);
> >  
> > -	err = dwc3_octeon_clocks_start(dev, data->base);
> > +	err = dwc3_octeon_clocks_start(dev, data->base,
> > +				       ref_clk_sel, ref_clk_fsel, mpll_mul);
> >  	if (err)
> >  		return err;
> >  
> > -- 
> > 2.39.2
> > 
> 
> BR,
> Thinh

  reply	other threads:[~2023-07-13 21:37 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-02  0:15 [PATCH v2 0/3] Cleanup Octeon DWC3 glue code Ladislav Michl
2023-07-02  0:16 ` [PATCH v2 1/3] usb: dwc3: dwc3-octeon: Convert to glue driver Ladislav Michl
2023-07-05 23:25   ` Thinh Nguyen
2023-07-13 21:33     ` Ladislav Michl
2023-07-14  0:37       ` Thinh Nguyen
2023-07-02  0:16 ` [PATCH v2 2/3] usb: dwc3: dwc3-octeon: Move node parsing into driver probe Ladislav Michl
2023-07-05 23:08   ` Thinh Nguyen
2023-07-13 21:37     ` Ladislav Michl [this message]
2023-07-14  0:42       ` Thinh Nguyen
2023-07-02  0:17 ` [PATCH v2 3/3] usb: dwc3: Add SPDX header and copyright Ladislav Michl

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=ZLBunhzPaRsFlg41@lenoch \
    --to=oss-lists@triops.cz \
    --cc=Thinh.Nguyen@synopsys.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=tsbogend@alpha.franken.de \
    --cc=windhl@126.com \
    /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.