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 vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 11288C4332F for ; Thu, 17 Nov 2022 17:13:00 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S240530AbiKQRM6 (ORCPT ); Thu, 17 Nov 2022 12:12:58 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:41372 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S234960AbiKQRMy (ORCPT ); Thu, 17 Nov 2022 12:12:54 -0500 Received: from mail-pj1-x102b.google.com (mail-pj1-x102b.google.com [IPv6:2607:f8b0:4864:20::102b]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 069085D6A6 for ; Thu, 17 Nov 2022 09:12:54 -0800 (PST) Received: by mail-pj1-x102b.google.com with SMTP id w4-20020a17090ac98400b002186f5d7a4cso2450632pjt.0 for ; Thu, 17 Nov 2022 09:12:54 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=1R822jcgCiPh3CxEI4LZqZZ6f8Tc9V1v0R26xcOw7ZM=; b=KDavSi0mdYdPpqiYNYkyB6ALcKpDiqvA6qoBp6uo6WPci0B62WhYU+tEdx9RvVST13 nElxU5sXpxk3vxdRv+MV45hsoF0ryXbvYsAViuobUqZoG9JbGFahBbsKCrbMj5XI9nC5 FJGIZdApp0fONaw//XhTp7kkKzXF8Y5TisIVs= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=1R822jcgCiPh3CxEI4LZqZZ6f8Tc9V1v0R26xcOw7ZM=; b=n7YhkpBUpiHK5ibHYcB9lTJ7s0UedNEZSWN1Remv04IfPQp0YfAmd1efGbqNrwJNKS 3sG4uMeyohTCaV8z4dfhHVdBo4N73NTN20FAn0tJTz4Ro71QgPeX9IkuvZPyLnxGTzkx bLqcaPkcMr+8NfuS5sEpKnyYCw+Sm4lTaLU3pmD71fmxIhcbNiSBJIX1uI+6jc4yJV4/ 8QzUuiEb22oJVwN/ES/iFn40L3YLdSbA2gMROmE4ujLYPJkUznhCzyJ/PYTrBOxkO2Mp npnS5nkNHsE77MILiEQzjnzvjOQtLw95GvuzUcd9PjDrOBXwvZH8ZFkU0OwVh6SP1fM5 4cMA== X-Gm-Message-State: ANoB5pmZ7IKrueEBlo1vnlM73/MBxQo475qvgp2ouwgxzrVrdgpo2oNK 9T8PTqygwTT0IDIX/fa4I0ZRIotDWPTl0+BWBoLvAcO7ENg= X-Google-Smtp-Source: AA0mqf4Sr75qf5iJL/dTTs3yLXtqkRa5F/ANwcf6gxNnYDL3LMROj1R4pCZt6TEyz7OGaduAq6Tj4R9nhmFejgKpai4= X-Received: by 2002:a17:90a:5317:b0:213:34f7:fb14 with SMTP id x23-20020a17090a531700b0021334f7fb14mr9449761pjh.25.1668705173302; Thu, 17 Nov 2022 09:12:53 -0800 (PST) MIME-Version: 1.0 References: <20221117110804.1431024-1-hsinyi@chromium.org> In-Reply-To: From: Hsin-Yi Wang Date: Fri, 18 Nov 2022 01:20:19 +0800 Message-ID: Subject: Re: [PATCH v6 1/3] drm_bridge: register content protect property To: Doug Anderson Cc: Sean Paul , Robert Foss , Maarten Lankhorst , Maxime Ripard , Thomas Zimmermann , Daniel Vetter , dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org, Allen Chen , David Airlie Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Nov 17, 2022 at 11:57 PM Doug Anderson wrote: > > Hi, > > On Thu, Nov 17, 2022 at 3:08 AM Hsin-Yi Wang wrote: > > > > Some bridges are able to update HDCP status from userspace request if > > they support HDCP. > > > > HDCP property is the same as other connector properties that needs to be > > created after the connecter is initialized and before the connector is > > registered. > > > > If there exists a bridge that supports HDCP, add the property to the > > bridge connector. > > > > Signed-off-by: Hsin-Yi Wang > > Reviewed-by: Sean Paul > > Reported-by: kernel test robot > > Not sure it's worth spinning for, but FWIW I wouldn't put > "Reported-by: kernel test robot ". The emails from that > bot are always a bit confusing in this regards, but I think they mean > "if the patch has already landed and you're sending a separate patch > with a fix then please add the "Reported-by" tag". ...but adding it to > the original patch just doesn't make a lot of sense. Got it, thanks. I think I'll wait for a while to see if there's other comments. Otherwise should I send another version to remove the tag? 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 6D1C3C433FE for ; Thu, 17 Nov 2022 17:13:01 +0000 (UTC) Received: from gabe.freedesktop.org (localhost [127.0.0.1]) by gabe.freedesktop.org (Postfix) with ESMTP id 87FEF10E19F; Thu, 17 Nov 2022 17:12:58 +0000 (UTC) Received: from mail-pj1-x102f.google.com (mail-pj1-x102f.google.com [IPv6:2607:f8b0:4864:20::102f]) by gabe.freedesktop.org (Postfix) with ESMTPS id 0FDBC10E19F for ; Thu, 17 Nov 2022 17:12:54 +0000 (UTC) Received: by mail-pj1-x102f.google.com with SMTP id k2-20020a17090a4c8200b002187cce2f92so782103pjh.2 for ; Thu, 17 Nov 2022 09:12:54 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=1R822jcgCiPh3CxEI4LZqZZ6f8Tc9V1v0R26xcOw7ZM=; b=KDavSi0mdYdPpqiYNYkyB6ALcKpDiqvA6qoBp6uo6WPci0B62WhYU+tEdx9RvVST13 nElxU5sXpxk3vxdRv+MV45hsoF0ryXbvYsAViuobUqZoG9JbGFahBbsKCrbMj5XI9nC5 FJGIZdApp0fONaw//XhTp7kkKzXF8Y5TisIVs= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=1R822jcgCiPh3CxEI4LZqZZ6f8Tc9V1v0R26xcOw7ZM=; b=05FcO8QXQZpR0qmsnhqqk/w7d7f919xcsyY2hbZ7JpTWTISES6r3wEB2AxmJ433U+b G19MMh6C1OiRB0fbX94FTiyuvmqmLqE3PuIcuyubjhthT+7DdcHEzepT9RIrP8U7CiuK ww1LUOaT7CnEhrsWsHL48LH3G0NJNuYKINI+6MggHzxAkvZibR45WJH5og5yGCrJeIgF e/pISAAsQN9XaWRGvpqb+CIMi71JiPN3EGRLsNdh7X9k4T+QoqS34RwL5TgymVZvk/O/ GffKSNbFwqgGNVUVZoDM+2QiaEwQsnIuNxmCSDSm0Evzdn0eg4dmNML0Zii9qpPrCmIs NXKg== X-Gm-Message-State: ANoB5pnZePP2AfKijFqXGAAx4Ms70kN1chQszQFA6LhjokPlAZcCNb0/ 8dW2pIceruNCmnOBComQeXcMNhCZfvohw+PIGS8dhA== X-Google-Smtp-Source: AA0mqf4Sr75qf5iJL/dTTs3yLXtqkRa5F/ANwcf6gxNnYDL3LMROj1R4pCZt6TEyz7OGaduAq6Tj4R9nhmFejgKpai4= X-Received: by 2002:a17:90a:5317:b0:213:34f7:fb14 with SMTP id x23-20020a17090a531700b0021334f7fb14mr9449761pjh.25.1668705173302; Thu, 17 Nov 2022 09:12:53 -0800 (PST) MIME-Version: 1.0 References: <20221117110804.1431024-1-hsinyi@chromium.org> In-Reply-To: From: Hsin-Yi Wang Date: Fri, 18 Nov 2022 01:20:19 +0800 Message-ID: Subject: Re: [PATCH v6 1/3] drm_bridge: register content protect property To: Doug Anderson Content-Type: text/plain; charset="UTF-8" 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: , Cc: Thomas Zimmermann , Allen Chen , dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org, Sean Paul , Robert Foss Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" On Thu, Nov 17, 2022 at 11:57 PM Doug Anderson wrote: > > Hi, > > On Thu, Nov 17, 2022 at 3:08 AM Hsin-Yi Wang wrote: > > > > Some bridges are able to update HDCP status from userspace request if > > they support HDCP. > > > > HDCP property is the same as other connector properties that needs to be > > created after the connecter is initialized and before the connector is > > registered. > > > > If there exists a bridge that supports HDCP, add the property to the > > bridge connector. > > > > Signed-off-by: Hsin-Yi Wang > > Reviewed-by: Sean Paul > > Reported-by: kernel test robot > > Not sure it's worth spinning for, but FWIW I wouldn't put > "Reported-by: kernel test robot ". The emails from that > bot are always a bit confusing in this regards, but I think they mean > "if the patch has already landed and you're sending a separate patch > with a fix then please add the "Reported-by" tag". ...but adding it to > the original patch just doesn't make a lot of sense. Got it, thanks. I think I'll wait for a while to see if there's other comments. Otherwise should I send another version to remove the tag?