Reviewed-by: Lyude Paul
On Fri, 2022-11-11 at 09:19 +0800, Yang Li wrote:
> ./drivers/gpu/drm/nouveau/nvkm/engine/gr/gf100.c:423:31-32: Unneeded semicolon
>
> Link: https://bugzilla.openanolis.cn/show_bug.cgi?id=3013
> Fixes: 78a43c7e3b2f ("drm/nouveau/gr/gf100-: make global attrib_cb actually
tree/branch:
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
branch HEAD: 3c1f24109dfc4fb1a3730ed237e50183c6bb26b3 Add linux-next specific
files for 20221115
Error/Warning reports:
https://lore.kernel.org/oe-kbuild-all/202211041320.coq8eelj-...@intel.com
https
On Mon, 14 Nov 2022 14:00:31 +0100, Maxime Ripard wrote:
> We'll need to get the pixel clock to generate proper display modes for
> all the current named modes. Let's add it to struct drm_cmdline_mode and
> fill it when parsing the named mode.
>
>
Applied to drm/drm-misc (drm-misc-next).
Thanks
On Mon, 14 Nov 2022 14:00:30 +0100, Maxime Ripard wrote:
> The current code to deal with named modes will only set the mode name, and
> then it's up to drivers to try to match that name to whatever mode or
> configuration they see fit.
>
> The plan is to remove that need and move the named mode ha
On Mon, 14 Nov 2022 14:00:29 +0100, Maxime Ripard wrote:
> The current named mode parsing relies only on the mode name, and doesn't
> allow to specify any other parameter.
>
> Let's convert that string list to an array of a custom structure that will
> hold the name and some additional parameters
On Mon, 14 Nov 2022 14:00:27 +0100, Maxime Ripard wrote:
> drm_connector_pick_cmdline_mode() is in charge of finding a proper
> drm_display_mode from the definition we got in the video= command line
> argument.
>
> Let's add some unit tests to make sure we're not getting any regressions
> there.
>
On Mon, 14 Nov 2022 14:00:28 +0100, Maxime Ripard wrote:
> The current construction of the named mode parsing doesn't allow to extend
> it easily. Let's move it to a separate function so we can add more
> parameters and modes.
>
> In order for the tests to still pass, some extra checks are needed,
On Mon, 14 Nov 2022 14:00:21 +0100, Maxime Ripard wrote:
> As the number of kunit tests in KMS grows further, we start to have
> multiple test suites that, for example, need to register a mock DRM
> driver to interact with the KMS function they are supposed to test.
>
> Let's add a file meant to p
On Mon, 14 Nov 2022 14:00:20 +0100, Maxime Ripard wrote:
> KMS supports a number of named modes already, but it's never been
> documented anywhere, let's fix that.
>
>
Applied to drm/drm-misc (drm-misc-next).
Thanks!
Maxime
