All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hristo Venev <hristo-dptOiocmjbVBDLzU/O5InQ@public.gmane.org>
To: amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: drm/amdgpu/display: Multiple fixed-point implementations
Date: Sat, 10 Dec 2016 12:29:04 +0200	[thread overview]
Message-ID: <1481365744.3081.2.camel@venev.name> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 668 bytes --]

There are at least three implementations of fixed-point arithmetic in
drm/amdgpu/display: fixed31_32 (signed 32-32), fixed32_32 (unsigned 32-
32) and bw_fixed (signed 40-24). I don't think fixed-point arithmetic
implementations belong in drivers.

There already are two implementations of fixed-point in drm: fixed20_12
(unsigned 20-12) and drm_fixp (signed 32-32). The latter could be used
instead of fixed31_32.

Maybe we could use a standard fixed-point interface and share the
source code between most (or all) of the implementations. This is one
of the things that can be done before merging DC and is not too driver-
specific. What do you guys think?

[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

[-- Attachment #2: Type: text/plain, Size: 154 bytes --]

_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx

             reply	other threads:[~2016-12-10 10:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-10 10:29 Hristo Venev [this message]
     [not found] ` <1481365744.3081.2.camel-dptOiocmjbVBDLzU/O5InQ@public.gmane.org>
2016-12-10 22:25   ` drm/amdgpu/display: Multiple fixed-point implementations Deucher, Alexander

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=1481365744.3081.2.camel@venev.name \
    --to=hristo-dptoiocmjbvbdlzu/o5inq@public.gmane.org \
    --cc=amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@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.