Received: by 2002:a05:7412:f584:b0:e2:908c:2ebd with SMTP id eh4csp1296427rdb; Mon, 4 Sep 2023 08:59:02 -0700 (PDT) X-Google-Smtp-Source: AGHT+IEzmujQlG5UPzaYCWf2BKEvoEKfcGPZDjyk536zUkxAF5w+MhY3HPFnd/0/XYHXxiSDkYqk X-Received: by 2002:a17:90a:2acf:b0:26b:36dc:2f08 with SMTP id i15-20020a17090a2acf00b0026b36dc2f08mr8196828pjg.46.1693843141715; Mon, 04 Sep 2023 08:59:01 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1693843141; cv=none; d=google.com; s=arc-20160816; b=Wy+u6V5xYtHa6/+hFpmnxfoiRQQ4ooRUTVNRipsCGKtDN1ZiM+VQnjyJc99i78Obal +LnkFWlqHNdlj4evhhAhBZY6thevENT+0FUwjg9JKlmotf74Ft+oKKrcfLt6jHPqQDY9 VQhixEVQCDt2rqmanxu3AsSh9RQp1ZObaDA3kVvuTX2uI82xKPFOOrWE8HBehqtuc4Yi QY3tYuGPMkRKOpXKxFBa5mtlxX6F9RyKk3p8WFeXrWUgClIOeTZSuszEAei6ci7BopIi fBn9XF8xwtC6+IEDlsLkR0bl8qy/WK+NSB6ZDrr6tCeoIpV0yT8cX0+8j5DMoHsWigrV n3fw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date:dkim-signature; bh=8dxBnPoXxdza+32w6j4E/LZJpPXpU3PuCN1rf7gsWNY=; fh=TcVHToPCZ9+JT6xgPbW0xB/HLEUeSqBcbchxlt4KYfQ=; b=zEXo9xf8zfKLOREikksWbxxuovxMKtYOH2odeyxiA/ZQ2m9DqhRz6gQx2nh44qMWTC RQ1kiGTmcn6W17xXMd8vw8NOzBMyUyPxbiGkA/ZccoOGtuY+dTuBhok0Dj7lA+C7v3BV mLsGfL0sKbZvZZBP1wBSS29WIddcgXIKpQVGTWh0z0YNlKjAtVmOslcaCpQ3UxMovg7r rM0r5lky0j5FZOW1r7w2zUDNr+XLOrcvB7QBQBAwjs014I4XBzIUmUaTpkbBlFX6ueYL lgkWxrqeATw+M+plBvuTanwS4SLdEJqVgiEWMYzWrE7fssU2ZoJsI2eyMt0oXoMOcMZL CpDg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=dH13EUrJ; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id bj7-20020a17090b088700b0026841a42bffsi8045591pjb.139.2023.09.04.08.58.45; Mon, 04 Sep 2023 08:59:01 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=dH13EUrJ; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S239358AbjIDPoa (ORCPT + 99 others); Mon, 4 Sep 2023 11:44:30 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:49398 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229492AbjIDPo3 (ORCPT ); Mon, 4 Sep 2023 11:44:29 -0400 Received: from dfw.source.kernel.org (dfw.source.kernel.org [IPv6:2604:1380:4641:c500::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 4327383; Mon, 4 Sep 2023 08:44:26 -0700 (PDT) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id CB9866147A; Mon, 4 Sep 2023 15:44:25 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 71FDFC433C8; Mon, 4 Sep 2023 15:44:23 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1693842265; bh=qdTA8V0KXUZLUrgT6HNemfUGewlGYuqtThrUKMyrcZ0=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=dH13EUrJ64qj61MXG8wG386P+QT4XaAFmRFAw2/w72eMe0857orK3vQj6JAk6cgVn iJPLJFgL4Xi2O2SNHeIBZpMEIWf4FuRG3eNTendu87z3KgGSqv9O8Xgvzm8PGCWnza H4LOYfFM8wDC1Gx6gyv2CLr/GHaVHs5C72QJc28/WX0sK+r7ChVixP1RvWUSyzHQUR 1OnGvXh+m8TFv2dKEJ+GqWDrV/0kR0v9oG0AIVXpdl1T3EesqgAxQ/qiYHwwlKMqA0 Bg3WOp7I6xyGVbCc6xi+MYgY1igO4ezDYIoR+KdjLtiT/IAIgZP1ObXexiiQuvWyAw HpNYGylUAzweg== Date: Mon, 4 Sep 2023 08:46:40 -0700 From: Bjorn Andersson To: Dmitry Baryshkov Cc: David Airlie , Daniel Vetter , Andrzej Hajda , Neil Armstrong , Robert Foss , Laurent Pinchart , Jonas Karlman , Jernej Skrabec , Maarten Lankhorst , Maxime Ripard , Thomas Zimmermann , Bryan O'Donoghue , Guenter Roeck , Heikki Krogerus , Janne Grunau , Simon Ser , Andy Gross , Konrad Dybcio , Greg Kroah-Hartman , dri-devel@lists.freedesktop.org, linux-arm-msm@vger.kernel.org, linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org, freedreno@lists.freedesktop.org Subject: Re: [RFC PATCH v1 00/12] drm,usb/typec: uABI for USB-C DisplayPort connectors Message-ID: References: <20230903214150.2877023-1-dmitry.baryshkov@linaro.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20230903214150.2877023-1-dmitry.baryshkov@linaro.org> X-Spam-Status: No, score=-4.4 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_MED, SPF_HELO_NONE,SPF_PASS autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Sep 04, 2023 at 12:41:38AM +0300, Dmitry Baryshkov wrote: > During the discussion regarding DisplayPort wrapped in the USB-C > connectors (via the USB-C altmode) it was pointed out that currently > there is no good way to let userspace know if the DRM connector in > question is the 'native' DP connector or if it is the USB-C connector. > > An attempt to use DRM_MODE_CONNECTOR_USB for such connectors was > declined, as existing DP drivers (i915, AMD) use > DRM_MODE_CONNECTOR_DisplayPort. New drivers should behave in the same > way. > Sorry, didn't see the commit message before posting my complaint about USB -> DisplayPort. > An attempt to use subconnector property was also declined. It is defined > to the type of the DP dongle connector rather than the host connector. > > This attempt targets reusing the connector's PATH property. Currently > this property is only used for the DP MST connectors. This patchset > reuses it to point out to the corresponding registered typec port > device. > Still interested in understanding how the path string should look like. Is the path expected to be consumed by machine, or is it only there for human convenience? Regards, Bjorn