[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAPybu_3EBnHk3x1nRXTvZT1tuk5CmJidiA9BupaTbgjP6pADOg@mail.gmail.com>
Date: Wed, 26 Jul 2017 15:47:51 +0200
From: Ricardo Ribalda Delgado <ricardo.ribalda@...il.com>
To: Harry Wentland <harry.wentland@....com>
Cc: Alex Deucher <alexander.deucher@....com>,
Christian König <christian.koenig@....com>,
David Airlie <airlied@...ux.ie>, Rex Zhu <Rex.Zhu@....com>,
Tom St Denis <tom.stdenis@....com>,
Eric Huang <JinHuiEric.Huang@....com>,
Huang Rui <ray.huang@....com>,
Dan Carpenter <dan.carpenter@...cle.com>,
"Edward O'Callaghan" <funfunctor@...klore1984.net>,
Kees Cook <keescook@...omium.org>,
"Andrew F. Davis" <afd@...com>,
Hawking Zhang <Hawking.Zhang@....com>,
Baoyou Xie <baoyou.xie@...aro.org>,
Masahiro Yamada <yamada.masahiro@...ionext.com>,
Colin Ian King <colin.king@...onical.com>,
Nils Wallménius <nils.wallmenius@...il.com>,
Joe Perches <joe@...ches.com>, amd-gfx@...ts.freedesktop.org,
"dri-devel@...ts.freedesktop.org" <dri-devel@...ts.freedesktop.org>,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 01/14] amdgpu: powerplay: Remove unused function
Hi Harry
On Mon, Jul 24, 2017 at 5:45 PM, Harry Wentland <harry.wentland@....com> wrote:
> On 2017-07-24 10:06 AM, Ricardo Ribalda Delgado wrote:
>> Hi Harry
>> On Mon, Jul 24, 2017 at 4:01 PM, Harry Wentland <harry.wentland@....com> wrote:
>>
>>>
>>> This is used and needed by the DC display driver. See
>>> display/amdgpu_dm/amdgpu_dm_services.c:193 in Alex's amd-staging-4.11 tree:
>>>
>>> https://cgit.freedesktop.org/~agd5f/linux/tree/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm_services.c?h=amd-staging-4.11
>>>
>>
>> I could not find any reference to the function in linux-next (>4.12)
>>
>> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/tree/drivers/gpu/drm/amd
>>
>> Is there any plan to merge Alex's amd-stagin tree?
>
> The plan is to merge/upstream the amd/display portion of Alex's
> amd-staging tree. We're currently working on the community feedback we
> received to get it into shape.
Is there any timeframe for this?
At least we should remove the pr_info("min_core_set_clock not
set\n"); message.
it is (very) misleading right now.
Regards!
>
> Harry
>
>>
>> Sorry, I am not very familiar with this subsystem.
>>
>> Regards!
>>
--
Ricardo Ribalda
Powered by blists - more mailing lists