mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Johan Hovold <johan@kernel.org>
To: Matthias Kaehlcke <mka@chromium.org>
Cc: Johan Hovold <johan+linaro@kernel.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Felipe Balbi <balbi@kernel.org>, Andy Gross <agross@kernel.org>,
	Bjorn Andersson <bjorn.andersson@linaro.org>,
	Konrad Dybcio <konrad.dybcio@somainline.org>,
	linux-arm-msm@vger.kernel.org, linux-usb@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] usb: dwc3: qcom: clean up icc init
Date: Sun, 7 Aug 2022 11:50:19 +0200	[thread overview]
Message-ID: <Yu+K28R2YJ327jET@hovoldconsulting.com> (raw)
In-Reply-To: <Yu1Y1nDCyzKhJUAI@google.com>

On Fri, Aug 05, 2022 at 10:52:22AM -0700, Matthias Kaehlcke wrote:
> On Fri, Aug 05, 2022 at 09:45:00AM +0200, Johan Hovold wrote:
> > Clean up the interconnect-initialisation helper by increasing
> > indentation of (or merging) continuation lines and adding brackets
> > around multi-line blocks in order to improve readability.
> > 
> > Signed-off-by: Johan Hovold <johan+linaro@kernel.org>
> > ---
> >  drivers/usb/dwc3/dwc3-qcom.c | 15 +++++++--------
> >  1 file changed, 7 insertions(+), 8 deletions(-)
> > 
> > diff --git a/drivers/usb/dwc3/dwc3-qcom.c b/drivers/usb/dwc3/dwc3-qcom.c
> > index 196efa9f2545..f2ff4fe1490a 100644
> > --- a/drivers/usb/dwc3/dwc3-qcom.c
> > +++ b/drivers/usb/dwc3/dwc3-qcom.c
> > @@ -253,7 +253,7 @@ static int dwc3_qcom_interconnect_init(struct dwc3_qcom *qcom)
> >  	qcom->icc_path_ddr = of_icc_get(dev, "usb-ddr");
> >  	if (IS_ERR(qcom->icc_path_ddr)) {
> >  		dev_err(dev, "failed to get usb-ddr path: %ld\n",
> > -			PTR_ERR(qcom->icc_path_ddr));
> > +				PTR_ERR(qcom->icc_path_ddr));
> 
> What's wrong with the existing indentation? It looks similar to the indentation
> changes you do below for icc_set_bw().

The indentation of continuation lines in this driver is a bit
inconsistent, but the above change matches the next conditional and the
rest of the function (which does not use open-parenthesis alignment).

> Maybe your preference is double indentation for continuation lines rather than
> aligning them roughly with the opening parenthesis of the calling function?

I generally prefer two tabs over excessive indentation involving space
characters that need to be added or removed in continuation lines just
because a symbol name is updated.

> >  		return PTR_ERR(qcom->icc_path_ddr);
> >  	}
> >  
> > @@ -265,20 +265,19 @@ static int dwc3_qcom_interconnect_init(struct dwc3_qcom *qcom)
> >  	}
> >  
> >  	max_speed = usb_get_maximum_speed(&qcom->dwc3->dev);
> > -	if (max_speed >= USB_SPEED_SUPER || max_speed == USB_SPEED_UNKNOWN)
> > +	if (max_speed >= USB_SPEED_SUPER || max_speed == USB_SPEED_UNKNOWN) {
> >  		ret = icc_set_bw(qcom->icc_path_ddr,
> > -			USB_MEMORY_AVG_SS_BW, USB_MEMORY_PEAK_SS_BW);
> > -	else
> > +				USB_MEMORY_AVG_SS_BW, USB_MEMORY_PEAK_SS_BW);
> > +	} else {
> >  		ret = icc_set_bw(qcom->icc_path_ddr,
> > -			USB_MEMORY_AVG_HS_BW, USB_MEMORY_PEAK_HS_BW);
> > -
> > +				USB_MEMORY_AVG_HS_BW, USB_MEMORY_PEAK_HS_BW);
> > +	}
> >  	if (ret) {
> >  		dev_err(dev, "failed to set bandwidth for usb-ddr path: %d\n", ret);
> >  		return ret;
> >  	}
> >  
> > -	ret = icc_set_bw(qcom->icc_path_apps,
> > -		APPS_USB_AVG_BW, APPS_USB_PEAK_BW);
> > +	ret = icc_set_bw(qcom->icc_path_apps, APPS_USB_AVG_BW, APPS_USB_PEAK_BW);
> >  	if (ret) {
> >  		dev_err(dev, "failed to set bandwidth for apps-usb path: %d\n", ret);
> >  		return ret;

Johan

      reply	other threads:[~2022-08-07  9:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-05  7:44 [PATCH 0/2] " Johan Hovold
2022-08-05  7:44 ` [PATCH 1/2] usb: dwc3: qcom: only parse 'maximum-speed' once Johan Hovold
2022-08-05 17:44   ` Matthias Kaehlcke
2022-08-05 20:34   ` Andrew Halaney
2022-08-05  7:45 ` [PATCH 2/2] usb: dwc3: qcom: clean up icc init Johan Hovold
2022-08-05 17:52   ` Matthias Kaehlcke
2022-08-07  9:50     ` Johan Hovold [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=Yu+K28R2YJ327jET@hovoldconsulting.com \
    --to=johan@kernel.org \
    --cc=agross@kernel.org \
    --cc=balbi@kernel.org \
    --cc=bjorn.andersson@linaro.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=johan+linaro@kernel.org \
    --cc=konrad.dybcio@somainline.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=mka@chromium.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

all inboxes | Powered by JetHome®