All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 2/2] drm/i915: Simplify some icl pll calculations
Date: Mon, 8 Apr 2019 19:06:01 +0300	[thread overview]
Message-ID: <20190408160601.GH3888@intel.com> (raw)
In-Reply-To: <155473855386.26510.399775695436410433@skylake-alporthouse-com>

On Mon, Apr 08, 2019 at 04:49:13PM +0100, Chris Wilson wrote:
> Quoting Ville Syrjala (2019-04-08 16:27:02)
> > -       /*
> > -        * Adjust the original formula to delay the division by 2^22 in order to
> > -        * minimize possible rounding errors.
> > -        */
> > -       tmp = (u64)m1 * m2_int * ref_clock +
> > -             (((u64)m1 * m2_frac * ref_clock) >> 22);
> > -       tmp = div_u64(tmp, 5 * div1 * div2);
> > -
> > -       return tmp;
> > +       return div_u64(mul_u32_u32(ref_clock * m1, m2),
> > +                      (5 * div1 * div2) << 22);
> 
> You say the denominator here is a u64, so do you not need to cast
> (u64)(5 * d1 * d2) to ensure it doesn't overflow the shift?

It should fit into u32. The maximum value should be
<= (5*0xf*0x7)<<22 based on the number of bits available
for div1/2.

-- 
Ville Syrjälä
Intel
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2019-04-08 16:06 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-08 15:27 [PATCH 1/2] drm/i915: Use mul_u32_u32() more Ville Syrjala
2019-04-08 15:27 ` [PATCH 2/2] drm/i915: Simplify some icl pll calculations Ville Syrjala
2019-04-08 15:49   ` Chris Wilson
2019-04-08 16:06     ` Ville Syrjälä [this message]
2019-04-08 16:14       ` Chris Wilson
2019-04-08 17:05       ` Chris Wilson
2019-04-10 17:59         ` Ville Syrjälä
2019-04-10 18:13           ` Chris Wilson
2019-04-10 18:51             ` Ville Syrjälä
2019-04-08 15:40 ` ✗ Fi.CI.SPARSE: warning for series starting with [1/2] drm/i915: Use mul_u32_u32() more Patchwork
2019-04-08 15:44 ` [PATCH 1/2] " Chris Wilson
2019-04-10 18:24   ` Ville Syrjälä
2019-04-08 16:28 ` ✗ Fi.CI.BAT: failure for series starting with [1/2] " Patchwork
2019-04-30 14:10 ` ✗ Fi.CI.SPARSE: warning for series starting with [1/2] drm/i915: Use mul_u32_u32() more (rev2) Patchwork
2019-04-30 14:25 ` ✓ Fi.CI.BAT: success " Patchwork
2019-05-01  4:53 ` ✗ Fi.CI.IGT: failure " Patchwork
2019-05-02  7:43 ` Patchwork
2019-05-02  8:47 ` ✓ Fi.CI.IGT: success " Patchwork

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=20190408160601.GH3888@intel.com \
    --to=ville.syrjala@linux.intel.com \
    --cc=chris@chris-wilson.co.uk \
    --cc=intel-gfx@lists.freedesktop.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.