From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from gabe.freedesktop.org (gabe.freedesktop.org [131.252.210.177]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id AD1C2C43334 for ; Fri, 10 Jun 2022 08:54:22 +0000 (UTC) Received: from gabe.freedesktop.org (localhost [127.0.0.1]) by gabe.freedesktop.org (Postfix) with ESMTP id 4E79D10E799; Fri, 10 Jun 2022 08:54:19 +0000 (UTC) Received: from mail-4323.proton.ch (mail-4323.proton.ch [185.70.43.23]) by gabe.freedesktop.org (Postfix) with ESMTPS id 2A95511272C for ; Fri, 10 Jun 2022 08:54:17 +0000 (UTC) Date: Fri, 10 Jun 2022 08:54:03 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=emersion.fr; s=protonmail2; t=1654851255; x=1655110455; bh=Ay3vNldDYeXoH6RuVdHIVV78Y6TGsyO0i919h6PwFS8=; h=Date:To:From:Cc:Reply-To:Subject:Message-ID:In-Reply-To: References:Feedback-ID:From:To:Cc:Date:Subject:Reply-To: Feedback-ID:Message-ID; b=rYocdbt9FxwXriRbOwaMBgVloXVaNdt7yCwTZ/ew2S2MeyXlysD3+GGekcfGDcVs0 6d+m8kb+djn9Kbr3EQvF0QTIqYkLCOm9MdE8zcXIhS4tAdJQBTShP6hPnKM2iLj/OW Mb2vqws8RZv+STL2a02eydW/0f++qafcJU8oVsLDByqn3CUOL/7dZJZAOJ0lKnRSLp lLaB4yax0YfGEzp6ZHHMnYhq74HFkn+tccEgNAzaqnDtPz2IysYAC6ExiJDB+Pyypy /DF0Am8ClZlQqTGAtn7hkfNrs8xlDD692OMDhKU1RUEnQFMGMg5hndf23a/lwKbbMM 7xvalaTXG1tRQ== To: Zack Rusin From: Simon Ser Subject: Re: [PATCH 0/6] drm: Add mouse cursor hotspot support to atomic KMS Message-ID: <4CJ-x-v-p82cgfBong1zaXjiyI_CnIyh2mOHdGEDi8dpNgr-M4cagtnxFnFCipfM9OjcoM9ZtWtaHKglAzjDzP8169AKwGqGMVT042UhHXk=@emersion.fr> In-Reply-To: <0485fdf9844f8c89cd5670096b78f8090378b2a1.camel@vmware.com> References: <20220602154243.1015688-1-zack@kde.org> <20220607110707.02eccda5@eldfell> <197201d5da2c504502b8c2225d6766338b18d732.camel@vmware.com> <20220608105338.22592a09@eldfell> <0485fdf9844f8c89cd5670096b78f8090378b2a1.camel@vmware.com> Feedback-ID: 1358184:user:proton MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: dri-devel@lists.freedesktop.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Direct Rendering Infrastructure - Development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: Simon Ser Cc: "hdegoede@redhat.com" , "airlied@linux.ie" , "dri-devel@lists.freedesktop.org" , "gurchetansingh@chromium.org" , Martin Krastev , "ppaalanen@gmail.com" , "kraxel@redhat.com" , "tzimmermann@suse.de" , "wayland-devel@lists.freedesktop.org" , Maaz Mombasawala Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" I agree with what others have replied, just adding a few more details. On Thursday, June 9th, 2022 at 21:39, Zack Rusin wrote: > virtualized drivers send drm_kms_helper_hotplug_event which sends a HOTPL= UG=3D1 > event with a changed preferred width/height (Note: and the "hotplug_mode_update" property is set to 1.) > suggested_x and suggested_y properties These come with their own set of issues. They are poorly defined, but it se= ems like they describe a position in physical pixel coordinates. Compositors do= n't use physical pixel coordinates to organize their outputs, instead they use logical coordinates. For instance, a HiDPI 4k screen with a scale of 2 will take up 1920x1080 logical pixels. There is no way to convert physical pixel coordinates to logical pixel coordinates in the general case, because there= 's no "global scale factor". So suggested_x/y are incompatible with the way compositors work.