dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Samuel Pitoiset <samuel.pitoiset@gmail.com>
To: "Christian König" <deathsimple@vodafone.de>,
	"Emil Velikov" <emil.l.velikov@gmail.com>
Cc: ML dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH libdrm 0/4] libdrm: add new GPU sensor interface for AMDGPU
Date: Tue, 14 Feb 2017 11:25:05 +0100	[thread overview]
Message-ID: <43866d13-c2b8-0fcd-08a3-e9e05ec3c0da@gmail.com> (raw)
In-Reply-To: <7255f144-29c8-3e60-86fe-a999165b7dd0@vodafone.de>



On 02/14/2017 10:43 AM, Christian König wrote:
> Am 14.02.2017 um 02:44 schrieb Emil Velikov:
>> On 14 February 2017 at 00:08, Samuel Pitoiset
>> <samuel.pitoiset@gmail.com> wrote:
>>> Hi,
>>>
>>> This series implements a new GPU sensor interface which will allow to
>>> query the current temperature and the shader/memory clocks via the
>>> GALLIUM_HUD. This adds the same functionality as the Radeon driver.
>>>
>>> The first patch of the series syncs amdgpu_drm.h with kernel headers.
>>>
>>> Branch is here:
>>> https://cgit.freedesktop.org/~hakzsam/drm/log/?h=si_clocks_temp
>>>
>>> Please review.
>>> Thanks!
>>>
>>> Samuel Pitoiset (4):
>>>    amdgpu: sync amdgpu_drm.h with the kernel
>> Samuel,
>>
>> Please read through drm/include/drm/README in particular "When and how
>> to update these files".
>> JFYI multiple people are trying to get various UABI in, so do keep an
>> eye open for fireworks.
>>
>>>    amdgpu: add new GPU sensor related interface
>>>    amdgpu: allow to query GPU sensor related information
>> You'll need to add the new interface(s) to the symbols test. `make
>> check' must pass.
>>
>>>    Bump version for 2.4.76 release
>>>
>> Skim through RELEASING for details on how to roll one.
>>
>> Pardon, if I'm flocking up a dead horse here.
>
> Please keep an eye open on this Emil.
>
> Additionally to what said before you didn't used upstream, but rather
> the branch including the DC code (with the freesync IOCTL).
>
> We are probably not getting this upstream like that, so pushing it into
> libdrm is clearly not a good idea.

Thanks for your feedbacks. I will first wait for the kernel interface to 
be merged before making a new series.

>
> Regards,
> Christian.
>
>>
>> Thanks
>> Emil
>> _______________________________________________
>> dri-devel mailing list
>> dri-devel@lists.freedesktop.org
>> https://lists.freedesktop.org/mailman/listinfo/dri-devel
>
>
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

      reply	other threads:[~2017-02-14 10:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-14  0:08 [PATCH libdrm 0/4] libdrm: add new GPU sensor interface for AMDGPU Samuel Pitoiset
2017-02-14  0:08 ` [PATCH libdrm 1/4] amdgpu: sync amdgpu_drm.h with the kernel Samuel Pitoiset
2017-02-14  0:09 ` [PATCH libdrm 2/4] amdgpu: add new GPU sensor related interface Samuel Pitoiset
2017-02-14  0:09 ` [PATCH libdrm 3/4] amdgpu: allow to query GPU sensor related information Samuel Pitoiset
2017-02-14  0:09 ` [PATCH libdrm 4/4] Bump version for 2.4.76 release Samuel Pitoiset
2017-02-14  1:44 ` [PATCH libdrm 0/4] libdrm: add new GPU sensor interface for AMDGPU Emil Velikov
2017-02-14  9:43   ` Christian König
2017-02-14 10:25     ` Samuel Pitoiset [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=43866d13-c2b8-0fcd-08a3-e9e05ec3c0da@gmail.com \
    --to=samuel.pitoiset@gmail.com \
    --cc=deathsimple@vodafone.de \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=emil.l.velikov@gmail.com \
    /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