Subject: Re: [PATCH 04/12] drm: Nuke mode->vrefresh Message-ID: <20200226115708.GH13686@xxxxxxxxx> References: <20200219203544.31013-1-ville.syrjala@xxxxxxxxxxxxxxx> <CGME20200219203620eucas1p24b4990a91e758dbcf3e9b943669b0c8f@xxxxxxxxxxxxxxxxxxxx> <20200219203544.31013-5-ville.syrjala@xxxxxxxxxxxxxxx> <0f278771-79ce-fe23-e72c-3935dbe82d24@xxxxxxxxxxx> <20200225112114.GA13686@xxxxxxxxx> <3ca785f2-9032-aaf9-0965-8657d31116ba@xxxxxxxxxxx> <20200225154506.GF13686@xxxxxxxxx> <20200225192720.GG13686@xxxxxxxxx> <CACRpkdZk9QEy+Kzkmy4BXiHB+aq9hprf=dmA_-R23yqH3NCt1g@xxxxxxxxxxxxxx> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <CACRpkdZk9QEy+Kzkmy4BXiHB+aq9hprf=dmA_-R23yqH3NCt1g@xxxxxxxxxxxxxx> X-Patchwork-Hint: comment User-Agent: Mutt/1.10.1 (2018-07-13) On Tue, Feb 25, 2020 at 10:52:25PM +0100, Linus Walleij wrote: > On Tue, Feb 25, 2020 at 8:27 PM Ville Syrjälä > <ville.syrjala@xxxxxxxxxxxxxxx> wrote: > > > OK, so I went ahead a wrote a bit of cocci [1] to find the bad apples. > > That's impressive :D > > > Unfortunately it found a lot of strange stuff: > > I will answer for the weirdness I caused. > > I have long suspected that a whole bunch of the "simple" displays > are not simple but contains a display controller and memory. > That means that the speed over the link to the display and > actual refresh rate on the actual display is asymmetric because > well we are just updating a RAM, the resolution just limits how > much data we are sending, the clock limits the speed on the > bus over to the RAM on the other side. IMO even in command mode mode->clock should probably be the actual dotclock used by the display. If there's another clock for the bus speed/etc. it should be stored somewhere else. -- Ville Syrjälä Intel
_______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/dri-devel
