[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <MWHPR07MB276881500489CBFE1F297C1FC1759@MWHPR07MB2768.namprd07.prod.outlook.com>
Date: Wed, 7 Apr 2021 06:03:29 +0000
From: Parshuram Raju Thombare <pthombar@...ence.com>
To: Rob Herring <robh@...nel.org>
CC: "robert.foss@...aro.org" <robert.foss@...aro.org>,
"laurent.pinchart@...asonboard.com"
<laurent.pinchart@...asonboard.com>,
"airlied@...ux.ie" <airlied@...ux.ie>,
"daniel@...ll.ch" <daniel@...ll.ch>,
"dri-devel@...ts.freedesktop.org" <dri-devel@...ts.freedesktop.org>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"a.hajda@...sung.com" <a.hajda@...sung.com>,
"narmstrong@...libre.com" <narmstrong@...libre.com>,
"nikhil.nd@...com" <nikhil.nd@...com>,
"kishon@...com" <kishon@...com>,
Swapnil Kashinath Jakhade <sjakhade@...ence.com>,
Milind Parab <mparab@...ence.com>
Subject: RE: [PATCH v5 1/2] dt-bindings: drm/bridge: MHDP8546 bridge binding
changes for HDCP
Hi Rob,
Thanks for your comment and sorry for late response.
>> - minItems: 1
>> - maxItems: 2
>> + minItems: 2
>> + maxItems: 3
>
>1 entry was valid and now it is not? That's not a compatible change and
>needs an explanation at a minimum.
Yes, as the driver returns error in the absence of SAPB port address range, this
may break the driver on platform without SAPB port. This IP needs SAPB port
to support HDCP feature using embedded HDCP crypto module.
So, to maintain backward compatibility I will modify the driver and allow it
to proceed without HDCP feature, instead of returning an error, in case of no SAPB port.
Regards,
Parshuram Thombare
Powered by blists - more mailing lists