All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthias Kaehlcke <mka-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
To: Mark Brown <broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Cc: lgirdwood-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
	Douglas Anderson
	<dianders-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>,
	briannorris-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org,
	javier-0uQlZySMnqxg9hUCZPvPmw@public.gmane.org,
	robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org,
	mark.rutland-5wv7dgnIgG8@public.gmane.org,
	linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH v4 1/4] regulator: Add set_voltage_time op
Date: Tue, 13 Sep 2016 12:12:41 -0700	[thread overview]
Message-ID: <20160913191241.GD62872@google.com> (raw)
In-Reply-To: <20160913011831.GB62872-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>

El Mon, Sep 12, 2016 at 06:18:31PM -0700 Matthias Kaehlcke ha dit:

> El Tue, Sep 13, 2016 at 12:57:58AM +0100 Mark Brown ha dit:
> 
> > On Mon, Sep 12, 2016 at 04:18:51PM -0700, Matthias Kaehlcke wrote:
> > > El Mon, Sep 12, 2016 at 07:32:30PM +0100 Mark Brown ha dit:
> > > > On Tue, Sep 06, 2016 at 12:03:15PM -0700, Matthias Kaehlcke wrote:
...
> > > > Why were the gotos there?
> > 
> > > Not sure how to interpret your question. Would you prefer no to use
> > > gotos, should the notification be skipped in case the voltage is not
> > > changed, do you expect a comment, ...?
> > 
> > I mean I couldn't tell why a goto was a good idea for what seemed like
> > perfectly normal conditional logic.  Either I couldn't tell because it's
> > not a good idea or it is a good idea but should be clearer in some way
> > but since I didn't really understand what the purpose of doing the gotos
> > was I can't say for sure either way.
> 
> The main purpose is to avoid deeply nested code branches.
> 
> Without gotos I think we'd end up with something like this:
> 
> static int _regulator_do_set_voltage(struct regulator_dev *rdev,
>                                      int min_uV, int max_uV)
> {
> 	...
> 	if (ret == 0 && !rdev->constraints->ramp_disable) {
> 		if (rdev->desc->ops->set_voltage_time_sel) {
> 			if (old_selector >= 0 && old_selector != selector)
> 				  rdev->desc->ops->set_voltage_time_sel(rdev, old_selector, selector);
> 		} else {
> 		       if (old_uV != new_uV) {
> 				if (rdev->desc->ops->set_voltage_time)
> 					delay = rdev->desc->ops->set_voltage_time(rdev, old_uV, new_uV);
> 				else
> 					delay = _regulator_set_voltage_time(rdev, old_uV, new_uV);
> 		       }
> 		}
> 
> 		// delay
> 	}
> }
> 
> I can change the patch accordingly if this is preferred.

The above improves a bit when a local ops variable is used instead of
rdev->desc->ops. With that it looks bearable and probably better than
the goto version.
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

WARNING: multiple messages have this Message-ID (diff)
From: Matthias Kaehlcke <mka@chromium.org>
To: Mark Brown <broonie@kernel.org>
Cc: lgirdwood@gmail.com, Douglas Anderson <dianders@chromium.org>,
	briannorris@chromium.org, javier@dowhile0.org,
	robh+dt@kernel.org, mark.rutland@arm.com,
	linux-kernel@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v4 1/4] regulator: Add set_voltage_time op
Date: Tue, 13 Sep 2016 12:12:41 -0700	[thread overview]
Message-ID: <20160913191241.GD62872@google.com> (raw)
In-Reply-To: <20160913011831.GB62872@google.com>

El Mon, Sep 12, 2016 at 06:18:31PM -0700 Matthias Kaehlcke ha dit:

> El Tue, Sep 13, 2016 at 12:57:58AM +0100 Mark Brown ha dit:
> 
> > On Mon, Sep 12, 2016 at 04:18:51PM -0700, Matthias Kaehlcke wrote:
> > > El Mon, Sep 12, 2016 at 07:32:30PM +0100 Mark Brown ha dit:
> > > > On Tue, Sep 06, 2016 at 12:03:15PM -0700, Matthias Kaehlcke wrote:
...
> > > > Why were the gotos there?
> > 
> > > Not sure how to interpret your question. Would you prefer no to use
> > > gotos, should the notification be skipped in case the voltage is not
> > > changed, do you expect a comment, ...?
> > 
> > I mean I couldn't tell why a goto was a good idea for what seemed like
> > perfectly normal conditional logic.  Either I couldn't tell because it's
> > not a good idea or it is a good idea but should be clearer in some way
> > but since I didn't really understand what the purpose of doing the gotos
> > was I can't say for sure either way.
> 
> The main purpose is to avoid deeply nested code branches.
> 
> Without gotos I think we'd end up with something like this:
> 
> static int _regulator_do_set_voltage(struct regulator_dev *rdev,
>                                      int min_uV, int max_uV)
> {
> 	...
> 	if (ret == 0 && !rdev->constraints->ramp_disable) {
> 		if (rdev->desc->ops->set_voltage_time_sel) {
> 			if (old_selector >= 0 && old_selector != selector)
> 				  rdev->desc->ops->set_voltage_time_sel(rdev, old_selector, selector);
> 		} else {
> 		       if (old_uV != new_uV) {
> 				if (rdev->desc->ops->set_voltage_time)
> 					delay = rdev->desc->ops->set_voltage_time(rdev, old_uV, new_uV);
> 				else
> 					delay = _regulator_set_voltage_time(rdev, old_uV, new_uV);
> 		       }
> 		}
> 
> 		// delay
> 	}
> }
> 
> I can change the patch accordingly if this is preferred.

The above improves a bit when a local ops variable is used instead of
rdev->desc->ops. With that it looks bearable and probably better than
the goto version.

  parent reply	other threads:[~2016-09-13 19:12 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-06 19:03 [PATCH v4 1/4] regulator: Add set_voltage_time op Matthias Kaehlcke
     [not found] ` <20160906190315.GC92391-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
2016-09-12 18:32   ` Mark Brown
2016-09-12 18:32     ` Mark Brown
     [not found]     ` <20160912183230.GF27946-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2016-09-12 23:18       ` Matthias Kaehlcke
2016-09-12 23:18         ` Matthias Kaehlcke
2016-09-12 23:57         ` Mark Brown
     [not found]           ` <20160912235758.GO27946-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2016-09-13  1:18             ` Matthias Kaehlcke
2016-09-13  1:18               ` Matthias Kaehlcke
     [not found]               ` <20160913011831.GB62872-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
2016-09-13 19:12                 ` Matthias Kaehlcke [this message]
2016-09-13 19:12                   ` Matthias Kaehlcke
  -- strict thread matches above, loose matches on Subject: below --
2016-09-06 20:14 Matthias Kaehlcke
2016-09-06 21:01 Matthias Kaehlcke
     [not found] ` <20160906210125.GE79728-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
2016-09-06 22:40   ` Mark Brown
2016-09-06 22:40     ` Mark Brown
     [not found]     ` <20160906224054.GX3950-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2016-09-06 23:38       ` Mark Brown
2016-09-06 23:38         ` Mark Brown
2016-09-06 23:46         ` Matthias Kaehlcke

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=20160913191241.GD62872@google.com \
    --to=mka-f7+t8e8rja9g9huczpvpmw@public.gmane.org \
    --cc=briannorris-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org \
    --cc=broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
    --cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=dianders-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org \
    --cc=javier-0uQlZySMnqxg9hUCZPvPmw@public.gmane.org \
    --cc=lgirdwood-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=mark.rutland-5wv7dgnIgG8@public.gmane.org \
    --cc=robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.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 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.