All of lore.kernel.org
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Parshuram Raju Thombare <pthombar@cadence.com>
Cc: "robert.foss@linaro.org" <robert.foss@linaro.org>,
	"robh+dt@kernel.org" <robh+dt@kernel.org>,
	"airlied@linux.ie" <airlied@linux.ie>,
	"daniel@ffwll.ch" <daniel@ffwll.ch>,
	"dri-devel@lists.freedesktop.org"
	<dri-devel@lists.freedesktop.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"a.hajda@samsung.com" <a.hajda@samsung.com>,
	"narmstrong@baylibre.com" <narmstrong@baylibre.com>,
	"nikhil.nd@ti.com" <nikhil.nd@ti.com>,
	"kishon@ti.com" <kishon@ti.com>,
	Swapnil Kashinath Jakhade <sjakhade@cadence.com>,
	Milind Parab <mparab@cadence.com>
Subject: Re: [PATCH v2 1/2] dt-bindings: drm/bridge: MHDP8546 bridge binding changes for HDCP
Date: Mon, 1 Mar 2021 18:27:44 +0200	[thread overview]
Message-ID: <YD0WAMySrv53lxFR@pendragon.ideasonboard.com> (raw)
In-Reply-To: <DM5PR07MB319661E8BFEB251CE17AF587C19A9@DM5PR07MB3196.namprd07.prod.outlook.com>

Hi Parshuram,

On Mon, Mar 01, 2021 at 04:14:54PM +0000, Parshuram Raju Thombare wrote:
> Hi Laurent,
> 
> > Is this a property of the hardware, that is, are there multiple versions
> > of this IP core covered by the same compatible string that support HDCP
> > 1.4 only, DHCP 2.2 only or both ? Or is it a way to select what a given
> > system will offer ?[] 
> 
> MHDP hardware supports both HDCP 2.2 and 1.4. So, this is a way
> to select the version of HDCP, system wish to support.

Then I'm not sure this qualifies as a DT property, which should describe
the system, not configure it. A way for userspace to configure this
would be better.

-- 
Regards,

Laurent Pinchart

WARNING: multiple messages have this Message-ID (diff)
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Parshuram Raju Thombare <pthombar@cadence.com>
Cc: "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"narmstrong@baylibre.com" <narmstrong@baylibre.com>,
	"airlied@linux.ie" <airlied@linux.ie>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"dri-devel@lists.freedesktop.org"
	<dri-devel@lists.freedesktop.org>,
	"kishon@ti.com" <kishon@ti.com>,
	"a.hajda@samsung.com" <a.hajda@samsung.com>,
	"robh+dt@kernel.org" <robh+dt@kernel.org>,
	"robert.foss@linaro.org" <robert.foss@linaro.org>,
	Swapnil Kashinath Jakhade <sjakhade@cadence.com>,
	"nikhil.nd@ti.com" <nikhil.nd@ti.com>,
	Milind Parab <mparab@cadence.com>
Subject: Re: [PATCH v2 1/2] dt-bindings: drm/bridge: MHDP8546 bridge binding changes for HDCP
Date: Mon, 1 Mar 2021 18:27:44 +0200	[thread overview]
Message-ID: <YD0WAMySrv53lxFR@pendragon.ideasonboard.com> (raw)
In-Reply-To: <DM5PR07MB319661E8BFEB251CE17AF587C19A9@DM5PR07MB3196.namprd07.prod.outlook.com>

Hi Parshuram,

On Mon, Mar 01, 2021 at 04:14:54PM +0000, Parshuram Raju Thombare wrote:
> Hi Laurent,
> 
> > Is this a property of the hardware, that is, are there multiple versions
> > of this IP core covered by the same compatible string that support HDCP
> > 1.4 only, DHCP 2.2 only or both ? Or is it a way to select what a given
> > system will offer ?[] 
> 
> MHDP hardware supports both HDCP 2.2 and 1.4. So, this is a way
> to select the version of HDCP, system wish to support.

Then I'm not sure this qualifies as a DT property, which should describe
the system, not configure it. A way for userspace to configure this
would be better.

-- 
Regards,

Laurent Pinchart
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2021-03-01 17:35 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-01 11:21 [PATCH v2 0/2] enable HDCP in Cadence MHDP bridge driver Parshuram Thombare
2021-03-01 11:21 ` Parshuram Thombare
2021-03-01 11:22 ` [PATCH v2 1/2] dt-bindings: drm/bridge: MHDP8546 bridge binding changes for HDCP Parshuram Thombare
2021-03-01 11:22   ` Parshuram Thombare
2021-03-01 15:41   ` Laurent Pinchart
2021-03-01 15:41     ` Laurent Pinchart
2021-03-01 16:14     ` Parshuram Raju Thombare
2021-03-01 16:14       ` Parshuram Raju Thombare
2021-03-01 16:27       ` Laurent Pinchart [this message]
2021-03-01 16:27         ` Laurent Pinchart
2021-03-02 12:53         ` Parshuram Raju Thombare
2021-03-02 12:53           ` Parshuram Raju Thombare
2021-03-08 20:42           ` Laurent Pinchart
2021-03-08 20:42             ` Laurent Pinchart
2021-03-09  8:02             ` Parshuram Raju Thombare
2021-03-09  8:02               ` Parshuram Raju Thombare
2021-03-08 17:36   ` Rob Herring
2021-03-08 17:36     ` Rob Herring
2021-03-09 15:35     ` Parshuram Raju Thombare
2021-03-09 15:35       ` Parshuram Raju Thombare
2021-03-01 11:23 ` [PATCH v2 2/2] drm: bridge: cdns-mhdp8546: Enable HDCP Parshuram Thombare
2021-03-01 11:23   ` Parshuram Thombare

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=YD0WAMySrv53lxFR@pendragon.ideasonboard.com \
    --to=laurent.pinchart@ideasonboard.com \
    --cc=a.hajda@samsung.com \
    --cc=airlied@linux.ie \
    --cc=daniel@ffwll.ch \
    --cc=devicetree@vger.kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=kishon@ti.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mparab@cadence.com \
    --cc=narmstrong@baylibre.com \
    --cc=nikhil.nd@ti.com \
    --cc=pthombar@cadence.com \
    --cc=robert.foss@linaro.org \
    --cc=robh+dt@kernel.org \
    --cc=sjakhade@cadence.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.