Received: by 2002:a05:6a10:a0d1:0:0:0:0 with SMTP id j17csp72241pxa; Mon, 3 Aug 2020 23:14:57 -0700 (PDT) X-Google-Smtp-Source: ABdhPJw0WT4t2tTm2xle9LDre2csClQu+61RcPHBoa1uRFQBFdZqlc8YHFFi4yaFrAruyECY2igp X-Received: by 2002:a17:906:264d:: with SMTP id i13mr19305033ejc.284.1596521697165; Mon, 03 Aug 2020 23:14:57 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1596521697; cv=none; d=google.com; s=arc-20160816; b=LBnLiArZCEgBRHVsT+BhX5L4NtN2wy2CYiPswWZDNF3KZbCY1N6/oDCaV2fAAgADL3 oGwfUd2KwiE3kz2jYyBEltrhoo1zAbWyfdUP5vhTGRezg+TjTSP6tmzbd6mthd75bdHv zFZ1DfQMRD4RRm7oU6xzRfIRjZ8l0dwsb/7gXZLxxQiwk5lLeH1ymWw50yu3in6vR9cN 0kdE0pR6Z7B0nK34uuf46VX4V08E3mNrFr4SiQnNmUC5nPmWZnfNBFagEzXXp/4ucnBZ AqTtVW06DNuyDCXfBvE1aj9/63HgU1UjaRpvtRWpm/mZwRo1Z6O3Gc47UjcF3YrihE7l PcCg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject; bh=Ot7UETlwTYvsyWpLZis8PNl8g1oezP6vUgQWVKDFCPU=; b=wYKxowpyhIw4z7nr2OJhgyo6OEU75pMEOmpnUGFBSFnpDz4ZV+tfkV4gAxmLULIVxp 2PTeljeE4nLBVKksdzAV1I7JeMjoSqXsxECaTZr+23zDUpcg24Nw+SepIl+aAvyKPL5b 9f1cvIPZ2xmMLSFYaQNzhlEaJdDQ6TEEuG/xQgXAVlJxUYhEKWbH7mr+ANTHsCRbd8Cj ozZhSzGK/a6BNmbhtxE9fFSyY5gDYWWzJbioSJEJBxCY+Se/JysCO8T51dfwk5BhYYGa Q3WPJbMiHT7oc+F83C8WNm5j/4JXBpmYneGv28G+2wx7xJkkIWZqQqrogT9MGzRhts3P ajyA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id f1si11508981ejx.211.2020.08.03.23.14.34; Mon, 03 Aug 2020 23:14:57 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728462AbgHDGOI (ORCPT + 99 others); Tue, 4 Aug 2020 02:14:08 -0400 Received: from mx2.suse.de ([195.135.220.15]:34140 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727862AbgHDGOI (ORCPT ); Tue, 4 Aug 2020 02:14:08 -0400 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.221.27]) by mx2.suse.de (Postfix) with ESMTP id B8F2CAEFE; Tue, 4 Aug 2020 06:14:22 +0000 (UTC) Subject: Re: [PATCH 4/6] xen: Sync up with the canonical protocol definition in Xen To: Oleksandr Andrushchenko , xen-devel@lists.xenproject.org, dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org, boris.ostrovsky@oracle.com, airlied@linux.ie, daniel@ffwll.ch Cc: sstabellini@kernel.org, dan.carpenter@oracle.com, intel-gfx@lists.freedesktop.org, Oleksandr Andrushchenko References: <20200731125109.18666-1-andr2000@gmail.com> <20200731125109.18666-5-andr2000@gmail.com> From: =?UTF-8?B?SsO8cmdlbiBHcm/Dnw==?= Message-ID: <90b215cb-c878-340e-402a-7739ba17e4a7@suse.com> Date: Tue, 4 Aug 2020 08:14:06 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0 MIME-Version: 1.0 In-Reply-To: <20200731125109.18666-5-andr2000@gmail.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 31.07.20 14:51, Oleksandr Andrushchenko wrote: > From: Oleksandr Andrushchenko > > This is the sync up with the canonical definition of the > display protocol in Xen. > > 1. Add protocol version as an integer > > Version string, which is in fact an integer, is hard to handle in the > code that supports different protocol versions. To simplify that > also add the version as an integer. > > 2. Pass buffer offset with XENDISPL_OP_DBUF_CREATE > > There are cases when display data buffer is created with non-zero > offset to the data start. Handle such cases and provide that offset > while creating a display buffer. > > 3. Add XENDISPL_OP_GET_EDID command > > Add an optional request for reading Extended Display Identification > Data (EDID) structure which allows better configuration of the > display connectors over the configuration set in XenStore. > With this change connectors may have multiple resolutions defined > with respect to detailed timing definitions and additional properties > normally provided by displays. > > If this request is not supported by the backend then visible area > is defined by the relevant XenStore's "resolution" property. > > If backend provides extended display identification data (EDID) with > XENDISPL_OP_GET_EDID request then EDID values must take precedence > over the resolutions defined in XenStore. > > 4. Bump protocol version to 2. > > Signed-off-by: Oleksandr Andrushchenko Reviewed-by: Juergen Gross Juergen