On 2017-07-26 09:47 AM, Ricardo Ribalda Delgado wrote: > Hi Harry > > On Mon, Jul 24, 2017 at 5:45 PM, Harry Wentland <harry.wentland at amd.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 at amd.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? > We're actively working on this. It depends on cleaning up our codebase a fair bit. Harry > 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! >>> > > >
