All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thierry Reding <thierry.reding@gmail.com>
To: Doug Anderson <dianders@chromium.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	Mark Brown <broonie@kernel.org>,
	Liam Girdwood <lgirdwood@gmail.com>,
	"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Boris Brezillon <boris.brezillon@free-electrons.com>,
	Alexandre Courbot <acourbot@nvidia.com>
Subject: Re: linux-next: manual merge of the pwm tree with the regulator tree
Date: Mon, 11 Jul 2016 23:30:59 +0200	[thread overview]
Message-ID: <20160711213059.GA12816@ulmo.ba.sec> (raw)
In-Reply-To: <CAD=FV=UBidDK2XN=uchV=Rr9LtYQ7m6Y6uRxe8xKhFLva6f5+w@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2136 bytes --]

On Mon, Jul 11, 2016 at 09:47:34AM -0700, Doug Anderson wrote:
> Hi,
> 
> On Sun, Jul 10, 2016 at 11:56 PM, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> > Hi Thierry,
> >
> > Today's linux-next merge of the pwm tree got a conflict in:
> >
> >   drivers/regulator/pwm-regulator.c
> >
> > between commit:
> >
> >   830583004e61 ("regulator: pwm: Drop unneeded pwm_enable() call")
> >   27bfa8893b15 ("regulator: pwm: Support for enable GPIO")
> >   c2588393e631 ("regulator: pwm: Fix regulator ramp delay for continuous mode")
> >
> > from the regulator tree and commit:
> >
> >   b0303deaa480 ("regulator: pwm: Adjust PWM config at probe time")
> >   8bd57ca236d0 ("regulator: pwm: Switch to the atomic PWM API")
> >   25d16595935b ("regulator: pwm: Retrieve correct voltage")
> >   53f239af4c14 ("regulator: pwm: Support extra continuous mode cases")
> >
> > from the pwm tree.
> >
> > I fixed it up (I think, please check - see below) and can carry the fix
> > as necessary. This is now fixed as far as linux-next is concerned, but
> > any non trivial conflicts should be mentioned to your upstream maintainer
> > when your tree is submitted for merging.  You may also want to consider
> > cooperating with the maintainer of the conflicting tree to minimise any
> > particularly complex conflicts.
> >
> > --
> > Cheers,
> > Stephen Rothwell
> 
> [ cut ]
> 
> >  -      /* Delay required by PWM regulator to settle to the new voltage */
> >  -      usleep_range(ramp_delay, ramp_delay + 1000);
> >  +      /* Ramp delay is in uV/uS. Adjust to uS and delay */
> >  +      ramp_delay = DIV_ROUND_UP(abs(min_uV - old_uV), ramp_delay);
> 
> This was what I was worried about and why I originally sent my patch
> based upon Boris's series.  The above should be:
> 
> ramp_delay = DIV_ROUND_UP(abs(req_min_uV - old_uV), ramp_delay);
> 
> Specifically note the use of "req_min_uV" and not "min_uV".

Okay, so this is something that needs to be fixed up in one of Boris'
patches? Can you help point out where exactly? The conflict should be
gone as of tomorrow's linux-next.

Thierry

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2016-07-11 21:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-11  6:56 linux-next: manual merge of the pwm tree with the regulator tree Stephen Rothwell
2016-07-11 16:47 ` Doug Anderson
2016-07-11 21:30   ` Thierry Reding [this message]
2016-07-11 21:39     ` Thierry Reding
2016-07-25  8:29       ` Thierry Reding
2016-07-25 13:29         ` Doug Anderson
2016-07-25 14:26           ` Thierry Reding
  -- strict thread matches above, loose matches on Subject: below --
2016-05-03  8:25 Stephen Rothwell
2016-05-03 11:03 ` Mark Brown
2016-05-03 12:18   ` Thierry Reding

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=20160711213059.GA12816@ulmo.ba.sec \
    --to=thierry.reding@gmail.com \
    --cc=acourbot@nvidia.com \
    --cc=boris.brezillon@free-electrons.com \
    --cc=broonie@kernel.org \
    --cc=dianders@chromium.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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.