Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S935132AbeAHQsa (ORCPT + 1 other); Mon, 8 Jan 2018 11:48:30 -0500 Received: from mail-wm0-f50.google.com ([74.125.82.50]:34530 "EHLO mail-wm0-f50.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757568AbeAHQs2 (ORCPT ); Mon, 8 Jan 2018 11:48:28 -0500 X-Google-Smtp-Source: ACJfBouklf/WZ5DCNt5I33a4c7oMjLYyoT1KH2UNUB/mwhlPuE0gE5dxW0I4dcH82OcmGvJCwdEGMVJAgehn9PPh3rY= MIME-Version: 1.0 In-Reply-To: <20180108155029.244552-6-seanpaul@chromium.org> References: <20180108155029.244552-1-seanpaul@chromium.org> <20180108155029.244552-6-seanpaul@chromium.org> From: Philippe Ombredanne Date: Mon, 8 Jan 2018 17:47:46 +0100 Message-ID: Subject: Re: [PATCH v5 5/9] drm/i915: Add HDCP framework + base implementation To: Sean Paul Cc: dri-devel , intel-gfx@lists.freedesktop.org, LKML , Daniel Vetter , seanpaul@google.com, ramalingam.c@intel.com, Chris Wilson , Jani Nikula , Joonas Lahtinen , Rodrigo Vivi , David Airlie Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Return-Path: Sean, On Mon, Jan 8, 2018 at 4:50 PM, Sean Paul wrote: > This patch adds the framework required to add HDCP support to intel > connectors. It implements Aksv loading from fuse, and parts 1/2/3 > of the HDCP authentication scheme. > > Note that without shim implementations, this does not actually implement > HDCP. That will come in subsequent patches. > --- /dev/null > +++ b/drivers/gpu/drm/i915/intel_hdcp.c > @@ -0,0 +1,740 @@ > +/* > + * Copyright (C) 2017 Google, Inc. > + * > + * Permission is hereby granted, free of charge, to any person obtaining a > + * copy of this software and associated documentation files (the "Software"), > + * to deal in the Software without restriction, including without limitation > + * the rights to use, copy, modify, merge, publish, distribute, sublicense, > + * and/or sell copies of the Software, and to permit persons to whom the > + * Software is furnished to do so, subject to the following conditions: > + * > + * The above copyright notice and this permission notice shall be included in > + * all copies or substantial portions of the Software. > + * > + * THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR > + * IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, > + * FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL > + * THE COPYRIGHT HOLDER(S) OR AUTHOR(S) BE LIABLE FOR ANY CLAIM, DAMAGES OR > + * OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, > + * ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR > + * OTHER DEALINGS IN THE SOFTWARE. Would you mind using an SPDX tag instead of this fine but long legalese? See Thomas doc [1] for details. Thanks! [1] https://lkml.org/lkml/2017/12/28/323 -- Cordially Philippe Ombredanne