Re: disp_cc_mdss_pclk0_clk_src: rcg didn't update its configuration

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Fri, 6 Aug 2021 at 19:18, Steev Klimaszewski <steev@xxxxxxxx> wrote:
>
> Hi Dmitry,
>
> On 8/6/21 2:04 AM, Dmitry Baryshkov wrote:
> > Hi Steev,
> > Could you please check if the following kernel commits also show this
> >>> behaviour:
> >>>
> >>> - 170b763597d3a0a79f135e4d83a38462c3964fdf
> >>>
> >>> - f4b43ac0b0af1d115effd08133046a694ac33dc2
> >>>
> >> Yes, I have both of those commits, and the issue still shows up.  This
> >> is with 5.13.8 - additionally, I have a Lenovo Flex 5G which is running
> >> a tree based on 5.14.0-rc2-next-20210721 and it shows a similar issue,
> >> with the message being
> >>
> >> disp_cc_mdss_edp_pixel_clk_src: rcg didn't update its configuration.
> >>
> > Thus I have asked you to check if the issue shows up if you build one
> > of the mentioned commits (they are between 5.12 and 5.13). We are
> > trying to narrow down which of the changes broke your system.
> >
> Apologies for misunderstanding, I thought you meant make sure I had
> those commits in my tree.  I have tried reverting both individually, as
> well as both together and the issue still shows up.

Uhm. Could you please just checkout (note, checkout, not revert) each
of those commits, build the kernel and try the resulting kernel?

Two additional commits to try (checkout, build, try):

- c68da22dc9cc39ced8fc30b65fca5ce2f9583735

- b2150cab9a97c1fcc15684200a6020b6d231106d

Also just to be sure, could you please also build the v5.13-rc1 and
try running that kernel?

So in the end I'm asking you to try 5 kernel builds.

-- 
With best wishes
Dmitry



[Index of Archives]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [Linux for Sparc]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux MIPS]     [ECOS]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux